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

Submission Dossier

submission-dossier.md

Boundary

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

Open raw file

Submission Dossier

Purpose

This document is the shortest serious handoff for a judge, grant reviewer, investor, or diligence process.

For public competition routing and packet choice during the current cycle, pair this file with superteam-track-submission-matrix-2026.md.

PrivateDAO now combines protocol hardening, zero-knowledge proof surfaces, and a published cryptographic artifact integrity layer so reviewers can validate not only the protocol logic, but also the integrity of the evidence package itself.

It ties together:

  • what the protocol is
  • what the strategy framing is
  • what the security evidence is
  • what the live proof is
  • what the stablecoin treasury layer is
  • what additive V3 hardening proves
  • what remains outside the repo

Core Identity

PrivateDAO is a governance security system for private, replay-resistant, treasury-safe decision flow on Solana.

Its strongest commercial role is:

the confidential governance, stablecoin treasury, and reviewer-readable execution layer for organizations that need payments, grants, payroll, gaming rewards, and treasury decisions to stay governed from the browser.

What Is Proven Today

  • on-chain governance lifecycle
  • commit-reveal voting
  • timelocked execution
  • treasury validation
  • replay and failure-mode reasoning
  • live Solana Testnet proof
  • PUSD stablecoin treasury and billing lanes
  • dedicated Devnet proof for Governance Hardening V3 and Settlement Hardening V3
  • canonical release manifest
  • reviewer and operations verification gates
  • web and Android-native review surfaces

Strategy Package

Security Package

Live Proof Package

Stablecoin Treasury Package

Operations Package

Unified Verification

The current repository can be closed and checked with:

npm run verify:all

Honest Boundary

What still remains outside the current repository:

  • live strategy engine and performance history
  • external audit
  • production mainnet rollout
  • any protocol-v2 interface change intended to tighten currently documented operational guards

Honest V3 Boundary

The additive V3 path is now part of the repository's serious proof surface:

  • Governance Hardening V3 is Devnet-proven
  • Settlement Hardening V3 is Devnet-proven
  • both remain additive and do not reinterpret legacy objects
  • neither is presented as a production-custody or unrestricted-mainnet claim