The short answer
What does this use case involve?
Institutional digital-asset treasury translates familiar governance into custody accounts, wallets, transaction policies and reconciled records. Technology can enforce permissions, but it cannot define risk appetite or replace accountable approvals. Start with asset purpose, legal ownership and operating limits, then select custody, liquidity and reporting infrastructure.
Where the current process breaks down
Digital assets introduce continuous markets, irreversible transfers, multiple custody models and fragmented records. Existing treasury controls must be translated into wallet permissions, transaction policies and evidence that finance teams can reconcile. Useful for corporate stablecoin balances, exchange and custodian accounts, tokenized cash products, collateral operations, market-making treasury and settlement wallets.
From input to outcome
How does the workflow operate?
The following is an illustrative operating model, not a claim about a specific deployment. Ownership, approvals and exception handling should be agreed before implementation.
- 01
Classify assets and accounts
Document why each asset is held, the owning entity, approved venues and wallets, valuation source, liquidity needs and applicable restrictions.
- 02
Set authority and limits
Map initiators, approvers and reviewers to transaction types and thresholds. Separate routine settlement from new-address, emergency and recovery actions.
- 03
Move and settle
Screen counterparties and destinations, verify transaction details independently and preserve policy evidence from request through finality. Apply counterparty and concentration limits.
- 04
Reconcile and review
Match custody statements and on-chain balances to the treasury ledger. Investigate breaks, monitor fees and exposures, and review dormant permissions and addresses on a schedule.
Build the operating stack
Which infrastructure is needed?
These capabilities may sit inside an existing system, a specialist service or an integrated platform. Map each one to a responsible owner; do not assume a single vendor covers every function.
- Institutional custody or wallet infrastructure
- Role-based transaction policy
- Liquidity and settlement connectivity
- Blockchain monitoring and screening
- Treasury ledger integration
- Incident and recovery procedures
Evidence and context
NIST key management guidanceGeneral cryptographic key-management guidance. It does not prescribe a digital-asset custody model or determine regulatory, accounting or fiduciary obligations.
Design for the exceptions
What can go wrong?
Key or credential compromise
Use appropriate cryptographic controls, separation of duties, protected recovery material and tested revocation procedures.
Unauthorized destination
Require independent address verification, allowlists or risk-based holds for new destinations and dual approval for policy changes.
Books diverge from on-chain state
Reconcile balances and transactions across wallets, custodians, venues and the general ledger with documented exception ownership.
When this is not the right fit
Do not hold digital assets operationally when the institution cannot establish legal ownership, accounting treatment, qualified staff, recovery authority or reliable valuation. Exposure through an appropriately structured third-party product may be more suitable.
A bounded first deployment
How should a team start?
Start with one workflow and named operational owners. A pilot should show that the process works through exceptions, not just that a transaction can succeed once.
- Select one legal entity, asset purpose and low-value account.
- Define the account hierarchy, signers, thresholds and emergency authority.
- Test a new destination, rejected transaction, lost approver and reconciliation break.
- Complete security, finance and legal sign-off before increasing limits.
What should the pilot measure?
- Unreconciled balances and time to resolve breaks
- Policy exceptions and unauthorized transaction attempts
- Liquidity availability, counterparty concentration and settlement failures
Set a baseline and acceptance thresholds before choosing technology. Include support effort and failed cases in the comparison, and validate the result with the teams that will operate it.
Procurement questions
What should you ask vendors?
- Who legally owns each account and asset balance?
- How are key recovery, staff departure and emergency policy changes controlled?
- Can every custody and on-chain movement reconcile to the treasury ledger?
Request evidence from comparable workflows, a clear responsibility matrix, integration documentation and an export or exit plan. Confirm current capabilities directly rather than relying on a category listing.
Relevant vendor directories
Common questions
Does MPC eliminate key-management risk?
No. MPC can change how signing authority is distributed, but credentials, policy changes, recovery, software and operator access still require controls.
Should every treasury asset use the same custody model?
Not necessarily. Institutions may separate long-term reserves, operating balances and exchange liquidity, with different limits and controls for each purpose.
Sources and further reading
Independent implementation guidance, not legal, investment or regulatory advice. Requirements depend on your product, jurisdiction and operating model.
Last updated