How It WorksD6
Two governance spaces
Protocol governance and project governance are separated at the contract, storage, voter-roll and execution level — not merely on separate screens.
- Status
- Design stage
- Whitepaper basis
- §10.1 Protocol Governance Framework · §10.2 Platform vs. Asset Governance
- Verified on-chain today
- None — nothing here is deployed yet
- Still at design stage
- Protocol governance contract · Project governance contract · Quorum, delegation and timelock parameters
Protocol governance
MPC holders decide protocol policy
- Whether to support a project
- Fee policy
- Minimum data standards
- Reviewer pool criteria
- Framework revisions
- Protocol treasury
Project governance
Asset-token holders decide project matters
- Only matters the contract and AT structure permit
- For example, a sale-or-continue proposal
- Vote result and execution status are recorded separately
- Off-chain execution ends as executed, failed or disputed
Protocol governance cannot decide the disposal of an individual project's assets or rights. Project governance cannot change protocol policy or another project's rights.
Explicitly out of bounds for both
- Overriding a readiness result
- Approving a legal issuance
- Altering the rights attached to a different project
What this does not do
- A vote is never presented as legal completion of the matter it concerns.
- Governance participation is not framed as a return-bearing activity.
- Quorum, delegation and timelock values are not published as final while they remain open decisions.
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