- Native support for the CIP-0056 token standard for interoperability with institutional stablecoin issuers: holdings are referenced directly, never wrapped or bridged into a synthetic asset
- Release quorum: fund release can require an n-of-m signature threshold from independent release approvers, enforced by the ledger’s native multi-party signatory model, with no separate multisig infrastructure to operate or trust. The quorum can rise with the amount (for example, two approvers from 10,000 and three from 100,000), and an escrow agent can name its own officers as the default approvers, so larger releases need more of the institution’s keys
- Directed release: once a milestone is verified, the escrow agent directs its release and the asset custodian executes it. Each milestone sets when a direction can be executed (at once, after a challenge window in which a party can still dispute, or only once the parties approve), and a dispute pauses it
- Limits by kind of proof: the agreement sets the largest release each kind of evidence (an oracle signal, attested proof, audited proof) may unlock on its own; above it the depositors and beneficiaries approve. The escrow agent’s automation also works only up to an amount per release in each currency, above which the release waits for the parties
- Co-holders and document examination: a bank named in a letter of credit, or an export-import bank, can co-hold the money and countersign each release. A co-holder named as examiner checks the presented documents first; if they don’t comply, the release is held until the depositor waives the discrepancies or new documents comply (UCP 600 practice)
- Holds that expire: when the money is held by a lock that expires (a token-standard allocation), each escrow shows how long it is held and by when it must be renewed; automatic holds are renewed ahead of time, and every party is alerted if a renewal is overdue or fails
- Reserve attestation, human-countersigned: a reserve snapshot is only valid once an independent Auditor party co-signs it on-ledger, not merely claimed by the asset custodian
- Hybrid settlement rail routing: one contract can settle on-chain (stablecoin) or off-chain (ACH, RTP, FedNow, wire, via a swappable fiat-payments-orchestration integration) per disbursement leg, without the ledger needing to know rail-specific mechanics like batch windows or cutoffs
- Asset custodian per currency: the asset custodian and stablecoin rail for a given leg are resolved per currency, not fixed for the whole contract, so a single multi-currency deal clears each leg through the asset custodian actually licensed for that currency
- Settlement-triggering signatures are proofed through hardware-backed key management (KMS/HSM-class), never software-only keys. Every institution (each escrow agent and asset custodian) signs its own transactions with its own key, with an offline root key and a signing key that rotates without changing the institution’s identity on the ledger
- Escrow agent per escrow: each contract names its escrow agent (no single platform-wide one), and a release quorum governs releases and sweeps to registered destinations. The asset custodian is the issuer of the holding that funds the escrow, among the issuers recognized for its currency
- Funding backers on record: a bank, underwriter or insurer standing behind the depositor’s funds is recorded with its backing type and risk tier, so a letter of credit and on-chain collateral are never treated as equivalent
- Guaranteed fiat settlement: a named underwriter (the asset custodian or a correspondent bank) attests a guarantee, modeled on standby letter-of-credit practice (ISP98); once the asset custodian and the underwriter both approve, the beneficiary is paid over the fiat rail. Verified for holdings the asset custodian issues; real-money use is gated on compliance and legal sign-off
- Funding that fits the final cost: the agreement records an estimate and, optionally, a ceiling, and funds either one. At close-out the final amount is set by a statement the parties ratify, or certified by the verifier within a band they agreed in advance; the beneficiaries are paid what is due and the remainder is refunded to the depositors in the same settlement. When the final cost is higher, the escrow agent calls a true-up with a deadline (early only for a milestone the locked funds cannot cover); a missed true-up is declared a default and goes to dispute. Above the ceiling, the parties amend the agreement
- Who bears the network fee is a contract term (depositor, beneficiary or shared), mirroring the OUR/BEN/SHA charge options of international wire payments
- Integration with institutional digital-asset custody providers for real disbursements to external wallets, alongside ledger-native holdings
- Funding choice per depositor: a verified deposit with the asset custodian today (a real per-tenant custody wallet, checked and reserved before anything is minted), with a depositor-owned-holding lock-in-place path specified as the roadmap alternative — see Promise & Lock below
← Back to Tripart overview
Platform capabilities
Settlement & Custody
LiveAssets are held as real token interfaces, never as a numeric balance the platform tracks itself, and settlement rail is a choice per leg, not a fixed medium for the whole contract.