Custodial architecture
Independent custody, segregation and asset evidence.
- Authorization and permitted custody scope
- Legally assessed trust or segregation arrangements
- Gold allocation and bar-level records where applicable
An institutional blueprint for asset structure, identity, permissioned issuance and lifecycle controls.
Structure the security, confirm the documents and control the issuance instruction.
Connect verification and wallet eligibility to transfer checks throughout the lifecycle.
Keep investor records, reporting and programme events in one coordinated experience.
Redemptions, maturities and cancellations follow the rights and operational steps of each programme.
Illustrative operating model. Functions and legal rights depend on each programme.
Select a wallet, then test the example rules.
Interactive simulation. No wallet connection or on-chain transaction.
Sample wallet ASample wallet BService provider standards for the Meridium Architectural Framework.
Independent custody, segregation and asset evidence.
Assess the operator, control environment and assurance evidence.
Define the rights before the digital implementation.
Connect legal ownership records and permissioned ledger states.
Qualify the investor and associated receiving wallet.
Specify the implementation and readiness evidence.
Selection and integration criteria only. Counterparties, legal arrangements and production integrations are confirmed through programme-specific diligence and agreements.
Meridium’s framework uses open-standard references to specify token permissions, investor identity and credential verification.
The design baseline for identity-aware securities: an ERC-20-compatible token interface, identity registry and transfer-rule checks.
ERC-3643 specification ↗Reference model for issuer, holder and verifier roles, with credential status and verification requirements defined in the identity architecture.
W3C data model ↗Identity and claims architecture associated with the ERC-3643 framework. Any bridge to a W3C credential model needs an explicit mapping and validation.
Identity registry reference ↗These references define the architectural approach. Deployed contracts, credential interoperability, network selection and security evidence require programme-specific implementation and validation before issuance. No production conformance or certification is claimed here.
Start with the asset, investors and intended jurisdictions.