Root docs
Repository viewer
Legacy docs parity surface
Back to repository viewer
Repository document
Reviewer Telemetry Packet
reviewer-telemetry-packet.generated.md
Boundary
This route preserves legacy markdown access inside the Next.js surface. The raw repository file remains authoritative.
Open raw fileReviewer Telemetry Packet
Overview
- project:
PrivateDAO - generated at:
2026-05-26T03:09:35.774Z - reviewer intent: Show the shortest truth-synced route into runtime maturity, hosted reads, indexed governance, and infrastructure-facing reviewer value without claiming unsupported partnerships or mainnet readiness.
Truth Sources
- Runtime evidence:
2026-05-26T03:07:06.583Zviadocs/runtime-evidence.generated.md - Frontier integrations:
2026-05-26T03:05:31.037Zviadocs/frontier-integrations.generated.md - Read-node snapshot:
2026-05-26T03:04:20.758Zviadocs/read-node/snapshot.generated.md - Devnet service metrics:
2026-05-26T03:07:06.583Zviaapps/web/src/lib/devnet-service-metrics.ts
What Works Now
- Hosted reads expose 17 indexed proposals across 16 DAOs through the backend-indexer path.
- Diagnostics, analytics, and services remain live reviewer-visible routes starting from https://privatedao.org/diagnostics/.
- 0/7 canonical governance lifecycle transactions are finalized in the current integrations package.
- 0/5 confidential settlement corridor transactions are finalized in the current integrations package.
- 2 REFHE-settled and 1 MagicBlock-settled proposal paths are already reflected in the indexed source.
What Is Externally Or Operationally Proven Now
- Runtime evidence package generated at 2026-05-26T03:07:06.583Z and published as docs/runtime-evidence.generated.md.
- Frontier integrations package generated at 2026-05-26T03:05:31.037Z with reviewer entry https://privatedao.org/proof/?judge=1.
- Read-node snapshot generated at 2026-05-26T03:04:20.758Z on slot 410937813 against https://api.testnet.solana.com.
- Proposal flow health, wallet readiness, and proof freshness summaries are taken from the same devnet service metrics module used by the live app.
- Unexpected runtime failures remain 0 and unexpected adversarial successes remain 0.
Hosted-Read Proof
- read path:
backend-indexer - rpc endpoint:
https://api.testnet.solana.com - slot:
410937813 - current Testnet program id:
EP9xE8MJZ6FfyEwLqns6HDdUZBknEa7WGYs1Jzsecuva - legacy Devnet hosted-read program id:
EP9xE8MJZ6FfyEwLqns6HDdUZBknEa7WGYs1Jzsecuva - commitment:
confirmed - indexed proposals:
17 - indexed DAOs:
16
Runtime Snapshot
- diagnostics page:
https://privatedao.org/diagnostics/ - wallet count:
5 - unexpected failures:
0 - fallback recovered:
true - stale blockhash recovered:
true - pending real-device targets:
4
Integrations Snapshot
- governance status:
degraded-testnet-governance-path - confidential status:
degraded-testnet-confidential-path - governance finalized:
0/7 - confidential finalized:
0/5 - zk anchors confirmed:
0/3
Export-Ready Summaries
- Proposal flow health: 50% — 0/7 governance proof steps are finalized. 1 proposal is already executed on Testnet, 0 proposal is still in commit mode, and 2 proposal is still waiting on settlement evidence. (Open proof and execution: /proof/?judge=1)
- Wallet-by-wallet readiness: Runtime capture live — Wallet diagnostics, connect/sign/submit evidence, and real-device intake are surfaced as a living runtime program with proof packets attached for each supported wallet path. (Open wallet diagnostics: /diagnostics)
- Proof freshness: fresh this hour — Runtime evidence fresh this hour and Testnet canary fresh this hour remain published together. The integration packet remains linked as the reviewer baseline without turning an archived source packet into the freshness score. Latest Testnet rehearsal is 19d old with 9 confirmed lifecycle signatures. (Open trust documents: /documents/live-proof-v3)
- Hosted read coverage: 17 — The backend-indexer read path currently exposes 17 indexed proposals across 16 DAOs. (Open services: /services)
- MagicBlock settlement completion: 0% — 0/5 confidential corridor transactions finalized in the current integration evidence package. (Open diagnostics: /diagnostics)
- Primary RPC latency: 104 ms — Current blockhash latency from the primary Testnet endpoint. Version latency is 796 ms. (Open analytics: /analytics)
Reviewer-First Path
- Open telemetry packet: Start from the generated truth-synced packet instead of inferring readiness from multiple pages. (/documents/reviewer-telemetry-packet)
- Open diagnostics: Validate runtime health and reviewer-visible operational signals. (/diagnostics)
- Open analytics: Inspect export-ready summaries sourced from the same metrics module. (/analytics)
- Open services: Confirm the hosted-read and buyer-facing infrastructure route. (/services)
Best Demo Route
- start:
/services - sequence:
/services->/diagnostics->/analytics->/documents/reviewer-telemetry-packet - explanation: Lead with the buyer-visible infrastructure surface, then validate runtime health, then show export-ready analytics summaries, and finally land on the reviewer packet that binds the same truth sources together.
Exact Boundary
- This packet does not claim live third-party analytics partnerships.
- It does not claim production mainnet custody or launch approval.
- It does not replace canonical custody proof, launch trust packet, or mainnet blockers.
- Pending real-device captures remain explicit and are not hidden behind aggregate metrics.
Linked Docs
docs/reviewer-telemetry-packet.generated.mddocs/runtime-evidence.generated.mddocs/frontier-integrations.generated.mddocs/read-node/snapshot.generated.mddocs/launch-trust-packet.generated.mddocs/canonical-custody-proof.generated.md
Live Routes
- https://privatedao.org/services/
- https://privatedao.org/diagnostics/
- https://privatedao.org/analytics/
- https://privatedao.org/documents/reviewer-telemetry-packet/
Canonical Commands
npm run build:reviewer-telemetry-packetnpm run verify:reviewer-telemetry-packetnpm run build:runtime-evidencenpm run verify:runtime-evidencenpm run build:frontier-integrationsnpm run verify:frontier-integrationsnpm run build:read-node-snapshotnpm run verify:read-node-snapshot