the read layer for solana
Decentralized, geo-distributed read-RPC with verifiable freshness and signed proof-of-serve receipts. Validators are the write layer for agents; Replikon is the read layer.
Bonds token 4bns…iCuB — your wallet must hold it, and its network must match the program's cluster.
Send as x-api-key header.
Tier follows your $REPL holdings.
Live endpoint
A real read against Solana mainnet. Real Answer + Slot + a Receipt you Verify yourself.
Why read-only, why now
Reads dominate
Most RPC traffic is reads - idempotent, cacheable, parallelizable. The right wedge for a permissionless network.
Built for agents
Autonomous agents are read-heavy: they watch state before acting, at high volume, and need verifiable answers.
Geo-latency
Read latency is dominated by network distance. A geo-distributed mesh is structurally faster than one endpoint.
Explorer
Proof-of-serve
Cheating is detectable cheaply and unprofitable by construction four layers.
The auditor fires a probe with a known answer. A dishonest node is caught and slashed.
Account-hash proofs
Point reads link data to a hashed stat commitment - cryptographically checkable.
Known-answer audits
Probes with known answers, indistinguishable from real traffic, catch stale/false answers.
Signed receipts
Every read carries a node-signed receipt over the query, answer digest, and slot.
Stake & slashing
Operators bond $REPL; proven dishonesty burns stake and ejects the node.
Build
npm install replikon-rpc-sdkimport { ReplikonClient } from "replikon-rpc-sdk";const repl = new ReplikonClient({ endpoint: "https://backend.replikonrpc.com" });const { result, receipt } = await repl.getBalance("<address>");// repl.verify(receipt, { result, slot }) → independently verifiedOperators will run lightweight read-replicas and earn $REPL for verified reads. Requirements: a VPS, an upstream account stream, and a $REPL bond.
$REPL token
$REPL is a utility / access token - it is not an investment and carries no yield. Day one, holding $REPL gives you higher read limits.