Real-world assets.
Provably backed on-chain.
Bind an off-chain asset list to an on-chain portfolio with a custodian-signed attestation. Counterparties verify cryptographically, without ever seeing the assets themselves.
How it works
Four steps, one signature.
The attestation binds a portfolio to an asset-list hash. Everything except the hash + the signature stays off-chain.
01Agree on the asset list off-chain
You and your custodian settle the exact list of assets that back the portfolio outside the blockchain, in whatever format your compliance regime requires.
02Compute the canonical hash
Both sides independently hash the list via POST /api/custody · action:hash-assets. If your hashes match, you have a shared reference the chain can commit to.
03Custodian signs, you submit
Custodian signs a build-message payload with their enrolled ed25519 key. You submit the signature via rwa_custody_attestor::submit_attestation.
04Anyone verifies, no asset list required
Any counterparty calls POST /api/custody · action:verify with the attestation object id. They learn "yes, this portfolio is backed by an asset list this custodian signed". Nothing about which assets, nothing about the value.
Who this is for.
- Tokenized-treasury issuers
- Bind on-chain treasury bill wrappers to the actual custody holdings without revealing the position list.
- Real estate / receivables platforms
- Prove that a portfolio is backed by an underlying loan or property pool without disclosing borrower identities.
- Fund managers issuing on-chain shares
- Give LPs cryptographic proof of NAV backing at any point in time. Auditor-ready artifacts, no share leakage.
- Custodians serving crypto-native clients
- Sign attestations once. Every counterparty verification is a stateless off-chain call, no ongoing operational burden.
Engineering
Under the hood.
Onboard as a custodian.
Enrol your ed25519 signing key, run through hash-assets with a test payload, then start issuing attestations. 30-minute onboarding call.
Book onboarding call