DeliveryD10
MPC Registry dApp: Planned Scope and Development Status
The MPC Registry dApp remains in design and development; every item in the MVP scope is still a design. The MVP covers Registry operation: core registries, a Compliance Policy Engine and a Public Explorer. Purchase, subscription, transfer and custody functions are not built, not even behind a flag.
- Status
- Scope definition
- Whitepaper basis
- §12.1.1 2026: Foundations and Launch Preparation · §5.1 Five-Layer Mining RWA Architecture
- Verified on-chain today
- None. Nothing here is deployed yet
- Still at design stage
- Every item in the in-scope list below
What is planned for the MVP across the core registries, the Compliance Policy Engine and the Mongolia profile?
- Organisation- and project-level permissions with an audit record
- Project Registry and Verification Registry
- Authority & Trust Registry, Verification Party Registry, Attestation Schema Registry
- Evidence Adapter contract, Source Receipts, and handling for external failure and conflict
- Compliance Policy Engine with versioned assessments
- Material versions, provenance and change history
- Reviewer credential, review scope, signature and limitations
- Readiness separated from the human decision
- Impact tracing and suspension when material changes
- Public Explorer
- BNB Chain Registry proof
- Protocol and project governance, separated
- The Tsagaan Tolgoi reference workflow
- Mongolia Jurisdiction Profile: schema, states and manual fallback
What is deliberately absent from the MVP, including purchase, transfer and custody?
| Included now | Held back, with the reason |
|---|---|
| Registry operation end to end | Asset and Offering integration: waiting on legal, organisational, ERSP and security gates |
| Public Explorer with limitations shown | Investor eligibility and transfer whitelisting: belongs to an authorised provider, not to MPC |
| Registry anchor and inclusion proof | Any broader on-chain state: the first deployment is limited to the anchor on purpose |
| Mongolia jurisdiction profile | Additional jurisdictions: the core stays country-neutral so this is additive, not a rewrite |
- Included now
- Registry operation end to end
- Held back, with the reason
- Asset and Offering integration: waiting on legal, organisational, ERSP and security gates
- Included now
- Public Explorer with limitations shown
- Held back, with the reason
- Investor eligibility and transfer whitelisting: belongs to an authorised provider, not to MPC
- Included now
- Registry anchor and inclusion proof
- Held back, with the reason
- Any broader on-chain state: the first deployment is limited to the anchor on purpose
- Included now
- Mongolia jurisdiction profile
- Held back, with the reason
- Additional jurisdictions: the core stays country-neutral so this is additive, not a rewrite
What this does not do
- The MVP does not move money and does not hold assets.
- It does not implement an offering flow in any hidden or disabled form.
- It does not claim an institutional integration that has not been confirmed.
This chapter is a public adaptation of the internal product specification. Where the two differ, the specification and the whitepaper govern.
MPC dApp Guide · design & build stage · synthetic demo data