Roadmap
— From a signed read-RPC to a fully decentralized, staked read mesh.
Pluid ships the read layer incrementally: prove the model with a signed, centralized mesh, then progressively decentralize serving and governance. Each phase keeps the same contract — every read is fresh, anchored, and verifiable.
Phase AShipped
Signed Read-RPC & Explorer
- Read-only /api/v1 surface over the mesh with per-IP FREE tier.
- Proof-of-serve receipts (ed25519 over canonical JSON) on every read.
- Block explorer: search, accounts, tokens, blocks, transactions.
- Realtime global stats over Socket.IO.
Phase BIn Progress
SDK & Independent Verification
- @pluid/sdk with typed methods and one-call verify().
- Published signing key at /api/v1/pubkey for offline verification.
- Worked examples for verifying receipts in any language.
Phase CNext
API Keys & Tiered Limits
- x-api-key issuance with per-key usage analytics.
- Sliding-window limiter and the Build / Scale tiers.
- $PLUID-staked access tier wired into the limiter.
Phase DPlanned
Operator Mesh
- Node software for independent operators to serve signed reads.
- Stake-weighted routing and health-aware request steering.
- Reward accrual for fresh reads; slashing for provably stale answers.
Phase EPlanned
Decentralized Read Layer
- Per-wallet realtime rooms over a shared upstream subscription.
- On-chain registry of operators and signing keys.
- Governance over limits, reward curves, and the read allow-list.
Holding $PLUID is the front-row seat: access tiers and operator onboarding both unlock through the phases above. Want to serve reads? Start with Run a Node.