Proof Center

The Next.js app exposes the same proof story as the current site, but inside a cleaner operational shell: baseline live proof, dedicated V3 hardening proof, integration packets, and explicit launch boundaries.

Open command center Open dashboard Open curated docs

Judge runtime logs

Real Devnet execution logs, not summary-only proof

Freshness

3d old

The judge route now exposes real proposal and settlement signatures from the indexed Frontier evidence and the dedicated V3 hardening proof. This keeps the review surface tied to actual Devnet execution instead of packet summaries alone.

Governance path logs

Proposal AegjmwkX1FknBJMDyH5yM6BMhyHsiUreNtz3d8iz3QrP · verified-devnet-governance-path

create-dao

finalized

5mcyVi3SbZo4hvpVMjH2eZH8FYeywdbbPz4ArmE5wHXH5X9EnP6gSq76ogBWYWVkVUwzrCchPnSdhGV1mFb48s5Q

slot 453103934

deposit

finalized

KHWqfteEQhsH7hk7onQymbmnYdtF8rLoPWwchoQz5XFy8eY3DufeaX8DPiiVS1or7XkMVjMrbH2rsEhPtrPfzi9

slot 453103942

create-proposal

finalized

E93ikMXVJbtvz8ewAHA2BasZPVKYyUXe3Jy88h3b3AQubm7PSYFMNtDveBkRts7uYodwzb8cGZSVDoneKF16X2L

slot 453103948

commit

finalized

3RMbrcYGx297hgcTrov9PqtUqM97ZFg6A21qxmepTboLQAoXov6toY2QTa8yU1i8zmQPvjR3ArNGpvR3jat79uTP

slot 453103951

reveal

finalized

5L3cxZZgwMRnJTxNXLQCyjQMXSAi6bwoskFoKsfaQ7JycYUPuGCkWAkr7qA18WkddfNdSPB5qHt3FVSiHq2eDGh5

slot 453104032

finalize

finalized

4JSPRJQuSY5es74TcChBTzuGMMCr4RknHkmr6vFmtmbav4TRABDAnapmtgipYioEZzh4wmKfg2PMzZHCfJ7UruLG

slot 453104044

execute

finalized

x1vhP6H3Regi6WHYx6LUGbeo4CCbJxWwtUVucPVjonnymyccpM8mpb7t3UpQpqksXBU7PYGPd86cPnZLYwRzBn9

slot 453104062

Confidential payout logs

Proposal 52UpWHJodPWQzpR8u2qqpgwo3jRB7mvjgwCnf8oSJuXX ·

magicblock-deposit

finalized

3FV1LENXhfzktPUQh6rK1mRhEk4aJf2snFhfMSK3nLM4au2y4n1smbEGCEWr5x8kJ7t86ZcAivB5HhsMqMWpkRJC

slot 453755521

magicblock-private-transfer

finalized

662meytSDxGaCpkkkvMwqo6ZLFNvbC8jswHUw4sCaJmaYpov1995Xoik97CoWUHu6vvYigNdvfWSGBMfktzwbRr4

slot 453755612

magicblock-withdraw

finalized

23VxsHqP9aDWTLCdPmRep5UxRXzj9mpvR9B5HGDC8Nt9tKNrVxiwCHCpzm7BLHg8TrChdpmx4awtHyUEW1QPdEBC

slot 453755711

magicblock-settle

finalized

56zD3JYxYssgAkSsmxoh2zGzs11SakCXmUviMF53rdHy1HHcNQGqq72Jo9cbww2m67k7XsD5gqTB42HXMC8YEHHM

slot 453755859

magicblock-execute

finalized

LoNED2YKkYWxaQbFV4y8fCzqGi5YrpPSruJYppqfvcTyAJ2zU5HM92QEsPNydQb26abE7qp2kB7hCNPJFbVUUPA

slot 453757637

V3 hardening proof capture

test-wallet-devnet-proof-v3 · governance executed: yes · settlement evidence consumed: yes

Governance V3 tx capture

DYrU5yZ22fmUQHeTXwgSoQtfBKo7e7ZLsHJxRzvWLh4i

createDao · 3ncJuKRk1dbAm9QfxDRLNMgzQc2ECBFr9GYk7JACV3D47fxroi4hHbndRCU5VkNJrCXb3AQBsUwaow6ieqfP6x9H

initializeGovernancePolicyV3 · Mo6cL9p8Hp93sitx3hjY9WrR7iE2pdnnSfEGL4tkHbqeZuoHg5f9up1i4SUSAc7DSpkQD3AdDcdLDFy6X6r8gYy

fundRevealRebateVaultV3 · 3pc7saV5aWWkK9jzgxcvox4WpTW8Tnwch1ZTbfphJUodsZmusa8ttyPZMYGoAbzpSmuw6K5aLcgkGdjRRKyiPoA3

deposit · 5PLctwJyhswNQahhHWc6vqJsZpuE7mEMGu7BrSC7jueDFEAQV7cDvdeTUWazaADSSvNwE1f4ZXN7UjLRgifsEjwu

createProposal · g1Tk8SiaP5w12kCXUCySSKUADme8h4jLBiuVT4UUbFAGeYvHsS7gVPgipUpUhv3LV2jnQkxjQ8jDduR68E2EqDS

Settlement V3 tx capture

4i2sCjJogN1xy3irRs1L5JdU1cJkWp2kK7XHA1oGE7z4

fundRecipient · 4wc6fTADGWKorycZLtR8A4hQoD7CX5dTTMRnefCXf2rdUNEqrWTutgqtj3M4JEy5fc2DnUCCz1k1toC85zChLfTo

createDao · 29sHWJKQjcSfj9fQChhfmSYZ2YZqyDreUXVmEP2sUPEJWCJSj8tCwYB2sjJKfTsxRGZ4pxAggzuEnzSQMJ32HE1i

initializeSecurityPolicyV2 · 2sfs9NkPLa7BuapXVFve5djwUyb2Ax7EnNNrBJ2jyp3BJJX3X5dajApm7QPSsdjCPvtJWPd3JumzGWsNo57XFdAd

initializeGovernancePolicyV3 · 5A2Kodun61aZUA9kYSRNnCevXjnjkCdpYFDekJCWUGSbHF88q6xcw66aGsUtRnMmnU8JxfHDozq3upsGg3MQHnKw

fundRevealRebateVaultV3 · 5Us3r1aDPr97iJkHF7dHRwUjEp7RrepdZJ1M5PPzt3uneqjBRFtHYHkcV3NTdWHEfoacUX22xRzjJhLxyyDyRPmr

Runtime reality

Real-device coverage

0/5 real-device targets completed

Captured tx outcomes

185/212 tx outcomes captured

Adversarial discipline

33 adversarial scenarios · 0 unexpected successes

Open integration packet Open V3 proof

Read-node activation

Read-node judge activation

Judges should see that read-node is not a claim buried in docs: the indexed read path, telemetry packet, and deployment target are part of the proof story with an explicit backend gap.

Activation state

Indexed reads are live in-product; same-domain backend serving is still pending host cutover

The current live site is static on GitHub Pages. `/api/v1` becomes a true product rail only after a separate backend host and reverse proxy are cut over.

Read path

backend-indexer

Indexed coverage

41 proposals / 21 DAOs

Confidential

8 confidential payouts

Operator checks

6 operator checks

Integration coverage

4/6 REFHE settled · 3/4 MagicBlock settled

Open judge proof route Open telemetry packet Open read-node snapshot Open read-node ops Open deploy target Open cutover packet

Host readiness

Judge backend readiness

Judges should see the same backend truth as operators: the host target, public health and metrics proofs, and the fallback policy stay explicit until `/api/v1` is truly live.

Readiness state

Host-ready lane defined; public same-domain serving is still pending real cutover

Do not claim `/api/v1` as live on the current public site until the read node is hosted behind a real domain or subdomain with health, metrics, and reverse-proxy evidence.

Deploy target

https://app.privatedao.xyz/ → /api/v1

Health

/healthz

Metrics

/api/v1/metrics

Public checks

6 public checks

Indexed proof

41 proposals / 21 DAOs

Settlement proof

8 confidential payouts · 4 REFHE settled · 3 MagicBlock settled

Telemetry freshness

2026-04-11T14:20:29.957Z

Route binding

Reverse-proxy `/api/v1/*` to the read-node process while keeping writes wallet-signed on the client.

UI fallback policy

Until backend cutover is live, keep read-node evidence available through in-app packets and snapshots.

Open cutover packet Open deploy guide Open runtime snapshot Open telemetry packet

Live proofs

Baseline proof and dedicated V3 proof packet are both reviewer-facing

ZK anchors

On-chain proof anchors exposed in the Devnet evidence path

Wallets

Multi-wallet Devnet rehearsal already captured and packaged

Commercial rails

Grant, fund, gaming, and enterprise service packs remain part of the UI

Step 1

Live proof

Open the canonical Devnet flow that proves create → submit → private vote → execute treasury happened.

Step 2

Dedicated V3 proof

Open the additive hardening packet for Governance V3 and Settlement V3 after reviewing the baseline flow.

Step 3

Integration packet

Open the Frontier integrations packet to verify ZK, REFHE, MagicBlock, and Fast RPC surfaces together.

Step 4

Audit and launch trust

Close the loop with audit packet, launch trust packet, and mainnet blockers so proof is not separated from deployment truth.

Live proof

Canonical Devnet create → vote → execute flow with public reviewer links.

Open judge view

Live proof V3

Dedicated additive hardening proof for Governance V3 and Settlement V3.

Open curated V3 packet

ZK capability matrix

PrivateDAO-specific matrix for what the ZK stack proves today, how it is verified, and what is still explicitly not claimed.

Open curated ZK matrix

Cryptographic confidence engine

Deterministic scoring model for how ZK, REFHE, MagicBlock, and Fast RPC strengthen specific proposal patterns.

Open engine specification

Frontier integrations

ZK, REFHE, MagicBlock, backend-indexed reads, and runtime evidence in one surface.

Open integrations packet

Audit packet

Reviewer and launch artifacts tied together with generated attestations.

Open curated audit packet

Security rails

ZK Capability Matrix

Layer-by-layer truth-aligned matrix for proofs, anchors, attestation, zk_enforced posture, and verifier boundaries.

Cryptographic Confidence Engine

Proposal-aware scoring model for privacy depth, enforcement depth, execution integrity, and reviewer confidence across ZK, REFHE, MagicBlock, and Fast RPC.

Governance Hardening V3

Token-supply quorum mode, policy snapshots, and reveal rebate vaults stay additive and versioned.

Settlement Hardening V3

Payout caps, evidence aging, REFHE/MagicBlock requirements, and single-use settlement consumption semantics.

Mainnet blockers

The app keeps launch boundaries honest: what is live now, what is pending-external, and what still needs custody/audit work.