Analytics | PrivateDAO

This route turns proposal counts, treasury motions, telemetry, and runtime freshness into a readable product surface. It exists so a visitor can understand what happened after a wallet action without reading raw logs first.

Open govern Open execute Open curated docs

Start with /learn if you are new. Use this route after a real Testnet action to understand the product through counts, freshness, and treasury movement before going deeper into proof or diagnostics.

Living proof

Live Testnet freshness and private visitor signal

Every visit pings the read node without storing personal data. Freshness is backed by a throttled Solana Testnet memo transaction, and usage is counted by hashed browser session only.

Last proof

waiting for first auto-refresh

auto-refresh will create the first ping

Signed today

...

visitor Testnet txs

Live sessions

...

last 30 minutes

Since launch

...

visitor-signed txs

Last 7 days

Top pages

Counted privately — no personal data stored.

Telemetry truth

Telemetry truth for analytics reviewers

Keep freshness, hosted-read scale, finalized governance counts, and the reviewer packet visible above the analytics surface itself.

Freshness

2d old

Indexed proposal count

Governance finalized

0/7

Confidential finalized

0/5

Open reviewer telemetry packet Open diagnostics Open analytics

Runtime and telemetry

Analytics is the easiest way to understand the live blockchain story after a wallet action

Use this corridor when a visitor, judge, or operator wants to understand signatures, telemetry, hosted-read value, treasury behavior, and runtime proof in one place without starting from raw blockchain internals.

Data corridor quick links

Fast path into the telemetry, hosted-read, and reviewer-safe data corridor without scanning the full product or document library first.

Open telemetry packet Open diagnostics Open analytics Open hosted-read proof Open read-node snapshot

Analyst-grade data corridor

Export-ready summaries and hosted-read proof for reviewer-grade telemetry

Telemetry posture

Runtime evidence, diagnostics, and analytics now behave like one reviewer-safe telemetry corridor rather than three disconnected surfaces.

Hosted-read proof

Core integrations, read-node snapshot, and services packaging keep hosted reads visible as buyer and reviewer value.

Operational trust

Launch trust, custody truth, and runtime evidence remain close enough that data reviewers can inspect proof without leaving the product shell.

Export-ready route

The telemetry export packet now gives a compact path into diagnostics, analytics, runtime evidence, and the hosted-read proof chain.

Open telemetry export packet Open telemetry packet Open read-node snapshot Open diagnostics Open read-node ops Open integrations

Telemetry export confidence

What a Dune or RPC reviewer can verify in under one minute

This route now sells a real infrastructure corridor: indexed governance state, hosted-read posture, runtime freshness, and reviewer-safe export packets.

Indexed governance state

Proposal and DAO state can be inspected through reviewer packets, analytics surfaces, and hosted-read packaging without leaving the product shell.

Runtime freshness

Diagnostics, runtime evidence, and telemetry packets stay close enough that a reviewer can judge data freshness instead of trusting static screenshots.

Buyer-safe infrastructure story

The same corridor explains product value to infrastructure buyers and data judges: API posture, hosted reads, proof, and disciplined operating transparency.

Export packet discipline

The export packet, read-node snapshot, and analytics route now behave like one inspectable reviewer lane rather than disconnected notes.

Export packet Telemetry packet Read-node snapshot Runtime evidence Diagnostics

Telemetry export scorecard

The data points that make the infrastructure story reviewable fast

Success rate

87.3%

185 successful Testnet transactions across 212 recorded attempts.

Primary RPC latency

104 ms

Current blockhash latency from the primary Testnet endpoint. Version latency is 796 ms.

Wallet runtime

Capture intake live

Browser wallet sign/submit evidence, connect-only captures, and selector coverage remain visible through a dedicated runtime intake program. Selector coverage is 100% across the support matrix.

Proof completion

0/7 canonical governance lifecycle transactions are finalized in the live proof package.

Reviewer-safe validation

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.

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.

Proof freshness

2d old

Runtime evidence 2d old and Testnet canary 2d old 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 21d old with 9 confirmed lifecycle signatures.

Product-lane commercial readiness

Core Product Lane · Runtime API And Fast Reads · Privacy Infrastructure Lane

Current top conversion-ready product lanes combine commercial upside, operating readiness, and mainnet distance: Core Product Lane (9.2/10) · Runtime API And Fast Reads (8.3/10) · Privacy Infrastructure Lane (7.9/10).

Why this raises Dune and RPC fit

This is no longer a generic analytics route. It shows what is indexed, how fresh it is, and where the reviewer can verify the same story through packets and diagnostics.

It also makes the commercial infrastructure thesis clearer: hosted reads, telemetry, runtime evidence, and trust are one corridor, not four unrelated claims.

That is closer to what wins infrastructure side tracks: concise metrics, reviewable surfaces, and explicit blocker honesty.

Export packet Reviewer telemetry Read-node snapshot Runtime evidence Analytics route

Hosted-read proof strip

Runtime, integration, and reviewer proof tied to one infrastructure story

This strip keeps the RPC and telemetry story concrete: hosted reads, runtime evidence, integration proof, and trust surfaces remain linked so the infrastructure case reads like product value rather than hidden backend detail. A visitor should be able to connect a Testnet wallet, run the flow, and then use these routes to see why the system already behaves like production-intent infrastructure.

Runtime evidence Core integrations Read-node snapshot Launch trust packet

Release readiness map

Multisig + authority transfer

Tracked

Custody evidence is partially recorded in-product (4/6). External signatures and readouts are being pulled into the same readiness lane so reviewers can follow the operating progress directly.

External audit closure

External evidence next

Security review packet exists, and external sign-off remains an explicit hardening gate.

Real-device runtime captures

Capture expansion active

Wallet runtime templates are documented; production captures are still separated from claims.

Monitoring + alerting

Documented

Operational rules exist and are linked, but live deployment evidence remains outside the repo surface.