# Vastlink

> Vastlink is an early-stage, open and verifiable digital asset operating system (DAOS) for humans and AI, currently being shaped with a small group of design partners. It is designed to power keyless, self-custodial MPC / account-abstraction (AA) wallets with multi-factor authentication, policy controls (spend limits, multisig approvals) and treasury automation across BTC, Ethereum, Solana, BNB Chain, Polygon and more. It is intended to run self-hosted or as a cloud service.

Key facts:

- **Category:** digital asset operating system (DAOS). A DAOS manages the entire lifecycle of digital assets, whereas wallet-as-a-service (WaaS) and wallet-as-a-protocol (WaaP) only cover one component, the wallet. The relationship is similar to that of an operating system and a database.
- **Keyless, powered by MPC:** no private key or seed phrase for users to manage, and no single point of failure. Users sign in with familiar methods such as email.
- **Security:** enterprise-grade security with MFA, spend limits and multisig approvals.
- **Deployment (intended):** designed for self-hosting on your own infrastructure or cloud use, with no vendor lock-in. A production self-hosted release is not available yet.
- **Open (intended):** open source is part of the intended design, with a long-term goal of a decentralized network. Key flows are designed to be self-hosted, extended and audited.
- **Pricing:** there is no production pricing yet. Vastlink is working with a small number of design partners before finalizing the product or commercial model. See https://vastlink.xyz/design-partners/.
- **Developers:** a developer-first SDK with simple APIs, documentation and live examples, plus a modular path to more chains.
- **Who it is for:** individuals, teams, treasuries, DAOs, funds, PayFi operators and developers who need secure, auditable wallet infrastructure.
- **Use cases:** treasury management (multi-chain holdings, multisig approvals, payouts, AI-powered earning options); payments (on-ramp/off-ramp, KYC/KYB/KYT, compliant cross-border B2B payments); real-world assets (RWA project setup, user onboarding, token issuance and management).
- **Products:** Vastbase, a multisig wallet built on Vastlink and Lit Protocol for crypto treasuries, RWAs, DAOs and VC funds, with email onboarding and email-driven approval workflows.
- **Locations:** Dubai, Hong Kong, Singapore, Sydney.

This file contains the full text of every article on the Vastlink blog. The index of the site is at https://vastlink.xyz/llms.txt.

---

## Digital Asset Custody Platforms Compared: Why Security Technology Is No Longer the Differentiator

Source: https://vastlink.xyz/blog/digital-asset-custody-platforms-compared-2026/  
Published: 2026-09-09

![Digital asset custody platforms compared — Fireblocks, BitGo, Copper, Anchorage Digital, DFNS and more](https://vastlink.xyz/blog/digital-asset-custody-platforms-compared-2026/assets/headline.png)

*If you are choosing — or re-evaluating — a digital asset custody platform for your business, this is for you.*

### The shift nobody priced in

Custody used to be a security question: does the platform use MPC, HSMs, or multisig, and is the cryptography sound? In 2026, that question is mostly settled. It is becoming an operational-finance question instead: can your auditors sign off on it, can your accounting team reconcile it, and can you actually get your data out if you need to leave?

Ridgeway Financial Services put ten major institutional digital-asset security and custody platforms side by side — Fireblocks, BitGo, Copper, Ledger Enterprise, Ripple Custody, Anchorage Digital, DFNS, Fordefi, Safe, and Hex Trust — and reached a conclusion worth sitting with: **“Custody platforms differ more in audit-readiness and internal-control compatibility than in core security technology.”** ([Ridgeway Financial Services](https://www.ridgewayfs.com/digital-asset-security-platforms/))

That matches what we have been saying about custody for a while: the hard part was never the cryptography. It is everything built around it.

### Security is a solved (well, almost and technically) problem

Every platform in the comparison uses mature, well-understood cryptographic approaches — MPC, HSMs, secure enclaves, or on-chain multisig:

| Platform | Security method | Custody status |
| --- | --- | --- |
| **Fireblocks** | MPC | Regulated via Fireblocks Trust Company (NYDFS limited-purpose trust) |
| **BitGo** | Multisig + HSM | BitGo Bank & Trust, N.A. (federally chartered) |
| **Anchorage Digital** | Secure enclave (HSM, TEE) | Federally chartered bank |
| **Copper** | MPC (one offline share) | Infrastructure only — no custody entity |
| **DFNS** | MPC | Infrastructure only — API-first |
| **Fordefi** | MPC self-custody | Infrastructure only |
| **Ledger Enterprise** | Hardware root of trust | Infrastructure only |
| **Ripple Custody** | Multiple | Ripple-owned regulated entities |
| **Hex Trust** | Multiple | APAC-focused regulated custodian |
| **Safe** | On-chain multisig | Open-source, no custody entity |

*(Security method and custody status per Ridgeway Financial Services’ comparison.)*

None of these are exotic anymore. MPC, HSMs, and multisig have all been in institutional production for years. If you are evaluating a platform primarily on which cryptographic scheme it uses, you are asking a question the market has already answered. The real evaluation happens one layer up.

### The seven things that actually separate these platforms

According to Ridgeway’s analysis, the meaningful differences cluster around seven areas:

**1. Regulated custody — who actually holds the assets, and under which legal entity?**  
 Only some providers pair their technology with a qualified-custodian entity. Anchorage Digital Bank, BitGo Bank & Trust, N.A., and Fireblocks Trust Company hold federal or NYDFS charters. DFNS, Copper, Ledger Enterprise, Fordefi, and Safe are infrastructure only — if you need a qualified custodian, you have to pair the platform with one separately.

**2. Audit readiness — SOC 2 Type II, audit-log quality, and auditor support.**  
 All ten platforms claim SOC 2 Type II availability, but Ridgeway is direct about what that means in practice: **“SOC 2 status should be treated as vendor-reported until the company reviews the current report.”** The report needs to be current (within twelve months), and its scope — including any subservice organizations — has to be reviewed under NDA, not taken from a marketing page.

**3. Internal controls — segregation of duties, approval policies, and change management.**  
 This is the gap most companies underestimate. Ridgeway’s finding: **“A custody platform alone does not satisfy a company’s internal control obligations. Policies, approval workflows, segregation of duties, and reconciliation procedures must be designed independently and documented for audit.”** A platform can enforce a transaction policy technically while your organization has no procedure document describing it, no mapping from roles to a segregation-of-duties matrix, and no change-management approval when that policy changes.

**4. Reconciliation — how easily custody activity integrates with accounting and GL systems.**  
 Ridgeway’s framing: **“The platform that minimizes manual reconciliation is the platform that scales.”** Real-time or end-of-day export in a clean GL-compatible format matters more at scale than almost any other feature. Copper’s off-exchange settlement layer (ClearLoop) was flagged as a specific case requiring additional reconciliation infrastructure.

**5. Total cost of ownership — integration, reconciliation, controls, and audit work can exceed the platform fee.**  
 Most enterprise platforms quote custom pricing rather than a published rate card, and Ridgeway notes that **“year-one TCO frequently runs materially higher than the published platform fee”** once you add integration engineering (typically 3–9 months), reconciliation tooling, audit evidence preparation, internal-controls design, and operational staffing.

**6. Migration risk — can historical transaction and audit data actually be exported in a useful format?**  
 Ridgeway’s conclusion is blunt: **“Custody platform migrations are expensive, slow, and risky.”** If you cannot answer, in advance, how your audit trail and transaction history export on day one, you are accepting lock-in you have not evaluated.

**7. Jurisdiction — a platform built for the US may not fit APAC or European operations.**  
 State money-transmitter licensing, the New York BitLicense, MiCA in Europe, and the SEC’s 2026 staff statement on broker-dealer registration of front-end interfaces all intersect with platform choice differently depending on where you operate. A platform’s regulatory strength in one jurisdiction does not transfer to another.

### Qualified custodian vs. infrastructure-only

This distinction shows up throughout Ridgeway’s report and is easy to miss if you are evaluating platforms purely on developer experience:

| Category | Platforms | What it means |
| --- | --- | --- |
| **Qualified custodian entity** | Anchorage Digital Bank, BitGo Bank & Trust N.A., Fireblocks Trust Company, Ripple-owned entities | The platform itself can legally hold assets under a bank or trust charter |
| **Infrastructure only** | DFNS, Copper, Ledger Enterprise, Fordefi, Safe | You need to pair the platform with a separate qualified custodian if your regulatory profile requires one |

Neither category is universally “better” — infrastructure-only platforms are often the right choice for self-custody or hybrid models. But conflating the two during procurement is one of the more common — and expensive — mistakes Ridgeway’s report points to.

### Embedded wallets are a different animal

Several platforms — DFNS, Fireblocks, Ripple Custody among them — offer embedded wallet infrastructure for fintechs building user-facing products, not just institutional custody. Ridgeway flags a subtlety worth internalizing: **“Customer balances may flow through the platform as customer funds rather than company assets, which creates a different presentation in financial statements and a different MTL analysis.”** If your use case is an embedded wallet rather than treasury custody, the accounting and licensing questions are not the same ones covered by a standard custody evaluation.

### Thirteen questions to ask before you sign

Ridgeway compiled a due-diligence list for CFOs evaluating any of these platforms. Condensed:

| # | Question |
| --- | --- |
| 1 | Is a current SOC 2 Type II report available under NDA? |
| 2 | Is external auditor evidence contractual, or does it cost extra? |
| 3 | What is the legal custody entity, and what is its regulatory status? |
| 4 | Is segregation of duties enforced at the policy level? |
| 5 | Is the audit-log export format compatible with your tooling? |
| 6 | What data can you export if you migrate off the platform? |
| 7 | What does the insurance actually cover, and who is the underwriter? |
| 8 | What is the incident-response process and timeline? |
| 9 | What is your exposure to key-personnel risk at the vendor? |
| 10 | Does the platform’s regulatory framework match your qualified-custody obligations? |
| 11 | What is the reconciliation export cadence, and how well does it map to your GL? |
| 12 | What is realistic all-in year-one TCO, not just the platform fee? |
| 13 | What percentage of the vendor’s revenue comes from its top five customers? |

That last one is easy to skip and worth asking anyway — customer concentration is a business-continuity signal, not a technology one.

### Where this lands

Ridgeway’s headline recommendation is not a ranking: **“For most fintech and crypto companies, the right answer is not a single ‘best’ platform but the platform best aligned to the company’s regulatory profile, its auditor’s expectations, and its accounting team’s tooling.”** They put it even more sharply elsewhere in the report: the platform that is best for a Head of Engineering is rarely the platform that minimizes audit findings, simplifies SOC reporting, or keeps a fintech aligned with its money-transmitter obligations.

That is the same conclusion we keep arriving at from a different direction. The cryptography — MPC, HSMs, multisig, secure enclaves — is table stakes now. What is not solved, across every platform on this list, is the governance layer sitting on top of it: who can approve what, how that gets proven to an auditor, how it reconciles to your books, and what happens the day you need to leave. A perfectly implemented key-management scheme does not answer any of those questions by itself.

*Primary source: [Ridgeway Financial Services — “Digital Asset Security Platforms Compared: DFNS vs Fireblocks vs Anchorage (2026)”](https://www.ridgewayfs.com/digital-asset-security-platforms/). All comparative claims, quotes, and the platform-by-platform data above are drawn from that report; verify current SOC 2 status, custody licensing, and pricing directly with each vendor before making a procurement decision.*

---

## What the $88 Million Coldcard Hack Teaches Us About Single-Vendor Custody Risk

Source: https://vastlink.xyz/blog/coldcard-entropy-bug-88m-lessons/  
Published: 2026-08-05

*If you hold digital assets on a hardware wallet — or you advise clients who do — this is written for you.*

![Coldcard hardware wallet](https://vastlink.xyz/blog/coldcard-entropy-bug-88m-lessons/coldcard_title_image.png)

### What happened

On July 30, 2026, attackers drained 1,196 Bitcoin addresses in 41 minutes. 1,082.65 BTC — about $70.2 million at the time — gone before most victims knew anything was wrong. $30 million of it moved in the first ten minutes ([BleepingComputer](https://www.bleepingcomputer.com/news/security/coldcard-wallet-rng-flaw-likely-linked-to-88-million-bitcoin-theft/)).

Two more waves followed on July 31 and August 1: 76.16 BTC, then 207.73 BTC ([TechSpot](https://www.techspot.com/news/113322-coldcard-firmware-flaw-hackers-drain-70-million-bitcoin.html); [CybersecurityNews](https://cybersecuritynews.com/coldcard-hardware-wallet-rng-flaw-bitcoin-theft/)). By the time the bleeding stopped, the total stood at 1,367 BTC — roughly $88.6 million — pulled from 4,585 addresses ([Infosecurity Magazine](https://www.infosecurity-magazine.com/news/coldcard-users-lose-89m-bitcoin/)).

None of the victims lost a device. None of them clicked a phishing link. None of them approved a malicious transaction. They did everything a hardware wallet exists to make unnecessary to worry about — and lost their funds anyway.

The cause: a random number generator that had not been generating random numbers since March 2021.

### The bug, in plain terms

Coldcard, made by Canadian manufacturer Coinkite, is one of the most trusted names in Bitcoin self-custody. Air-gapped, open-source firmware, a dedicated hardware RNG chip. On paper, exactly what a security-conscious holder should want.

The firmware was supposed to pull randomness from the device’s STM32 hardware RNG when generating a new seed. A code change on March 1, 2021 broke that, and it first shipped in firmware v4.0.0 on March 17, 2021. A faulty guard in the `libngu` library checked whether a configuration macro was *defined*, not whether it was actually *enabled* — the macro was present but set to `(0)`, which was enough to pass the check anyway. In Coinkite’s own words: “The guard used `#ifndef`, which tests whether `MICROPY_HW_ENABLE_RNG` is defined, rather than whether its value is nonzero. We defined that macro as zero, so the `#error` did not stop the build.” That silently routed key generation into Yasmarang, a non-cryptographic software fallback built into MicroPython, seeded from the device’s unique ID XOR’d with a free-running timer ([Coinkite — technical backgrounder](https://blog.coinkite.com/entropy-technical-backgrounder/); [Fystack](https://fystack.io/blog/coldcard-entropy-bug-wallet-security); [CybersecurityNews](https://cybersecuritynews.com/coldcard-hardware-wallet-rng-flaw-bitcoin-theft/)).

The practical effect: seeds that should have carried 128 to 256 bits of entropy carried somewhere between 40 bits (Mk3) and 72 bits (Mk4, Mk5, Q) ([Fystack](https://fystack.io/blog/coldcard-entropy-bug-wallet-security)). An attacker who could pin down a device’s unique ID, timer state, and prior RNG calls could reproduce candidate seeds entirely offline and check them against known blockchain addresses — no phishing, no malware, no physical access to the wallet required ([BleepingComputer](https://www.bleepingcomputer.com/news/security/coldcard-wallet-rng-flaw-likely-linked-to-88-million-bitcoin-theft/)).

**⚠️ This wasn’t a zero-day someone had to reverse-engineer under pressure. It was one line of logic that had been silently wrong in shipping firmware for five years.**

### The response — and its limits

Coinkite disclosed the flaw roughly 30 hours after the first attack wave and shipped patched firmware within about two days ([Fystack](https://fystack.io/blog/coldcard-entropy-bug-wallet-security); [TechSpot](https://www.techspot.com/news/113322-coldcard-firmware-flaw-hackers-drain-70-million-bitcoin.html)). Per Coinkite’s own advisory, affected releases were Mk2/Mk3 firmware 4.0.1–4.1.9, Mk4/Mk5 before 5.6.0, and Q before 1.5.0Q, with fixed firmware at 4.2.0, 5.6.0, and 1.5.0Q respectively ([Coinkite — official advisory](https://blog.coinkite.com/coldcard-mk3-seed-generation-warning/)).

But patching the firmware does not patch the seed. Anyone who generated a wallet on vulnerable firmware is still carrying a low-entropy seed today — updating the device doesn’t retroactively fix a key that already exists. Galaxy Research’s advice was blunt: move funds off any Coldcard-generated single-sig seed immediately, generate a fresh seed on patched firmware, verify addresses on-device, and migrate ([Fystack](https://fystack.io/blog/coldcard-entropy-bug-wallet-security); [CybersecurityNews](https://cybersecuritynews.com/coldcard-hardware-wallet-rng-flaw-bitcoin-theft/)).

That is a lot to ask of someone whose entire reason for buying a hardware wallet was to stop thinking about key security.

### This is not a Coldcard problem. It’s a pattern.

Entropy failures are not a hardware wallet issue, or a Bitcoin issue, or a Coinkite issue. They are a recurring category of loss across the entire industry, because entropy quality is invisible until an attacker with capital at stake decides to test it.

| Incident | Year | Root cause | Impact |
| --- | --- | --- | --- |
| Android `SecureRandom` | 2013 | Weak Java RNG on Android reused signing randomness | Bitcoin private keys recovered from reused values |
| Profanity vanity address tool | 2022 | 32-bit seed space in a GPU key generator | ~$160M drained, including Wintermute |
| Trust Wallet browser extension | 2023 | Insufficient entropy in key generation | User funds compromised |
| Libbitcoin Explorer (“Milk Sad”) | 2023 | Predictable Mersenne Twister seeding | Systematic wallet draining |
| Coldcard | 2026 | Hardware RNG silently bypassed for software fallback | $88.6M, 4,585 addresses |

*(Sourced from [Fystack’s](https://fystack.io/blog/coldcard-entropy-bug-wallet-security) analysis of historical entropy failures.)*

The common thread across all five: a single implementation was trusted to get randomness right, nobody could verify that it did, and the flaw sat there — sometimes for years — until someone found it the hard way. As Fystack puts it, the failure mode is “assumed instead of verified.”

### The real lesson: single points of failure don’t announce themselves

A hardware wallet concentrates trust in one place: one vendor, one firmware build, one RNG implementation, one moment of key generation. When that one thing is correct, it’s an excellent security model. When it’s silently wrong, everything built on top of it is wrong too — and there is no way to know until someone with an incentive to look, looks.

Notably, even coverage of this incident pointed at the fix that was hiding in plain sight: multi-signature setups spanning devices from different manufacturers would have been resilient against a vendor-specific RNG failure like this one ([CybersecurityNews](https://cybersecuritynews.com/coldcard-hardware-wallet-rng-flaw-bitcoin-theft/)). If a Coldcard-generated key was only one of several independent keys required to move funds, a flaw in Coldcard’s RNG alone would not have been enough to drain a wallet.

That’s the principle worth generalizing, and it’s a governance principle before it’s a cryptography one: **no single vendor, device, or implementation should be a single point of failure for control of an asset — no matter how trusted that vendor is.** Multi-party computation, multisig across independent hardware, and threshold key generation all express the same underlying idea in different technical forms: split trust so that one silent bug, one compromised employee, or one bad firmware push cannot unilaterally compromise the funds.

To be clear, that alone doesn’t make an organization safe. Distributed key generation still needs to be paired with the operational discipline to catch this class of failure — independent audits of the code paths that generate entropy, monitoring for anomalous fund movement, a real incident-response process, and a documented answer to “how do we know our key generation is doing what we think it’s doing?” Coinkite is a serious, open-source vendor, and the bug still went undetected in production for five years. Verification has to be a process, not a one-time assumption made at purchase.

### Questions worth asking about any wallet’s key generation

| Question | Why it matters |
| --- | --- |
| Is any single vendor’s implementation the sole source of entropy for this key? | A single-vendor RNG bug is a single point of failure, as Coldcard showed |
| Would a flaw in one device or one signer alone be enough to move funds? | Multisig / MPC across independent implementations limits blast radius |
| How would we detect a silent entropy or RNG regression before an attacker does? | Coinkite’s bug shipped in March 2021 and was found in July 2026 |
| If a vendor discloses a flaw, do we have a tested process to rotate keys and migrate funds fast? | Patching firmware does not fix seeds already generated on it |
| Who is accountable for verifying vendor security claims, and how often? | “Open source” and “hardware RNG” are marketing claims until someone checks the code path in production |

### Where this is going

Hardware wallets solved a real problem: keeping keys off internet-connected devices. But the Coldcard incident is a reminder that “cold storage” answers *where* a key lives, not *whether the process that created it was trustworthy* — and that a single implementation, however well-regarded, is still a single point of failure.

The industry’s next step isn’t choosing a different hardware vendor and hoping its RNG is the one that never fails. It’s building custody around the assumption that any single implementation — vendor, device, or protocol — can fail silently, and designing governance so that no single failure is catastrophic: distributed key generation, independent verification, and an operational process that can respond fast when (not if) a flaw surfaces.

That is the governance layer Vastlink is building for digital asset custody — where control of an asset is never resting on the correctness of one vendor’s firmware, and recovery from a single point of failure is a designed capability, not a scramble.

---

## Crypto Custody for Business: A Practical Guide for 2026

Source: https://vastlink.xyz/blog/crypto-custody-for-business/  
Published: 2026-07-05

If your business holds crypto — as treasury, as payment, as investment — and you do not have a documented custody plan, you have a problem you may not know about yet.

### The gap nobody talks about

741 million people own crypto wallets globally ([Crypto.com](https://crypto.com/en/research/crypto-market-sizing-report-h1-2025)). A growing share of them are businesses: funds, treasuries, DAOs, startups accepting crypto payments, and companies holding Bitcoin on their balance sheet.

200+ public companies now disclose Bitcoin reserves totaling over $110 billion ([Bitbo](https://bitbo.io/treasuries/)). Behind each one is a custody arrangement. Most of them were designed by engineers, not governance professionals.

The result: 61% of institutional crypto holders use multiple custodians, but manage them through spreadsheets and Slack messages ([EY / Coinbase Institutional Investor Survey](https://www.ey.com/en_us/financial-services/institutional-digital-assets-survey)). No unified approval workflow. No single audit trail. No documented succession plan.

If someone at your company can move $500,000 in crypto by themselves, and there is no written policy governing who approves what — you do not have a custody solution. You have a liability.

### Three questions your business needs to answer

Before evaluating any custody technology, answer these three questions. They determine everything else.

#### 1. Who can move assets?

In traditional banking, this is straightforward. Authorized signatories are filed with the bank. Dual authorization is standard for large transfers.

In crypto, there is no bank enforcing your policies. If someone has the private key, they can move all assets instantly, irreversibly, at 3 AM on a Sunday. There is no reversal, no chargeback, no fraud department to call.

Your custody solution must enforce authorization thresholds — not as a guideline, but as a cryptographic guarantee. A 2-of-3 multisig means no single person can move funds, period. Not even the CEO.

#### 2. What happens when someone leaves?

Employees leave. Co-founders fall out. Key personnel get hit by buses. If your crypto access depends on any single person, you have a single point of failure.

**QuadrigaCX:** The sole key holder died. C$215.7 million became permanently inaccessible ([Ontario Securities Commission](https://www.osc.ca/quadrigacxreport/)).

Your custody arrangement needs: key rotation when someone leaves, recovery procedures that do not depend on any individual, and a succession plan that is documented and tested — not stored in someone's head.

#### 3. What happens when something goes wrong?

$3.4 billion in crypto was stolen in 2025 ([Chainalysis](https://www.chainalysis.com/blog/2025-crypto-crime-report-introduction/)). Recovery rate: approximately 8% ([PeckShield](https://peckshield.com/)).

If an employee's device is compromised, if a smart contract has a vulnerability, if a custodian goes bankrupt — what is your recovery plan?

FTX held $8 billion in customer assets with no segregation. When it collapsed, customers became unsecured creditors ([CFTC](https://www.cftc.gov/)). Your custody arrangement must guarantee asset segregation, and that guarantee must be independently audited.

### Custody options for businesses — honest comparison

There are four practical approaches. Each makes sense at a different stage.

#### Consumer wallets (MetaMask, Coinbase, Ledger)

| Factor | Reality |
| --- | --- |
| Cost | Free to $150 |
| Setup time | Minutes |
| Multi-user approval | No |
| Audit trail | No |
| Key recovery if holder leaves | Manual (move assets to new wallet) |
| Regulatory compliance | Insufficient for most jurisdictions |
| Appropriate for | Testing, small petty-cash amounts under $10K |

**Bottom line:** Consumer wallets are designed for individuals. They have no concept of organizational roles, approval workflows, or access revocation. If your business relies on a MetaMask wallet controlled by one person, you are one compromised seed phrase away from losing everything.

#### Multisig wallets (Safe, Electrum, native Bitcoin multisig)

| Factor | Reality |
| --- | --- |
| Cost | Free to $100/month |
| Setup time | Hours to days |
| Multi-user approval | Yes (2-of-3, 3-of-5, etc.) |
| Audit trail | On-chain (public) |
| Key recovery if holder leaves | Replace signer, rotate keys |
| Regulatory compliance | Partial (audit trail exists, but no built-in compliance tools) |
| Appropriate for | $10K-$1M, teams of 2-5, DAOs, startups |

**Bottom line:** Multisig is the most accessible business-grade custody option. Safe (formerly Gnosis Safe) secures over $100 billion in digital assets ([Safe](https://safe.global/)). The limitation is that governance lives on-chain and is visible to everyone. For some businesses, this is fine. For others, it exposes operational details they would prefer to keep private.

#### MPC (Multi-Party Computation) platforms

| Factor | Reality |
| --- | --- |
| Cost | $1,000-$10,000/month (mid-market); $50,000-$100,000+/year (enterprise) |
| Setup time | Days to weeks |
| Multi-user approval | Yes, with policy engine |
| Audit trail | Off-chain (private) + on-chain |
| Key recovery if holder leaves | Re-share key fragments without moving assets |
| Regulatory compliance | Built-in compliance tools, SOC 2, ISO 27001 |
| Appropriate for | $1M-$100M+, regulated businesses, funds, family offices |

**Bottom line:** MPC splits private keys into fragments distributed across multiple parties. No single party ever holds the complete key. Key rotation and recovery can happen without moving assets on-chain. This is the institutional standard — but enterprise MPC platforms (Fireblocks, Cobo, BitGo) are priced for enterprises. The mid-market ($500K-$10M in holdings) is underserved. For a deeper technical comparison, see our guide on [crypto custody solutions for institutions](https://vastlink.xyz/blog/crypto-custody-solutions-guide-2026/).

#### Third-party custodians (Coinbase Custody, Anchorage, Fidelity Digital Assets)

| Factor | Reality |
| --- | --- |
| Cost | 0.05%-0.50% of assets annually + transaction fees |
| Setup time | Weeks to months (KYC/KYB required) |
| Multi-user approval | Varies by provider |
| Audit trail | Yes (provider-managed) |
| Key recovery if holder leaves | Managed by custodian |
| Regulatory compliance | Full (regulated entities) |
| Appropriate for | $10M+, businesses requiring regulatory compliance, banks |

**Bottom line:** Third-party custodians are the closest model to traditional banking. You delegate key management to a regulated entity. The trade-off: you depend on the custodian's security and solvency. Verify asset segregation, insurance coverage, and what happens in bankruptcy. The crypto insurance market reached $9.49 billion in 2025 ([Grand View Research](https://www.grandviewresearch.com/)), but coverage typically covers only a fraction of assets under custody.

### The mid-market gap

If your business holds between $500,000 and $10 million in crypto, you are in the most underserved segment of the market.

- Consumer wallets are not enough — you need multi-user controls 
- Enterprise platforms (Fireblocks, BitGo) start at $50,000-$100,000/year — too expensive 
- Third-party custodians require $10M+ minimums for full service 
- Multisig works but lacks policy enforcement, compliance reporting, and private governance 

This is the "Fireblocks gap." You are too sophisticated for MetaMask, too small for enterprise MPC. The result: most mid-market businesses cobble together Safe multisigs + Google Sheets + manual Slack approvals. It works until it does not.

83% of institutional investors plan to increase their crypto allocations ([EY / Coinbase Institutional Investor Survey 2025](https://institutional.coinbase.com/)). The mid-market will grow. The tooling needs to catch up.

### The governance checklist

Regardless of which custody technology you choose, your business needs documented answers to these questions:

#### Access control

- Who are the authorized signers? 
- What is the approval threshold (e.g., 2-of-3)? 
- Are there spending limits that require additional approvers? 
- Is there a maximum single-transaction limit? 

#### Key management

- Where are keys stored? (Hardware, cloud, MPC fragments?) 
- Who has backup access? 
- How often are keys rotated? 
- What is the process when a key holder leaves the company? 

#### Recovery and succession

- What happens if one key holder becomes unavailable? 
- Is there a dead man's switch or time-locked recovery? 
- Who is the backup signer? 
- Is the recovery procedure tested regularly? 

#### Compliance and reporting

- Is there a complete audit trail of all transactions? 
- Can you produce transaction records for tax reporting? 
- Does your custody arrangement meet the requirements of your jurisdiction? 
- Are assets properly segregated from company operational funds? 

#### Incident response

- What happens if a signer's device is compromised? 
- Who do you contact? What is the response time? 
- Is there a freeze mechanism for suspicious transactions? 
- When did you last test your incident response plan? 

If you cannot answer all of these questions, your custody arrangement has gaps. The technology does not matter if the governance is not there.

### What regulations require

The regulatory landscape shifted dramatically in 2025-2026. Businesses holding crypto now face real compliance requirements in most major jurisdictions.

| Jurisdiction | Key requirement | Effective |
| --- | --- | --- |
| United States | SAB 122 repealed accounting barriers for bank custody. OCC Letter 1183 authorized national banks for crypto custody. SEC No-Action Letter (Sep 2025) clarified broker-dealer obligations. IRS broker reporting starts 2026. | 2025-2026 |
| European Union | MiCA requires licensed custody providers, segregation of assets, and operational resilience standards. | Dec 2024 |
| Hong Kong | SFC licensing regime for virtual asset trading platforms. Stablecoin Ordinance (Aug 2025). | 2024-2025 |
| Singapore | MAS licensing under Payment Services Act. Upcoming custody-specific regulations. | 2024-2026 |
| UAE | VARA framework in Dubai. ADGM in Abu Dhabi. Comprehensive licensing for custody providers. | 2024-2025 |

The common thread across all jurisdictions: maintain a complete audit trail, ensure asset segregation, and have documented governance procedures. The era of informal crypto custody is ending.

For a detailed breakdown of regulatory requirements by jurisdiction, see our [comprehensive custody solutions guide](https://vastlink.xyz/blog/crypto-custody-solutions-guide-2026/).

### How to choose — a decision framework

Start with your situation, not with the technology.

| Your situation | Recommended approach | Monthly cost estimate |
| --- | --- | --- |
| Solo founder, under $50K | Hardware wallet + documented seed phrase backup | $0 (after $150 hardware) |
| Small team (2-5), $50K-$500K | Multisig (Safe) with 2-of-3 threshold | $0-100 |
| Growing business, $500K-$5M | Multisig + MPC key management, or mid-market custody platform | $500-3,000 |
| Regulated entity, $5M-$50M | MPC platform with compliance tools | $3,000-8,000 |
| Institution, $50M+ | Enterprise MPC + third-party custodian | $8,000+ |

Notice: the recommendation is not based on technology preference. It is based on your business context — team size, asset value, regulatory requirements, and operational complexity.

As your business grows, your custody should evolve with it. A startup that begins with a Ledger and ends up with a full governance stack has done it right. The mistake is staying at a consumer-grade solution after you have outgrown it.

### FAQ

#### Does my business need a crypto custodian?

If your business holds more than $50,000 in digital assets, or if more than one person needs to authorize transactions, a formal custody arrangement is strongly recommended. Below that threshold, a hardware wallet with documented key management procedures may be sufficient. The deciding factor is not the amount — it is the number of people and processes involved.

#### How much does crypto custody cost for a small business?

Self-custody with hardware wallets costs $150-500 upfront. Software-based multisig solutions are typically free or under $100/month. Third-party custodians charge 0.05%-0.50% of assets under custody annually, plus transaction fees. Enterprise MPC platforms start at $50,000-100,000/year. For businesses holding $500K-$10M, the sweet spot is usually a combination of multisig governance and MPC key management, costing $1,000-$5,000/month.

#### What happens to business crypto if the CEO leaves or dies?

Without a documented succession plan, assets may become permanently inaccessible. Every business holding crypto needs: a minimum 2-of-3 or 3-of-5 authorization threshold, documented key recovery procedures, and a time-locked recovery mechanism. This is the single most common point of failure for business crypto.

#### Can a business use a regular crypto wallet?

Technically yes, but it creates serious risks. Consumer wallets lack multi-user approval workflows, audit trails, spending limits, and role-based access. If an employee with wallet access leaves, there is no way to revoke their access without moving all assets. For any business with more than one person involved in crypto operations, a business-grade solution is necessary.

#### Do businesses need to report crypto holdings?

Yes, in most jurisdictions. In the US, businesses must report crypto on tax returns, with IRS broker reporting starting 2026. The EU's MiCA requires transaction records. Hong Kong's SFC requires proper custody arrangements. The key requirement everywhere: maintain a complete audit trail.

#### What is the safest custody option for business crypto?

There is no single safest option — safety depends on governance, not technology. A well-governed multisig is safer than a poorly-governed MPC system. The safest approach combines threshold authorization, documented recovery procedures, and regular security audits. Technology is the implementation detail. Governance is the foundation.

---

## Crypto Custody Solutions: What Institutions Need to Know in 2026

Source: https://vastlink.xyz/blog/crypto-custody-solutions-guide-2026/  
Published: 2026-07-01

If you hold digital assets for your business — as a fund manager, a treasury operator, a CEO — this is for you.

### The real problem

$3.4 billion in crypto was stolen in 2025. The year before, $2.2 billion across 303 incidents ([Chainalysis](https://www.chainalysis.com/blog/2025-crypto-crime-report-introduction/)).

The #1 attack vector? Private key compromise. It accounted for 43.8% of all stolen crypto in 2024. Infrastructure attacks (exchange breaches + key compromises) made up over 80% of stolen funds in H1 2025 ([Chainalysis](https://www.chainalysis.com/blog/2025-crypto-crime-report-introduction/)).

Recovery rate dropped from ~16% in 2024 to ~8% in 2025 ([PeckShield](https://peckshield.com/)). Once crypto is gone, it is almost always gone.

The FBI reported $11 billion in US crypto fraud in 2025 alone — 181,565 complaints ([FBI IC3](https://www.ic3.gov/AnnualReport/Reports/2024_IC3Report.pdf)).

Custody is not really a technology problem. It is a governance problem.

![Crypto custody governance framework — how custody, policy, and recovery layers interact in a digital asset operating system](https://vastlink.xyz/blog/crypto-custody-solutions-guide-2026/assets/p1.png)

### Why crypto custody is fundamentally different from traditional custody

If you come from traditional finance, custody is simple. A bank holds your assets. Something goes wrong — there are reversals, insurance, regulators. Layered protections.

Crypto has none of this by default.

**QuadrigaCX:** The sole key holder of the exchange died. C$215.7 million in customer assets became permanently inaccessible. No backup. No recovery. The funds are still locked today ([Ontario Securities Commission](https://www.osc.ca/quadrigacxreport/)).

**FTX:** Customer funds commingled with proprietary trading. $8 billion customer shortfall. $12.7 billion judgment ([CFTC](https://www.cftc.gov/PressRoom/PressReleases/8938-24)).

**Bybit (Feb 2025):** $1.5 billion stolen — not by breaking the cryptography, but by compromising the signing UI. The approval process was the vulnerability ([FBI IC3](https://www.ic3.gov/AnnualReport/Reports/2024_IC3Report.pdf)).

These are not edge cases. These are what happens when custody is treated as a technology checkbox instead of an operational discipline.

#### Traditional custody vs. crypto custody

|  | Traditional Assets | Digital Assets |
| --- | --- | --- |
| **Reversibility** | Transactions can be reversed | Blockchain transactions are final |
| **Recovery** | Lost credentials can be reset | Lost private keys = permanently lost assets |
| **Insurance** | FDIC/SIPC coverage is standard | Coverage is limited and expensive |
| **Regulation** | Decades of established custodial law | Frameworks still emerging |
| **Single point of failure** | Distributed across institutions | One compromised key can drain everything |
| **Asset segregation** | Legally required, audited | Varies widely by provider |

### What has changed in 2026

The custody provider market reached $3.28 billion in 2025, projected to grow to $7.74 billion by 2032 at 12.95% CAGR ([360iResearch](https://www.360iresearch.com/)). Assets under custody in the broader digital asset custody market: $658 billion in 2025, projected $6,067 billion by 2036 at 22.6% CAGR ([Meticulous Research](https://www.meticulousresearch.com/)).

The numbers behind the growth:

- 741 million people globally own crypto ([Crypto.com](https://crypto.com/research)) 
- 140+ public companies hold Bitcoin — ~1.16 million BTC, over $120 billion ([Cryptopolitan](https://www.cryptopolitan.com/); [Bitbo](https://bitbo.io/)) 
- Bitcoin ETF AUM: $79.9 billion, 1,248,218 BTC ([WalletPilot](https://www.walletpilot.com/)) 
- 83% of institutional investors plan to increase crypto allocations (352 firms surveyed) ([EY/Coinbase 2025](https://www.ey.com/en_us/financial-services/institutional-digital-assets-survey)) 
- 55% of hedge funds now have crypto exposure, up from 47% in 2024 ([PwC/AIMA 2025](https://www.aima.org/article/press-release-crypto-friendly-regulatory-changes-accelerate-institutional-investment.html)) 
- 33% of family offices invest in crypto, up from 16% in 2021. Separately, 74% are either invested or actively considering ([Goldman Sachs 2025](https://www.goldmansachs.com/); [BNY Wealth 2025](https://www.bny.com/)) 
- 32% of financial advisors allocated crypto in 2025, up from 11% in 2023 ([Bitwise/VettaFi 2026](https://bitwiseinvestments.com/)) 

And custody is now the **#1 concern** for institutional investors — ranked above volatility, above regulatory uncertainty, above liquidity ([Nickel Digital Asset Management](https://www.nickel.digital/)).

#### The regulatory door has opened

January 2025: SEC rescinded SAB 121 with SAB 122 — removed the balance-sheet penalty that kept banks out of crypto custody ([SEC](https://www.sec.gov/)).

March 2025: OCC confirmed national banks can custody digital assets without prior approval ([OCC Letter 1183](https://www.occ.treas.gov/)).

September 2025: SEC no-action letter confirmed state trust companies can be qualified custodians ([SEC](https://www.sec.gov/)).

Banks are entering the custody market now. The question is no longer “can I get institutional-grade custody?” — it is “how do I choose?”

### Types of crypto custody solutions

Most guides throw around terms like MPC, multisig, HSM, cold storage without explaining what they actually mean for your business. Here is what matters.

#### Self-custody

You hold your own private keys. No third party has access. Like keeping cash in your own safe — full control, full responsibility. Best for crypto-native teams with strong technical capability.

#### Third-party custody

A regulated custodian holds your private keys. Like a bank vault. Best for institutional investors and regulated funds that need qualified custodians.

#### Hybrid / collaborative custody

Control is shared between your organization and a service provider. No single party can move assets alone. Best for institutions that want balance between control and security.

#### Comparison

|  | Self-Custody | Third-Party | Hybrid |
| --- | --- | --- | --- |
| **Control** | Full | Delegated | Shared |
| **Key risk** | Lose keys = lose assets | Counterparty risk | Complex coordination |
| **Cost** | Infrastructure + staff | Fees (basis points on AUM) | Varies |
| **Compliance** | You build it | Custodian handles it | Shared |
| **Best for** | Crypto-native teams | Regulated funds | Balanced control |

#### The technology — in a nutshell

You do not need to understand the cryptography. You need to understand what each approach means for your operations:

- **Cold storage** — keys kept offline, disconnected from the internet. Harder to steal, slower to use. 
- **Multisig** — multiple people must approve a transaction independently. 3-of-5 approval means no single person and no single compromised account can move funds. 
- **MPC (multi-party computation)** — private key is split into pieces held by different parties. The full key never exists in one place. Transactions require collaboration. 
- **HSM (hardware security module)** — physical device that stores keys and signs transactions in tamper-resistant hardware. Banks already use these for traditional payments. 

The technology choice matters less than the governance around it. A perfect MPC setup is useless if you don’t know who has the key shares, what happens when someone leaves, or how approvals work at 2 AM on a Sunday.

### The governance gap

The technology for securing private keys is largely solved. What is not solved is the governance layer on top of it.

These are the real operational questions:

- Who can approve a $1 million transfer? One person? Two? Does it change based on the amount? 
- What happens when your CFO leaves? How quickly can you rotate key shares or revoke access? 
- Who has access on weekends? If a market event requires immediate action, who authorizes it? 
- How are approval policies enforced? Through technology? Or through a group chat? 
- What is your audit trail? If a regulator asks who authorized a specific transaction six months ago, can you answer in minutes? 

The market is starting to notice. In 2026, 66% of institutional investors cited security and key-signing as a key factor when evaluating custodians — up from just 8% in 2025 ([EY/Coinbase 2026](https://www.ey.com/en_us/financial-services/institutional-digital-assets-survey)).

61% of institutions now use a multi-custodian model ([EY/Coinbase 2026](https://www.ey.com/en_us/financial-services/institutional-digital-assets-survey)). Different custodians, different interfaces, different approval workflows, different reporting formats. Many institutions manage all of this with spreadsheets and group chats.

That is basically a patchwork governance system.

If users are building workflows outside the product — Slack + spreadsheet + wallet — then the wallet is not solving the actual problem. The actual problem is governance.

### How to evaluate a crypto custody solution

Most evaluation guides focus on technology features. These are the questions that actually matter if you are the one accountable for the assets.

#### 1. Who controls the keys — and what happens if they are unavailable?

This is the most important question. Unlike a bank password, a lost private key cannot be reset.

- How many people or systems need to participate to authorize a transaction? 
- What is the recovery process if a key holder is unavailable, leaves, or is compromised? 
- Is there a succession plan for key access? 
- Has the recovery process been tested — not just documented? 

#### 2. What is the approval process for moving assets?

Weak approval processes are how the largest thefts happen (see Bybit).

- Are approval policies enforced by technology or by human process? 
- Can requirements change based on transaction size, destination, or time? 
- Is there an audit trail of every approval and rejection? 
- Can a single admin override the policy? 

#### 3. How does it handle your regulatory requirements?

Crypto custody regulation varies by jurisdiction and is changing fast.

- Is the custodian licensed where you operate? 
- Does it support the asset segregation requirements of your jurisdiction? 
- Can it produce the reports your auditors and regulators need? 
- How does it handle regulatory changes? 

#### 4. What does the insurance actually cover?

The crypto insurance market reached $9.49 billion in 2025, projected to $192.72 billion by 2033 at 45.8% CAGR ([Grand View Research](https://www.grandviewresearch.com/)). But coverage varies enormously.

- What is the total coverage vs. assets under custody? 
- Does it cover theft, hacking, employee fraud, and operational errors? 
- Are hot wallets and cold storage covered equally? 
- What is the insurer’s track record of actually paying crypto claims? 

#### 5. Can you switch providers without losing access?

Vendor lock-in is real in crypto custody.

- What is the migration process and timeline? 
- Are there lock-in periods or exit fees? 
- Can you run multiple custodians during transition? 
- Who controls the keys during migration? 

#### Evaluation checklist

| Category | Question |
| --- | --- |
| Key control | Recovery process documented and tested |
| Key control | Succession plan for key holders |
| Approvals | Policies enforced by technology |
| Approvals | Immutable audit trail |
| Approvals | Role-based access that updates with team changes |
| Regulation | Licensed in required jurisdictions |
| Regulation | Asset segregation independently verified |
| Insurance | Coverage amount relative to AUM |
| Insurance | Covers theft, fraud, operational errors |
| Portability | Migration process documented |
| Portability | No contractual lock-in |

### What regulations require

Crypto custody regulation has accelerated globally. Here is what matters by jurisdiction.

#### United States

- **SAB 122** (Jan 2025): Rescinded SAB 121, removed balance-sheet penalty for banks offering custody ([SEC](https://www.sec.gov/)) 
- **OCC Letter 1183** (Mar 2025): Banks can custody digital assets, hold stablecoin reserves, participate in blockchain networks — no prior approval needed ([OCC](https://www.occ.treas.gov/)) 
- **SEC No-Action Letter** (Sep 2025): State trust companies can be qualified custodians under the Investment Advisers Act ([SEC](https://www.sec.gov/)) 

#### European Union

- **MiCA**: EUR 125,000 minimum capital. Asset segregation, regular audits, governance policies required. 

#### Hong Kong

- **SFC**: 98% of client assets must be in cold storage. No commingling of client and proprietary assets. 

#### Singapore

- **MAS**: Asset segregation with daily reconciliation. SGD 250,000 minimum capital. 

#### United Arab Emirates

- **VARA**: 15% of client assets must be immediately liquid. Monthly stress testing. 

#### By jurisdiction

| Jurisdiction | Capital | Cold Storage | Segregation | Audit |
| --- | --- | --- | --- | --- |
| **US** | Varies by charter | No ratio mandated | Required | Varies |
| **EU (MiCA)** | EUR 125,000 min | Not specified | Required | Regular |
| **Hong Kong** | Per SFC license | 98% cold | Required, no commingling | Ongoing |
| **Singapore** | SGD 250,000 | Not specified | Required, daily reconciliation | Ongoing |
| **UAE** | Per VARA license | Not specified | Required | Monthly stress test |

### FAQ

#### What is crypto custody?

In a nutshell — it is the safekeeping of private keys that control digital assets on a blockchain. Whoever holds the private keys controls the assets. Custody solutions manage the storage, access, and authorization of these keys.

#### Hot storage vs. cold storage?

Hot storage means keys are on devices connected to the internet. Fast but more exposed to attacks. Cold storage means keys are offline — hardware devices, air-gapped systems. Much harder to hack, but slower to access. Most institutional setups use both: cold for the majority of assets, hot for operational liquidity.

#### How much does it cost?

Third-party custodians typically charge 0.05% to 0.50% of assets under custody per year, plus transaction fees. Self-custody requires hardware, software, security infrastructure, and specialized staff. Self-custody often costs more than third-party custody for institutions holding under $100 million.

#### Is crypto custody insured?

Some custodians offer insurance. The crypto insurance market reached $9.49 billion in 2025 ([Grand View Research](https://www.grandviewresearch.com/)). But coverage amounts are usually a fraction of total assets under custody. Verify: coverage amount, what events are covered (theft, fraud, operational errors), and whether hot and cold storage are covered equally.

#### What happens if a custody provider goes bankrupt?

It depends on whether client assets were properly segregated. Under most regulatory frameworks, segregated assets should not be part of the bankruptcy estate. But FTX showed that not all providers follow segregation requirements in practice. Verify that your custodian’s segregation is independently audited.

#### How do I switch providers?

Generate new key material with the receiving custodian. Transfer assets on-chain. Verify receipt. Decommission the old arrangement. It can take days to weeks. During migration, assets are briefly in transit on-chain — that is a window of elevated risk that needs careful management.

### Where this is going

The market is moving from “which wallet?” to “which governance model?” The progression looks something like:

- Beginner: Which wallet? 
- Intermediate: Which custody model? 
- Advanced: Which governance model? 

If you are reading this, you are probably at the advanced stage. You have already discovered that custody is not the real problem. Custody is one implementation detail inside a larger governance system.

The question is not: can one system support all these custody models? Technically, yes.

The real question is: who can move assets, under what conditions, with what recovery guarantees, under what compliance requirements?

Private keys, MPC, multisig, HSM, passkeys — these are implementation details. The primary abstraction is asset governance.

---

## Digital Asset Management Landscape Research 2025

Source: https://vastlink.xyz/blog/digital-asset-management-landscape-2025/  
Published: 2025-12-02

![](https://cdn-images-1.medium.com/max/1024/1*BSiUV8r8hKl1nnN1gqwdmA.png)

#### Executive Summary

In 2025, the digital asset management landscape is characterized by a rapid convergence of traditional finance (TradFi) and decentralized finance (DeFi). The era of siloed “crypto” and “fiat” operations is ending, replaced by a demand for unified treasury ecosystems. Institutions and corporations are moving beyond simple speculation to utilize digital assets for operational efficiency, real-time settlement, and yield generation. While solution maturity has improved significantly — driven by advancements in Multi-Party Computation (MPC) security and clearer regulatory frameworks like MiCA — the market remains fragmented. The next generation of solutions must solve the “bridge” problem: offering seamless, compliant, and instant interoperability between sovereign currencies and digital assets without the friction of legacy banking rails.

#### Market Overview: The 2025 Landscape

The digital asset market has transitioned from niche adoption to institutional integration.

- User Base: Global cryptocurrency users have surpassed 580 million, up from 562 million in 2024.
- Institutional Adoption: Approximately 55% of traditional hedge funds now have exposure to digital assets, a significant increase from 47% the previous year. Furthermore, 74% of institutional investors planned to increase their exposure in 2025.
- Corporate Treasury: Public companies are projected to allocate up to $330 billion to Bitcoin over the next five years. Stablecoins have become a critical liquidity tool, with the market projected to reach $500–750 billion by JPMorgan.
- Treasury Evolution: Corporate portfolios are evolving from static cash repositories to dynamic ecosystems blending fiat, bonds, and tokenized assets (e.g., tokenized U.S. Treasury bills yielding ~5%).

#### Current Solution Categories

##### 1. Unified Fiat-Crypto Platforms

These platforms represent the cutting edge in 2025, aiming to remove the distinction between asset types for the end user.

- Episode Six + Fireblocks: A partnership delivering a programmable platform that integrates fiat, stablecoins, and loyalty points, enabling banks to operate across asset classes on a single infrastructure.
- Deblock: A French-regulated platform offering a unified Euro current account combined with a self-custody crypto wallet, allowing users to spend both seamlessly.
- TrustLinq: A Swiss-regulated crypto-to-fiat payment platform allowing users to pay third parties in fiat directly from their crypto holdings without the recipient needing a crypto wallet.
- TransFi: A unified gateway for the US and UK markets, handling regulatory compliance (KYB) to allow businesses to accept both USD/GBP and digital assets via a single checkout.

##### 2. Institutional Custody & Treasury

Solutions designed for high-security, high-volume corporate needs.

- Fireblocks: The industry standard for MPC-based custody, used by banks and fintechs for treasury, trading, and policy controls.
- Coinbase Prime: A fully regulated U.S. financial custodian serving large institutions with integrated trading and prime brokerage.
- Gemini Custody: Offers segregated accounts with hardware security modules (HSMs) and insurance coverage.
- IBM Digital Asset Haven: A platform for secure, policy-driven keys and transaction management, designed for institutions requiring “hot,” “warm,” and “cold” tiers.

##### 3. Wallet Infrastructure (Custodial vs. Non-Custodial)

**Non-Custodial (Self-Custody):**

- *Hardware:* Ledger Nano S Plus, Trezor Safe 7, and Tangem (innovative card-based hardware wallet).
- *Software:* Best Wallet and RockWallet (features built-in fiat on-ramps).

**Custodial:**

- Exchange wallets (Binance, Kraken) offer convenience but carry counterparty risk.
- Luno and similar services provide beginner-friendly, bank-like experiences.

##### 4. Portfolio Tracking & Analytics

- CoinStats: Integrates 1,000+ exchanges and wallets for a unified view.
- Nansen: Provides on-chain analytics to monitor token flows and market trends.

#### Comparative Analysis: Pros & Cons

##### Custodial Solutions (Exchanges & Prime Brokers)

- Pros: High convenience, integrated liquidity for trading, built-in fiat on/off ramps, customer support, insurance (in some cases like Gemini).
- Cons: Counterparty risk (insolvency/hacks), regulatory friction (frozen funds), lack of true ownership (“Not your keys, not your coins”).

##### Non-Custodial / Self-Custody

- Pros: Absolute control over assets, censorship resistance, elimination of counterparty risk, privacy.
- Cons: High responsibility (lost keys = lost funds), poor UX for fiat conversion, technical complexity for average users.

##### Unified Hybrid Platforms (Next-Gen)

- Pros: Seamless spending of crypto as fiat, “banking-grade” compliance, simplified treasury management, real-time settlement.
- Cons: Reliance on banking partners (rails can be cut off), varying regulatory availability by region (e.g., available in EU/Swiss but harder in US).

#### Key Challenges in Current Solutions

Despite the advancements, builders of next-gen solutions must address significant friction points:

1. Fragmentation: Users still often require a bank account, a crypto exchange account, and a self-custody wallet to manage their financial life. Moving value between these silos is slow (T+1 to T+3 settlement) and costly.
2. Fiat-Crypto Interoperability: While “on-ramps” exist, true bi-directional flow is often blocked by risk-averse banking partners. The “off-ramp” experience is frequently cited as a major barrier (38% of potential users cite difficulties buying/selling as a barrier).
3. Compliance Burden: Navigating diverse regulatory regimes (MiCA in Europe, state-level rules in the US, VARA in Dubai) requires complex, dynamic compliance infrastructure that many current platforms lack.
4. Custody Risk Trade-off: Institutions want the security of cold storage with the liquidity of hot wallets. Current solutions often force a choice between safety (delayed access) and utility (risk of theft).
5. Legacy Infrastructure: Traditional banking rails (SWIFT, ACH) operate on limited hours and slow settlement cycles, bottling the efficiency of 24/7 blockchain networks.

#### Emerging Trends 2025

##### 1. Payment-versus-Payment (PvP) Settlement

Major trials, such as the Citi and Swift collaboration, have proven the feasibility of settling payments between fiat and digital currencies in a PvP workflow. This reduces settlement risk and bridges the gap between DLT networks and traditional financial systems.

##### 2. Institutional-Grade MPC

Multi-Party Computation (MPC) has become the standard for security. By splitting private keys into shares distributed across different devices/servers, MPC eliminates the “single point of failure” of private keys without the usability hurdles of multisig.

##### 3. Tokenization of Real-World Assets (RWA)

Treasury departments are increasingly holding tokenized U.S. Treasury bills and other yield-bearing real-world assets. Platforms allowing “intraday sweeps” between stablecoins (for working capital) and tokenized T-bills (for yield) are redefining corporate finance.

##### 4. Regulatory Standardization

- EU: MiCA (Markets in Crypto-Assets) provides a clear operating framework.
- US: The proposed CLARITY Act and Responsible Financial Innovation Act of 2025 are moving the US toward regulatory clarity.
- Accounting: FASB’s 2025 update allows companies to mark crypto assets at fair value, encouraging corporate adoption.

#### Opportunities for Next-Gen Solutions

For a new entrant building a digital asset management solution, the following areas represent high-value opportunities:

##### 1. The “Compliance-by-Design” Layer

Build infrastructure where compliance (KYC, AML, Travel Rule) is embedded at the protocol or smart contract layer. This allows for permissioned pools of liquidity that institutional investors can access without fear of regulatory backlash.

- *Model:* Automate tax reporting (Form 1099-DA) and real-time audit trails.

##### 2. Seamless “Spend-Anywhere” Liquidity

Create a non-custodial wallet that integrates directly with a debit card issuer or real-time payment rail (like SEPA Instant or FedNow).

- *Goal:* Allow a user to hold Bitcoin or Stablecoins and swipe a card at a grocery store with instant, background conversion, similar to Deblock or TrustLinq.

##### 3. Hybrid Custody Models

Offer a “Smart Vault” solution that utilizes MPC to give the user self-custody rights (unseizable) while allowing the platform to co-sign transactions for recovery and fraud prevention. This bridges the gap between security and user experience.

##### 4. Unified Corporate Treasury Dashboard

A B2B platform that views Fiat accounts, Stablecoin wallets, and Tokenized Treasuries in a single view, with automated rules for liquidity management (e.g., “Keep $100k in Fiat for payroll, auto-sweep excess into 5% yield Tokenized T-Bills”).

#### Technical Infrastructure Considerations

- Wallet Architecture: Move away from simple hot/cold wallets to MPC (Multi-Party Computation) wallets. This allows for policy engines (e.g., “Transaction >$10k requires CFO approval”).
- Ledger Integration: The system must run a double-entry ledger that can reconcile blockchain transactions (6+ confirmations) with banking transactions (pending/settled) in real-time.
- Chain Agnosticism: Support for cross-chain interoperability (Layer 0 protocols like Polkadot or CCIP) is essential. Users shouldn’t need to know *which* chain their USDC is on.
- API-First Approach: Utilize providers like SDK.finance or Fireblocks for the heavy lifting of ledger management and connectivity, focusing development resources on the unique UX and logic layer.

#### Regulatory Landscape Summary (2025)

![](https://cdn-images-1.medium.com/max/1024/1*gk25yBpVxDGlaAXkGzH1nQ.png)

---

## The fundamental problem with current crypto wallets (1)

Source: https://vastlink.xyz/blog/fundamental-problem-crypto-wallets/  
Published: 2025-10-29

![](https://cdn-images-1.medium.com/max/1024/1*T3cx4RcJW_mUcBEgE3oJpA.png)

**1. “Not your keys, not your coins!”**

It is what crypto is all about. Somehow on the flip side, it means “if I lose my keys, I lose my coins”.

Managing keys (private keys and seed phrases) is hard for everyone, yes everyone, from crypto natives to new comers.

**2. “Is it possible that I lose my keys, I don’t lose my coins?”**

The answer is “no”, as it is the way crypto works. But the question is valid, the point here is that I don’t want to lose my coins if I lose my keys.

If we ask the question in a different way, “Is it possible that I don’t have to manage my keys, so I don’t worry about losing them, meanwhile I still have control over my coins?”

The answer is “yes”, it is possible with technologies like multi-party computation (MPC) and threshold signature scheme (TSS) as well as account abstraction (AA).

**3. “How it works?”**

In a nutshell, we don’t have to manage our keys, they are still there behind the scene, but they are no longer exposed to us, or hackers either. We can use the methods we are familiar with, such as email, social accounts, mobile phone, Face ID and etc, to “log in to” a MPC or AA wallet to access our assets.

It is much more user friendly now, with security mechanisms such as multi-factor authentication (MFA) and withdrawal limits, it could offer bank-grade security for crypto now.

Somehow nothing is perfect, it introduces new risks and concerns.

To be continued …

---

## Vastbase FAQ

Source: https://vastlink.xyz/blog/vastbase-faq/  
Published: 2025-09-05

![](https://cdn-images-1.medium.com/max/946/1*TUE3BE87u_YLfSY2EiFDoQ.png)

**🙋‍♂️ What is Vastbase?**

> [Vastbase](https://vastbase.vastlink.xyz/) is a next generation multisig wallet for digital asset management and onchain businesses, such as: Crypto treasuries (in BTC, ETH, SOL, stablecoins, ERC-20, NFT, …) , RWAs, DAOs and VC funds.

> Vastbase is built on [Lit Protocol](https://litprotocol.com/), Lit Protocol is a key management network for decentralized signing and encryption.

**🙋‍♂️ What problems is Vastbase solving?**

> Vastbase solves key barriers to mainstream onchain business adoption: unsafe wallet setups, unintuitive user experiences, and unsustainable pricing models.

**🙋‍♂️ What is the solution?**

> ● Bank-grade security with [MPC](https://medium.com/@vastlink/decentralized-mpc-the-future-infrastructure-for-crypto-wallets-6daa887f4f4a) (multi-party computation) and [MFA](https://support.microsoft.com/en-au/topic/what-is-multifactor-authentication-e5e39437-121c-be60-d123-eda06bddf661) (multi-factor authentication)  
> ● Onboarding with email in 10 seconds  
> ● Email notification driven workflows  
> ● Cost-efficient “pay as you go” pricing model powered by tokenomics  
> ● Unlimited features via the marketplace  
> ● Open source and open infrastructures

**🙋‍♂️ Why build Vastbase?**

> After [the 1.4B Safe{Wallet} & Bybit hack](https://www.nccgroup.com/research-blog/in-depth-technical-analysis-of-the-bybit-hack/) in February 2025, we as a user of Safe{Wallet}, were looking for alternatives, and couldn’t find one, meanwhile a lot of people were looking for the same too.

> Then we partnered with [Lit Protocol](https://litprotocol.com/) to build Vastbase aiming to address the issues with current multisig wallet offerings.

> It was relatively faster to build Vastbase, because we built it on top of [Vastlink](https://vastlink.xyz), a next generation digital asset operating system for humans and AI.

**🙋‍♂️ Why partner with** [**Lit Protocol**](https://litprotocol.com/)**?**

![](https://cdn-images-1.medium.com/max/512/1*oYqfHUlCFjCI5tA0l16LhQ.png)

> Lit Protocol’s offerings make it possible for Vastbase to realize it’s vision.

> ● It’s MPC solution ensures security and removes single point of failure  
> ● Lit’s programmable private key management solution provides a perfect tech stack for Vastlink's key management solution to be built on  
> ● Lit is OSS, decentralized, and community driven

**🙋‍♂️ How Vastbase works?**

> 1. Use email to sign up and sign in  
> 2. Set up security as you go  
> 3. Invite others to your teams via email  
> 4. Raise and approve proposals by following email notifications  
> 5. Send and receive crypto via email  
> 6. Pay as you go, no subscription or upfront fees, no lock-in

**🔖 References**

- Vastbase explainer video

- Website  
[https://vastbase.vastlink.xyz/](https://vastbase.vastlink.xyz/)
- Explainer page  
[https://vastbase.vastlink.xyz/product-explainer.html](https://vastbase.vastlink.xyz/product-explainer.html)

---

## What can we learn from the biggest crypto hack in history — #Bybit’s 1.4B hack

Source: https://vastlink.xyz/blog/bybit-hack-crypto-security/  
Published: 2025-02-22

#### What can we learn from the biggest crypto hack in history — Safe{Wallet} & Bybit $1.4B hack

![](https://cdn-images-1.medium.com/max/1024/1*sZTgPS5NYBrxyD9X83PIFw.png)

⚠️ Putting a lot of assets in a single wallet itself is a huge risk, as well as a huge bait for hackers.

⚠️ Large amount and critical transactions should be protected by more than one security mechanisms, e.g. multi-sig + MFA.

⚠️ Operators need to follow rigorous operation processes, as technology can’t solve all human issues. It is hard to believe that all the signers’ machines got infected by the same malicious software.

💡 Hopefully MPC could make things better as the private key would never be exposed, and the mentioned security mechanisms can be built on the protocol level to prevent hacks like this.

---

## Decentralized MPC — The Future Infrastructure for Crypto Wallets

Source: https://vastlink.xyz/blog/decentralized-mpc-future-infrastructure/  
Published: 2024-12-04

#### 1. The terms

##### 1.1. What is MPC?

![](https://cdn-images-1.medium.com/max/850/1*K5tDyZzSuuhMhDv1SCLDig.png)

Multi-Party Computation, often abbreviated as MPC, is a cryptographic protocol that enables multiple parties to jointly compute a function over their inputs while keeping those inputs private. In simpler terms, it allows different entities to collaborate on computing a result without revealing their individual data.

> Source: [https://wirexapp.com/blog/post/multi-party-computation-mpc-explained-0856](https://wirexapp.com/blog/post/multi-party-computation-mpc-explained-0856)

##### 1.2. What is TSS?

![](https://cdn-images-1.medium.com/max/1024/0*UqX7sk4wnVYWbwPx)

Threshold Signature Scheme (TSS) is a cryptographic primitive for distributed key generation and signing. TSS is a sub-field of MPC.

Threshold signatures require a subset of parties authorised to produce signatures on behalf of the group. The message is only considered signed if a threshold (t out of n, t = threshold of signers, n = number of total signers) of signers sign off on the message.

> Source: [https://mmasmoudi.medium.com/an-overview-of-multi-party-computation-mpc-threshold-signatures-tss-and-mpc-tss-wallets-4253adacd1b2](https://mmasmoudi.medium.com/an-overview-of-multi-party-computation-mpc-threshold-signatures-tss-and-mpc-tss-wallets-4253adacd1b2)

##### 1.3. What is decentralized MPC?

![](https://cdn-images-1.medium.com/max/1024/0*cNUOQcOpC5T-AyPd)

In the first generation MPC protocols, for example in a 2 of 3 scheme, there are 3 key shares generated and kept by 3 parties, normally the user, the vender and the backup (managed by the user). Any 2 out of the 3 key shares can work together to complete transaction signing. It is much safer, also it mitigates the risk of single point of failure, compared to single private keys where you lose the key you lose everything. Somehow the user needs to put trust in a third party, also managing key shares is still a burden and risk for the user.

In the next generation MPC protocols, instead of a fixed number of parties managing the key shares, there would be a group of nodes running and forming a network, the key shares would be generated and managed among the nodes. Signing can be performed only when the access conditions are met and agreed by a certain percentage (as a threshold) of nodes.

Besides that, if the network is permissionless and open source, it would become a trustless and open infrastructure for people to build applications on, including crypto wallets.

#### 2. Decentralized MPC protocols & MPC-based infrastructures

**2.1.** [**Lit Protocol**](https://www.litprotocol.com/)

> (2024–02–02)  
> Mainnet Beta launched as per [https://developer.litprotocol.com/v3/network/migration-guide/](https://developer.litprotocol.com/v3/network/migration-guide/)

**2.2.** [**Ika**](https://ika.xyz/)** (pka** [**dWallet**](https://dwalletlabs.com/)**)**

> (2024–12–18)

![](https://cdn-images-1.medium.com/max/1024/1*6tV3PfrHlWgMposXOdKdnQ.png)

> (2024–03–05)  
> dWallet (formerly known as Odsy Network) works differently to the other decentralized MPC protocols, where only 1 share out of 2 is operated with MPC through a permissionless network of nodes, and the other share is held by the users. So that it is noncollusive meaning it is impossible that the nodes can sign without the user and collude and steal the assets.

> (2024–02–24)  
> Testnet launched as per [https://twitter.com/omersadika/status/1760736045233230320](https://twitter.com/omersadika/status/1760736045233230320)

**2.3.** [**Silence Labs**](https://www.silencelaboratories.com/)

> (2024–02–27)  
> [Silent Shard snap](https://cointelegraph.com/press-releases/silence-laboratories-brings-a-new-paradigm-of-security-for-metamask-users-distributed-self-custod), a MetaMask snap enabling 2FA alike security with MPC.

> (2024–01–03)  
> As per the meeting with Jay, the CEO, they have released a standalone SDK library for third parties to build their own MPC solutions.

**2.4.** [**Entropy.xyz**](https://entropy.xyz/)

> (2023–12–29)  
> They seem just released a library, not a decentralized MPC network yet, but they got backed by **a16z** and **Coinbase** venture. Dynamic.xyz also got backed by a16z.

**2.5.** [**Internet Computer Protocol**](https://internetcomputer.org/)** (ICP)**

> (2024–01–09)  
> - Check out “threshold ECDSA” on [https://github.com/dfinity/oisy-wallet](https://github.com/dfinity/oisy-wallet)  
> - Some questions and answers on GitHub [https://github.com/dfinity/oisy-wallet/issues/587](https://github.com/dfinity/oisy-wallet/issues/587)  
> - The Oisy Wallet built on ICP

**2.6.** [**ARPA Network**](https://www.arpanetwork.io/)

> (2024–01–23)  
> It supports EVM chains only.

**2.7.** [**Nillion**](https://www.nillion.com/)

> (2024–02–26)  
> Some questions are discussed on GitHub, good community support. Exploration is going on…  
> [https://github.com/orgs/nillion-oss/discussions/2](https://github.com/orgs/nillion-oss/discussions/2)

**2.8.** [**Passport Protocol**](https://0xpass.io/)** by 0xPass**

> (2024–06–07)

> J Labs has been working on a next generation crypto wallet POC on Passport Protocol, with the 0xPass team, since 2024–03.

> We have been working together with as well as getting help from the 0xPass team along the way. The overall dev experience has been awesome, they’ve been listening to our demands and feedback carefully, and getting back to us with solutions and help responsively. We feel promising building our wallet with Passport.

> (2024–03–09)

> By talking to the founder [Krish](https://www.linkedin.com/in/cskc1/) at 0xPass, its architecture, implementation and vision seem to be fine.   
> Currently supports EVM only, would support BTC and other chains in the future.

> Some questions are discussed on GitHub  
> [https://github.com/0xpass/passport-demo/issues/2](https://github.com/0xpass/passport-demo/issues/2)

> The demo  
> [https://demo.0xpass.io/](https://demo.0xpass.io/)

> (2025–07–01)  
> Accquired by Silence Laboratories

**2.9.** [**ContinuumDAO**](https://continuumdao.org/)

> (2024–07–01)  
> The First Decentralized MPC Network to serve as a public good. Governance of the network is managed through on-chain voting by ContinuumDAO

**2.10.** [**Zenrock**](https://www.zenrocklabs.io/)

> (2024–12–18)  
> Permissionless MPC infrastructure for all  
> Zenrock emerged from the 5-year-old institutional MPC custody solution Qredo  
> Zenrock holds all IP, assets, and developers from Qredo

**2.11.** [**Sodot**](https://www.sodot.dev/)

> (2024–12–18)  
> Self-custodial MPC Infrastructure

**2.12.** [**Vultisig**](https://vultisig.com/)

> (2025–07–01)  
> The Free MPC Wallet that makes seed phrases obsolete

**2.13.** [**Fystack**](https://fystack.io/)

> (2025–12–01)  
> Emerging self-hosted MPC Infrastructure based in Vietnam

**2.14.** [**io.finnet**](https://iofinnet.com/)

> (2026–07–20)  
> Blockchain and digital asset infrastructure based on MPC. End-to-end digital asset solutions for financial institutions

#### 3. References

**3.1.** [**Threshold Signature Schemes in blockchain: an introduction**](https://www.blockstrata.co/threshold-signature-schemes-and-mpc-in-cryptocurrency-an-introduction/)

> (2024–01–23)  
> - Threshold Signatures (TSS) vs. Multi-sig  
> - TSS vs. Shamir secret sharing scheme  
> - TSS — Current implementations

**3.2. Some other terms used for decentralized MPC**

> - permissionless threshold signatures (ARPA Network)  
> - decentralized threshold signatures (Internet Computer Protocol)  
> - decentralized key management and access control (Lit Protocol)

![](https://cdn-images-1.medium.com/max/1024/1*-7M-60zA1FdDIDwoK9O_vw.png)

[https://vastlink.xyz/](https://vastlink.xyz/)