The succession layer for tokenized real-world assets.
Built for the Cleanverse Build: Trusted Assets Hackathon — RWA Track — on Monad Testnet.
Tokenization solved ownership. It didn't solve succession.
There's no standard way to transfer a tokenized real-world asset when its owner dies or loses capacity — while still respecting verified identity, compliance rules, and jurisdiction. Today that gap is patched with lawyers, custodians, and manual off-chain coordination.
Legacy lets an asset owner define a Legacy Plan while they're still in control: who inherits, how much, and under what conditions. When those conditions are met, the transfer executes on-chain — no manual intervention, no unverified handoff.
- CVA (A-Token) — the real-world asset is issued as a compliance-gated token via Cleanverse's
atoken/launch, carrying its compliance rule (tier, group, jurisdiction) with it. - CVI (A-Pass) — before a succession transfer executes, the beneficiary's identity is verified via
verify_apass. The transfer only proceeds if the beneficiary holds a valid, eligible A-Pass.
- Owner registers a real-world asset → issued as a CVA (A-Token)
- Owner creates a Legacy Plan → beneficiary, allocation, trigger condition
- On trigger, backend calls Cleanverse
verify_apassfor the named beneficiary - If verified,
SuccessionExecutortransfers ownership on-chain - Event emitted, viewable on Monad Testnet Explorer
contracts/
AssetRegistry.sol — AssetDNA record: owner, CVA ref, jurisdiction, plan ref
LegacyPlan.sol — beneficiary, allocation, conditions, plan status
SuccessionExecutor.sol — triggers transfer once CVI check passes
backend/
cleanverse.js — AES-encrypted calls to Cleanverse CVI/CVA API, acts as relayer
- Solidity, Hardhat
- Monad Testnet (Chain ID 10143)
- Cleanverse CVI / CVA API
- Node.js backend relayer
🚧 Built during the Cleanverse hacking window (Aug 8–9, 2026 UTC).
Solo build — xarkgg
MIT