PrivateD△O
Run payrollRun a private auctionCoordinate treasury
Explore

Product navigation

Products
Choose the right PrivateDAO solution
Verify
Turn sensitive records into trusted evidence
Decide
Choose fairly without exposing live offers
Govern
Make private decisions with a clear audit trail
Treasury
Coordinate approvals, funds, and accountability
Workflows
Prove that important business processes happened correctly
Pricing
Choose a pilot, managed plan, or private deployment
Pilots
Start with a focused business use case
Developers
Connect your systems with the API and SDK
Trust
Understand privacy, evidence, and operating boundaries
Docs
Read the product and integration guides
Community
Join the ecosystem and get support
Agent Marketplace
Discover and connect useful agent services
PDAO Worlds
Experience privacy and coordination through play
Hosted reads
QuickNode Streams
Diagnostics
Lecture 3
Solana Runtime UX: Hosted reads, Diagnostics, and Activity Tracking

This lecture explains why Hosted reads, QuickNode Streams, hosted reads, telemetry, analytics, and diagnostics are not backend trivia. They are core UX components that make Testnet activity understandable and trustworthy.

Open governOpen executeOpen curated docs
PrivateDAO Frontend Bootcamp
L1L2L3L4SlidesToolkitTasksQuiz
Users trust a dApp when state updates feel honest.

What this lecture turns into in the product

This lecture explains why Hosted reads, QuickNode Streams, hosted reads, telemetry, analytics, and diagnostics are not backend trivia. They are core UX components that make Testnet activity understandable and trustworthy.

Open DashboardOpen DiagnosticsOpen RPC ServicesOpen API Status
Lecture assets
Open slidesOpen assignmentOpen quiz
Dashboard route
https://github.com/X-PACT/PrivateDAO/tree/main/apps/web/src/app/dashboard/page.tsx
Diagnostics route
https://github.com/X-PACT/PrivateDAO/tree/main/apps/web/src/app/diagnostics/page.tsx
RPC services route
https://github.com/X-PACT/PrivateDAO/tree/main/apps/web/src/app/rpc-services/page.tsx
API status route
https://github.com/X-PACT/PrivateDAO/tree/main/apps/web/src/app/api-status/page.tsx
Testnet metrics
https://github.com/X-PACT/PrivateDAO/tree/main/apps/web/src/lib/devnet-service-metrics.ts
Reviewer telemetry packet
https://github.com/X-PACT/PrivateDAO/tree/main/docs/reviewer-telemetry-packet.md
Runtime activity starter template
https://github.com/X-PACT/PrivateDAO/tree/main/templates/frontend-solana-bootcamp/runtime-activity-starter/RuntimeActivityStarter.tsx
Run this lecture now

Run one state-and-proof check now

After a real wallet action, inspect dashboard, diagnostics, API status, RPC services, and telemetry so the user sees freshness, status, retries, QuickNode stream posture, and proof instead of a shallow success message.

  • • Perform a real wallet action first from Start or Govern.
  • • Open Dashboard to inspect the current activity and signatures.
  • • Continue into Diagnostics, API Status, and RPC Services to confirm runtime behavior, backend health, and proof freshness.
Open dashboard runtimeOpen diagnostics and logs
Why this is production learning
This lecture does not end at theory. The primary button takes the user into a live product route where the same concept becomes a real Testnet action from the UI.
The verification button opens the state, judge, diagnostics, or proof lane needed to confirm what the wallet action produced on-chain.
The result is stronger than a tutorial: a normal user learns the product and exercises the real system in the same corridor without terminal work.
What you’ll learn

How to show transaction hashes, proposal freshness, runtime diagnostics, hosted-read state, and analytics summaries after real wallet actions.

Why this matters on Solana

A user does not care about RPC branding. They care that state updates quickly, retries are understandable, and a transaction can be followed into logs and proof after a signature.

How PrivateDAO solves it

PrivateDAO uses dashboard, diagnostics, analytics, API status, RPC services, and reviewer packets to show the same truth from different depths. QuickNode-backed Testnet telemetry, Hosted reads, and hosted reads become visible through product behavior, not just claims.

Try it now

Run a wallet action, then move into Dashboard, Diagnostics, API Status, RPC Services, and Reviewer Telemetry to see the state change, proof freshness, QuickNode stream posture, and runtime corridor in one flow.

Check the code

The runtime story lives across dashboard, diagnostics, analytics, and the devnet metrics library. That is where product-facing state and infrastructure truth stay synchronized.

Assignment
Build a runtime activity widget

Create a widget that shows the last action, tx signature, live status, and a recovery hint when runtime state lags or retries are required.

  • • Last action summary
  • • Clickable Testnet transaction hash
  • • Status / retry hint / freshness indicator
Try the live routeOpen all assignments
Dashboard route
https://github.com/X-PACT/PrivateDAO/tree/main/apps/web/src/app/dashboard/page.tsx
Analytics route
https://github.com/X-PACT/PrivateDAO/tree/main/apps/web/src/app/analytics/page.tsx
Runtime activity starter template
https://github.com/X-PACT/PrivateDAO/tree/main/templates/frontend-solana-bootcamp/runtime-activity-starter/RuntimeActivityStarter.tsx
Quiz
Check understanding before you ship
1. Why does Hosted reads matter to the user experience here?
  • A)It makes proposal, proof, and payout state update quickly enough to feel trustworthy.Correct
  • B)It removes the need for analytics.
  • C)It only matters to validators, not to users.
2. What should happen after a wallet action lands?
  • A)The user should be able to follow the hash, status, and logs.Correct
  • B)The UI should stop explaining anything.
  • C)The app should hide runtime state until mainnet.
3. What does RPC stand for in this learning path?
  • A)Remote Procedure Call.Correct
  • B)Runtime Privacy Corridor.
  • C)Rapid Program Chain.
4. Why are diagnostics part of product UX instead of backend-only tooling?
  • A)Because they help the user understand freshness, retries, and what the chain actually recorded.Correct
  • B)Because diagnostics replace wallet signatures.
  • C)Because analytics pages should never show transactions.
5. What makes a runtime widget useful for a non-expert?
  • A)It shows the last action, tx hash, current status, and the next recovery hint.Correct
  • B)It only displays raw JSON responses.
  • C)It hides status until the session ends.
Open all quizzesVerify on-chain evidence