Root docs
Repository viewer
Legacy docs parity surface
Back to repository viewer
Repository document
Migration Story
migration-story.md
Boundary
This route preserves legacy markdown access inside the Next.js surface. The raw repository file remains authoritative.
Open raw fileMigration Story
PrivateDAO is not positioned as a greenfield-only DAO product.
The migration story is:
- start with an existing governance or treasury process
- move the voting surface into commit-reveal governance
- move treasury execution into a deterministic DAO-controlled path
- add confidential payout flows only where they are truly needed
- preserve reviewer and operator visibility through runtime evidence
What can migrate first
- treasury approval process
- grant voting
- internal budget approvals
- contributor payment approvals
What can migrate later
- encrypted payroll
- bonus approvals
- REFHE-bound evaluation paths
- MagicBlock corridor settlement paths
Why the story works
This reduces migration risk because PrivateDAO does not force every organization to adopt every advanced feature at once.
The product can start as:
- private governance + treasury control
and then grow into:
- confidential organizational operations