dApp GuideRelease Order
DeliveryD13

How is the MPC Registry dApp sequenced, and what decisions are still open?

In what order will the MPC Registry ship? The Release Order chapter of the Mineral Project Coin (MPC) dApp Guide sequences R0 to R7 by precondition, not by date: R3 is the BNB Chain Registry anchor and proof verification, R5 the Mongolia profile and Tsagaan Tolgoi, and R6 asset integration only once its gates pass.

Status
Planning
Whitepaper basis
§12.1 Roadmap, Q1 2026 to Q1 2028 · §13.6 Forward-Looking Statements
Verified on-chain today
None. Nothing here is deployed yet
Still at design stage
R0 through R7 in full
  • Release
    R0 Foundation
    Result
    Authentication, organisation and project isolation, encrypted storage, audit and operational base
  • Release
    R1 Registry
    Result
    Authority, Verification Party, Attestation Schema, Project and Verification registries, plus the Public Explorer
  • Release
    R2 Lifecycle
    Result
    Provenance, compliance policy, readiness, the human decision, change and suspension handling
  • Release
    R3 Chain proof
    Result
    BNB Chain Registry anchor and proof verification
  • Release
    R4 Governance
    Result
    Protocol and project governance, separated
  • Release
    R5 Reference
    Result
    The Mongolia profile and Tsagaan Tolgoi run as a real workflow, within the confirmed scope
  • Release
    R6 Asset integration
    Result
    Asset and Offering integration: only once legal, organisational and ERSP gates pass
  • Release
    R7 Scale
    Result
    Multi-project, multi-jurisdiction and external self-service

This chapter does not fix release dates: each release starts once its team, budget, legal review and real project material are confirmed. Project-wide quarterly targets are published on the MPC Roadmap page (globalmpc.tech/roadmap).

Which legal, security and governance decisions are still open?

The product direction is settled. These items are not, and each needs a decision from a user, a legal expert, a security owner or an external body, not from whoever implements the module first.

  • Deployment jurisdiction and the authorisation requirements per function
  • Real ERSPs, their contracts, interfaces and personal-data handling
  • Governance quorum, delegation and timelock values
  • Reviewer selection method and qualification criteria
  • Data residency and ownership of encryption keys
  • Technology stack, cloud and RPC vendors
  • Fee, staking and slashing rates: who bears verification cost is settled, the values are not
  • Team, budget, SLA and release schedule
  • Precedence when a legal register and a chain record disagree
  • Mongolia's real authority and source inventory, access, use and republication rights
  • Credential issuer and status-check method, and the attestation schema approval procedure
  • Whether DID, VC, OpenID4VC, vLEI or SD-JWT enter the adapter stack

Why doesn't the initial release sequence depend on DID or ZK?

A user does not need a DID to hold a credential and sign an attestation with a key they control. The MVP works with key and wallet signatures, issuer-signed credentials, identity and organisation binding, scope, jurisdiction, expiry, revocation, assignment and key rotation. DID and the VC/OpenID family become adapter candidates when portability across multiple issuers and wallets, or a persistent identifier, is actually required.

A zero-knowledge proof does not establish a reviewer's authority, the truth of source material or a legal right either. It is considered after R6, for cases such as investor and transfer eligibility where a specific condition must be proven without exposing sensitive source data, and only when an ordinary signed status or selective disclosure will not do, after legal, privacy, performance and audit review.

What this does not do

  • No release date is committed here.
  • No technology choice is presented as settled while it remains an open decision.
  • The roadmap does not add promises the whitepaper has not already made.

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