Root docs
Repository viewer
Legacy docs parity surface
Back to repository viewer
Repository document

Use Case Packs

use-case-packs.md

Boundary

This route preserves legacy markdown access inside the Next.js surface. The raw repository file remains authoritative.

Open raw file

Use Case Packs

PrivateDAO now groups the strongest product stories into **use case packs** so judges, pilot users, and operators can map the same protocol to different organizations without changing the core system.

Each pack explains:

  • who the operator is
  • what kind of proposal they run
  • why private voting matters
  • where ZK, REFHE, MagicBlock, and the read-node path help
  • what the realistic pilot path looks like

Packs

  • [Grant Committee Pack](grant-committee-pack.md)
  • [Fund Governance Pack](fund-governance-pack.md)
  • [Gaming DAO Pack](gaming-dao-pack.md)
  • [Enterprise DAO Pack](enterprise-dao-pack.md)

Shared PrivateDAO base

All packs use the same base product:

  • DAO creation
  • treasury funding
  • proposal submission
  • commit-reveal vote lifecycle
  • finalize and execute
  • optional confidential payout plans
  • optional REFHE evaluation path
  • optional MagicBlock corridor path
  • backend-indexed reviewer and operator evidence

Why packs matter

Without packs, the repo can look feature-rich but abstract.

With packs, the same protocol becomes easier to understand:

  • one pack for grants
  • one for fund decisions
  • one for gaming and guild operations
  • one for enterprise internal governance

That helps Frontier judges and early pilots see PrivateDAO as a usable product, not only a protocol surface.