Skip to content
MPCEvidence Registry

Mining compliance evidence infrastructure

Evidence that can be traced. Decisions that remain accountable.

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

Three registries. Different responsibilities.

A project can complete a useful Registry workflow without becoming an issued asset. Each promotion requires evidence and a separately accountable decision.

01registered

Project Registry

What the project and its evidence inventory are.

02published

Verification Registry

Who reviewed which version, within what scope and limitation.

03not_activated

Conditional Asset integration

Asset Registry does not exist until separate legal and service-provider gates pass.

Evidence lifecycle

Nine structures form one 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.

01

Authority & Trust Registry

Authority scope, jurisdiction, validity, and what a source does not prove.

02

Verification Party Registry

Credential, scope, assignment, expiry, revocation, and conflict.

03

Attestation Schema Registry

Versioned evidence, method, limitation, freshness, and disclosure rules.

04

Verification Attestation

A signed review of one frozen evidence snapshot.

05

Compliance Policy Engine

Versioned readiness assessment—not an approval engine.

06

Evidence Snapshot + Anchor

A public Registry version committed for integrity verification.

07

Public Explorer

Approved status, scope, limitation, version, and proof.

08

Evidence Adapter Framework

API, signed documents, exports, and manual receipts share one contract.

09

Mongolia Jurisdiction Profile

Jurisdiction rules remain outside the country-neutral core.

Trust boundary

Sensitive evidence stays private. Public claims stay explainable.

One canonical record produces different projections. The chain carries a commitment, not the underlying documents.

Private

Encrypted evidence

  • Raw source responses
  • Contracts and PII/KYC
  • Detailed coordinates
  • Reviewer work material

Public Explorer

Approved projection

  • Status, version, and as-of
  • Authority scope
  • Review scope and limitation
  • Correction and proof references

BNB Chain

Integrity commitment

  • Root and batch reference
  • Schema and rule version
  • Publish/revoke/supersede event
  • No raw documents or PII