Custody / Platform guide
Custody Vaults
Follow escrowed units through conversion, delivery and redemption, including their completion and return paths.
Workflow
Open a vault
Choose the vault type, amount, realize action and deadline.
Fund the escrow
Share units move into the program-owned escrow.
Trigger
The current authorized custodian triggers the lifecycle event.
Complete or return
Complete the event, or use its permitted return route after a positive deadline.
Details to check
Vault types and states
Custody vault types cover vesting, delivery escrow and redemption queues. Holder conversions and deliveries both use a delivery escrow, whose completion checks the holder’s identity passport. The lifecycle moves from Active to Triggered to Realized, with a separate revert path for an untriggered vault after its deadline.
Completion and return
Completion burns escrowed units and records the result. Once a positive deadline has passed, a holder return can be submitted permissionlessly for an Active or Triggered vault. Before then, operator actions require the current authorized custodian. Return eligibility and recipient checks still apply.
Delivery requests
Requesting delivery requires identity verification (KYC). Delivery deposits tokens into escrow. A completed return releases the holder’s recorded deposit; confirmed delivery burns the units. A holder’s refund may complete while the vault still contains someone else’s surplus. Review the actual request and transaction state.
Interrupted recording
If the wallet submitted a deposit or return but the app record is pending, keep the transaction receipt and retry recording the existing action. Refresh and verify the vault before sending anything again.
Conversion requests
Conversion requests track units escrowed for an off-chain conversion into company shares, which requires identity verification (KYC). They are returned if cancelled and burned once the conversion is executed.
Related reference
Read the shared rules for security and compliance and the legal structure that connects token terms to the underlying instrument.