Project Registry
What the project and its evidence inventory are.
Mining compliance evidence infrastructure
MPC connects source authority, evidence versions, professional review, human decisions, public Registry projections, and integrity proofs—without treating any one layer as the whole truth.
Registry architecture
A project can complete a useful Registry workflow without becoming an issued asset. Each promotion requires evidence and a separately accountable decision.
What the project and its evidence inventory are.
Who reviewed which version, within what scope and limitation.
Asset Registry does not exist until separate legal and service-provider gates pass.
Evidence lifecycle
The value is not the number of integrations. It is the ability to reproduce where a claim came from, who reviewed it, what changed, and what was disclosed.
Authority scope, jurisdiction, validity, and what a source does not prove.
Credential, scope, assignment, expiry, revocation, and conflict.
Versioned evidence, method, limitation, freshness, and disclosure rules.
A signed review of one frozen evidence snapshot.
Versioned readiness assessment—not an approval engine.
A public Registry version committed for integrity verification.
Approved status, scope, limitation, version, and proof.
API, signed documents, exports, and manual receipts share one contract.
Jurisdiction rules remain outside the country-neutral core.
Trust boundary
One canonical record produces different projections. The chain carries a commitment, not the underlying documents.
Private
Public Explorer
BNB Chain