Listen to this page
Legacy Voice Guide · TROPTIONS + Deepgram
Wallet Infrastructure
Legacy Vault Protocol registers owner, executor, and beneficiary wallet maps across all major chains through the TROPTIONS wallet identity model — without ever holding private keys, seeds, or sensitive credentials.
Chain Coverage
TROPTIONS / TSN
TROPTIONS Wallet
Owner-registered TROPTIONS wallet address within the TSN identity model. Primary namespace owner identity.
Custody
Owner holds private key. Never stored in Legacy system.
XRPL
XRPL Wallet Reference
XRP Ledger wallet address registered for trustline and cross-chain asset references. bridge-xrpl adapter routes proof packets.
Custody
Owner holds seed. Only public address stored in vault manifest.
Stellar
Stellar Wallet Reference
Stellar public key registered for asset trustline references and cross-chain proof packets. bridge-stellar adapter handles routing.
Custody
Owner holds seed. Only public key stored in vault manifest.
EVM (Ethereum/Polygon/Base)
EVM Wallet Reference
Ethereum-compatible address for USDC, USDT, DAI, EURC holdings and DeFi asset references.
Custody
Owner holds seed phrase. Only public address stored in vault manifest.
Solana
Solana Wallet Reference
Solana public key for SPL token and NFT references. Executor packet includes Solana transfer instructions.
Custody
Owner holds seed phrase. Only public key stored in vault manifest.
All chains
Executor Wallet Map
Executor-specific wallet references authorized to receive transfer instructions upon release. Multi-chain coverage.
Custody
Executor holds keys. Legacy generates signed transfer instruction packets only.
All chains
Beneficiary Wallet Map
Per-beneficiary wallet references for scoped access packets. Each beneficiary sees only their allocated wallets.
Custody
Beneficiary holds keys. Legacy generates scoped access packets only.
Security Model
Raw seed phrases are never stored, collected, or transmitted by Legacy Vault Protocol
Only public addresses / public keys are registered in vault manifests
Private key discovery of unknown wallets is not performed
Wallet maps are owner-authorized — only wallets you explicitly register appear
All wallet references are encrypted client-side before IPFS storage
Executor transfer instructions are generated as signed packets — not live on-chain transactions
TROPTIONS x402 meters wallet snapshot generation — billed to the namespace