When Asset and Offering features open
Only after each real gate is separately evidenced — and after implementation, legal review and a security audit that follow, rather than precede, that evidence.
- Status
- Locked
- Whitepaper basis
- §15.2 MPC Token and Asset Token · §6.2 From Onboarding to Issuance · §15.3 Asset Issuance and Regulatory Responsibility
- Verified on-chain today
- None — nothing here is deployed yet
- Still at design stage
- Asset Registry · Offering interface · Transfer and eligibility integration
Conditions, each evidenced on its own
- A project-specific issuer and a host-country SPV
- Rights, and the legal bridge between the off-chain right and the on-chain record
- The applicable jurisdiction and a legal issuance decision
- Authorisation and a project contract for each required ERSP function
- Professional review, including reinforced environmental material
- Smart contracts and a security audit
- Investor and transfer whitelisting, custody and escrow agreements
- 01
Issuer, SPV, rights, legal bridge
Confirmed or pending, each with its evidence — never inferred from the presence of the others.
- 02
Jurisdiction and legal issuance review
Counsel or authority status returned with its own limitations.
- 03
ERSP authorisation and contract
Status per function and per jurisdiction. One authorised function does not carry another.
- 04
Contract and security audit
Audit result plus unresolved findings. Unresolved findings stay visible.
- 05
Asset integration
Only with all gates evidenced and a separate legal issuance decision submitted. Otherwise the project stays a Reference Registry entry with trading functions inactive.
Neither data readiness nor an MPC support decision can open Asset or Offering features. Those are inputs to a different judgment, owned by different people.
What this does not do
- No permissionless swap or pool interface is offered for an asset token.
- No projected yield, distribution amount or valuation is displayed anywhere in this path.
- MPC does not re-adjudicate suitability or legality on a provider's behalf.
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
