- Quantum Chain-specific post-quantum signing for every authorized transaction.
- QRC token support rather than ERC-style standards.
- A non-custodial model where keys live in an external signer, not in Qustody.
Compatibility matrix
What Qustody intentionally does not promise
- Drop-in compatibility. Qustody is not a re-implementation of any specific custody platform. URLs, schemas, and event names are similar in shape but are not byte-for-byte identical.
- ERC-named token standards. Qustody publishes QRC standards. If you migrate from a platform that uses ERC names, expect a translation layer at the integration boundary.
- ECDSA signing. Quantum Chain transactions are authorized with post-quantum signatures. ECDSA-only signers cannot produce valid Quantum Chain transactions.
How to migrate from a familiar custody platform
1
Map the resource model
tenant → vault account → wallet → asset balance aligns 1:1 with most institutional custody platforms.2
Translate Ethereum standard references to QRC
Any reference to the Ethereum equivalent of
QRC-20 in your existing configuration becomes QRC-20. The on-chain operations are the same shape; the standard name is different. The same mapping applies to every other QRC standard listed in token standards.3
Replace ECDSA signers with a post-quantum signer
Swap the signing component for a Qustody-compatible external signer (callback, gRPC, or remote). See external signing.
4
Re-bind webhooks
Subscribe to
transaction.* events for transaction lifecycle and token.* events for typed token operations.5
Re-evaluate approval policies
The approval-policy engine maps onto most multi-approver workflows. Re-encode your existing rules using the Qustody rule types.