Info / Governance Guide
⚠Non-binding Advisory·All DAO resolutions are advisory. Final authority rests with the board of Dcosmos PTE. LTD. (Whitepaper §5.5)
Governance Guide
PWR DAO decision flow — Layer B Advisor consultation + Board multisig ratification · Whitepaper §5.4
3-Stage Advisory Resolution
Whitepaper §5.41
Notice (Discourse)
Discourse forum post — Temperature Check + minimum 5-day discussion
Off-chain · Discourse
2
Snapshot Vote
7-day gasless vote — majority via Layer B voting power
Off-chain · Snapshot
3
Board Ratification
30-day review · Ratify / Reject / Modify / Hold · Reopen executes on-chain
Dcosmos Board
1. Voting Power
All votes are restricted to Layer B Advisors (1+ NFT holders).
- Class A:
vote_weight = total_nft_count - Class B:
vote_weight = total_nft_count
★ 10% single-voter cap — no wallet exceeds 10% of Layer B Total Weight. Enforced at contract level.
2. Advisory Proposal
General ProposalOff-chain record
Flow for general proposals (Phase 4 pricing, ops policies):
propose()— Advisor submits. 7-day vote window auto-startsadvisory_vote()— Cast for/against within 7 days- Snapshot result on Discourse + 30-day board deliberation
- Ratified → admin multisig executes the relevant instruction (e.g.
set_phase4_price)
3. Reserve · Reopen Remaining Allocation
Reopen ProposalAuto on-chain execution
Nodes are minted only after pre-sale confirmation. Reserve is the count of unminted allocations remaining.
- After 180-day cooling, Advisor may call
propose_reconversion() - TWAP Floor guard — proposed price ≥ prior 30-day TWAP ×1.0
- 30-day notice → 7-day vote
- If ratified, buyer calls
reconvert_node()(pay PWR → instant burn → new NFT mint / additional issuance)
★ Sunset: 730 days after Phase 4 close, remaining allocation is permanently retired via sunset_burn() (never minted).
4. KYC / Sanction
Every NFT transfer hard-rejects unless the recipient passes:
- KYC Tier 1 attestation (identity check + sanction clearance)
- OFAC/SDN/PEP clear (
sanction_cleared = true) - Within Cap (A: 10, B: 20)
★ Quarterly keeper bot rescreens via refresh_sanction(). Failure immediately blocks transfers.
5. Detailed Instructions
Full 28-instruction spec — see dev docs: Whitepaper v2.0 ↗