Verification is not guarantee
Every status word in the product has a ceiling. This chapter states each ceiling explicitly, because a term that quietly expands is worse than no term at all.
- Status
- Design & build stage
- Whitepaper basis
- §15.4 Mining RWA and Verification Risk · §15.6 Forward-Looking Statements · §11.1 Multi-Layer Trust Framework
- Verified on-chain today
- None — nothing here is deployed yet
- Still at design stage
- RegistryAnchor contract · Inclusion proof verifier
| What the dApp displays | What it does not mean |
|---|---|
verified | That everything in the document is true |
ok | Automatic approval, or confirmed eligibility to issue |
registered | Legal effect, or a completed issuance |
supported | An investment recommendation or a suitability finding |
| A successful BNB Chain proof | The truthfulness, profitability or legal effect of the underlying document |
| Confirmation from an official source | Anything outside that body's authority scope, or the legality of the project as a whole |
| A valid credential | That the reviewer was assigned to this project, was independent, or was correct |
- What the dApp displays
verified- What it does not mean
- That everything in the document is true
- What the dApp displays
ok- What it does not mean
- Automatic approval, or confirmed eligibility to issue
- What the dApp displays
registered- What it does not mean
- Legal effect, or a completed issuance
- What the dApp displays
supported- What it does not mean
- An investment recommendation or a suitability finding
- What the dApp displays
- A successful BNB Chain proof
- What it does not mean
- The truthfulness, profitability or legal effect of the underlying document
- What the dApp displays
- Confirmation from an official source
- What it does not mean
- Anything outside that body's authority scope, or the legality of the project as a whole
- What the dApp displays
- A valid credential
- What it does not mean
- That the reviewer was assigned to this project, was independent, or was correct
AI assists with extraction, classification and anomaly detection. It does not replace a professional's signature, a legal judgment or an investment judgment.
What goes on-chain, and what never does
On BNB Chain
Commitments only
- Merkle root and hash of a Registry version
- Batch, schema and rule version references
- Governance vote results and contract state
- New state records announcing a correction or revocation
In private systems
Everything with a subject
- Source documents and contracts
- Detailed geological coordinates and trade secrets
- Personal data and KYC material
- Whistleblower information and reviewer working files
- Raw third-party API responses and receipt detail
- Credential originals, API credentials and secrets
The first on-chain deployment is deliberately narrow: a RegistryAnchor and inclusion proof, nothing else. The chain answers one question — was this record part of that version, and has it changed since. It does not adjudicate the content.
What this does not do
- No personal data, contract text or raw source response is written to a public chain.
- The product does not describe a chain proof as an audit, a certification or an endorsement.
- No reserve or grade figure is published before the corresponding competent-person report exists.
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