Explore
Product navigation
Read-node telemetry
Runtime telemetry
Reviewer-grade
Infrastructure
Run and verify low-latency infrastructure as a product lane, not hidden backend plumbing
This lane packages RPC and runtime infrastructure into a reviewer-facing route with telemetry, host readiness, and operational evidence continuity.
Route summary
Use PrivateDAO like infrastructure, not like a static brochure
This services route explains hosted reads, privacy policies, payout corridors, and the integration starter needed to plug the product into real organizations.
Services route brief
Services should show the business model, the operating lane, and the live Testnet proof in one commercial surface
This route works best when pricing, billing rehearsal, treasury routing, trust packets, and hosted-read packaging are kept together instead of being split across static documents.
Lead with the product lane a buyer can try immediately from a Testnet wallet.
Keep pricing and billing language tied to the current public-good Testnet boundary, not to unshipped mainnet claims.
Use the commercial surface to show that PrivateDAO can evolve into a sustainable infrastructure company.
Runtime infrastructure in PrivateDAO is exposed directly in product flows so operators and judges can inspect freshness, failover posture, and telemetry truth before trusting execution claims.
Read-node activation
Hosted-read activation
Buyer-facing infrastructure value starts here: indexed governance reads, reviewer telemetry, and the exact backend deployment target stay in one commercial path instead of being split across docs and GitHub blobs.
Activation state
Indexed reads and same-domain backend serving are live for Testnet reviewer checks
Public product routes consume indexed read evidence and the hosted `api.privatedao.org` lane now serves health, relayer, QVAC, Covalent GoldRush, Torque, Zerion, and SNS checks.
Read path
backend-indexer
Indexed coverage
20 proposals / 19 DAOs
Confidential
3 confidential payouts
Operator checks
6 operator checks
Integration coverage
2/3 REFHE settled · 1/2 MagicBlock settled
Host readiness
Hosted-read host readiness
Show buyers the real deployment lane: target host, public proof endpoints, route binding, and the static fallback policy stay visible from the commercial surface.
Readiness state
Host-ready lane defined; same-domain public serving is in final security hardening before release cutover
Use https://api.privatedao.org/api/v1 as the live read-node boundary. Same-domain `/api/v1` on the static frontend remains a future reverse-proxy consolidation step, not the current production-candidate API host.
Deploy target
https://privatedao.org/ → https://api.privatedao.org/api/v1
Health
https://api.privatedao.org/healthz
Metrics
https://api.privatedao.org/api/v1/metrics
Public checks
6 public checks
Indexed proof
17 proposals / 16 DAOs
Settlement proof
3 confidential payouts · 2 REFHE settled · 1 MagicBlock settled
Telemetry freshness
2026-05-26T03:09:35.774Z
Route binding
Serve read-node traffic from `https://api.privatedao.org/api/v1` until a same-domain reverse proxy is intentionally cut over.
UI fallback policy
If the API host is unreachable, keep read-node evidence available through in-app packets and snapshots.
Telemetry truth
Infrastructure telemetry truth
Freshness, fallback posture, and proof-linked telemetry shown from the same runtime corridor.
Freshness
12d old
Indexed proposal count
20
Governance finalized
0/7
Confidential finalized
0/5
Runtime service metrics
Hosted read coverage
20
The backend-indexer read path currently exposes 20 indexed proposals across 19 DAOs.
Confidential payout coverage
3
3 confidential payout proposals are indexed, with 2 REFHE-settled flows.
MagicBlock settlement completion
0%
0/5 confidential corridor transactions finalized in the current integration evidence package.
Service proof freshness
2026-05-26
Runtime evidence is generated as part of the current operational proof chain and kept published with the live surface.
Wallet review readiness
Capture program live
Browser-wallet review evidence, real-device intake, and the support matrix are tracked through a dedicated capture program instead of static claims.
Buyer-facing proof links
6
Trust package, launch trust packet, live proof V3, runtime evidence, wallet matrix, and mainnet acceptance remain linked in the live product.