Phase 1 complete · Devnet next
Autonomous agents, trading systems, and real-time dApps need Solana reads that are fast, correct, and not gated by one vendor. StreamSync is a decentralized indexing network (DePIN) where 3–5 independent operators race to answer every query in under 10 milliseconds. Miss the SLA and you don't pay. Return the wrong result and get slashed.
< 10 ms
enforced query SLA
3–5×
operators race each query
4
node specializations
193+
passing core-library tests
What is StreamSync?
StreamSync is a high-performance decentralized indexing network (DePIN) for Solana — the fast, verifiable read layer that autonomous agents, trading systems, and real-time dApps depend on. It is a protocol, not a single hosted service. Every query is dispatched to 3–5 independent operators who race to answer it in under 10 milliseconds. The first correct response wins 70% of the payment and verification nodes split the rest. If nobody meets the SLA, the customer isn't billed.
The query layer is distributed DuckDB, sharded across operator clusters running on commodity hardware by a hash ring. Payments settle in $STRM, SOL, USDC, or any whitelisted SPL token, batched to Solana every five minutes. Because the network is multi-operator from day one, agents get reads whose correctness is backed by staked capital — not a marketing promise — and there is no single vendor to depend on and no migration step if one disappears.
No single throat to choke
Multiple operators serve traffic at once; customers set selection policy per query.
Pricing set by competition
Market-set rates in STRM/SOL/USDC — not a corporate rate card that changes with a tweet.
Verifiable, SLA-enforced reads
Answers are cross-checked by verifiers and payment only flows when the sub-10ms target is met — reads an agent can act on.
Problem → solution
When agents and real-time apps are the ones reading, four problems baked into the single-vendor model turn from annoyances into risks. StreamSync fixes each at the protocol level.
The problem
Hosted Solana RPC is dominated by a few providers. Prices change with a tweet, query shapes get rate-limited mid-quarter, and the reliability number is set by the team that also sets the bill.
StreamSync’s approach
StreamSync is a protocol. Independent operators compete on speed and price, and customers can change selection policy per query — no single party controls access or pricing.
Why economic decentralization →The problem
An autonomous agent that makes a payment, or an AI that acts on decoded state, can’t verify a hosted API’s answer. It trusts a black box — and pays whether or not the response was fast enough or even correct.
StreamSync’s approach
Every answer is raced across operators and cross-checked by verifiers; the payment contract only pays on a verified answer under the 10ms SLA, and wrong results are slashed. Reads are fast, verifiable, and safe to act on.
How the SLA is enforced →The problem
A single backend means you build the HA pool, the retries, and the migration plan yourself. When a provider degrades, your on-call finds out first.
StreamSync’s approach
Every query is raced to 3–5 operators simultaneously. If one is slow or offline, another has already answered — redundancy is structural, not something you engineer.
The racing pipeline →The problem
With a hosted API you trust that decoded state and historical queries are correct. There is no economic penalty when they are not.
StreamSync’s approach
Verification nodes flag mismatched responses and bad results are slashed from the operator’s staked 10,000 STRM. Correctness is backed by capital at risk.
Staking and slashing →Code
Wire the gateway into your app in a few lines, or stake and run an operator node to earn on raced queries.
# point your Solana client at the StreamSync gateway
const ss = new StreamSync({
gateway: "https://gateway.streamsync.cryptuon.com",
pay: "USDC", // or STRM / SOL / any SPL
policy: { race: 5, slaMs: 10 }, // race 5 operators, 10ms SLA
});
// analytical SQL over sharded Solana state (DuckDB)
const rows = await ss.query(`
SELECT owner, SUM(amount)
FROM token_accounts
WHERE mint = 'EPjF…Dt1v'
GROUP BY owner`);
// billed only if a verified answer arrives < 10ms# stake, pick a role, and join the network
$ streamsync stake 10000 STRM
→ staked. 7-day unstake cooldown active.
$ streamsync init --role speed-runner
# roles: speed-runner | cache | zk | archive
$ streamsync start
→ joined gossip mesh (NNG)
→ DuckDB shard assigned via hash ring
→ racing queries · rewards scale with reputationAPI shapes are illustrative of the protocol interface. See how it works →
What you get
Every query is dispatched to 3–5 nodes at once. First correct response wins 70% of the payment; verifiers split the rest. Slow nodes earn nothing.
Learn more →If no node returns a verified answer within 10ms, the customer is not billed. The contract pays on outcome, not effort — so agent loops and live UIs get real-time reads without waiting.
Learn more →A hash ring partitions Solana state across operator clusters. DuckDB merges sub-query results locally so analytical SQL stays fast at multi-billion-row scale.
Learn more →ZK reconstruction, cache optimizer, speed runner, and archive. Operators pick the role that fits their hardware and get matched to queries that play to it.
Learn more →Payments aggregate into 5-minute batches on Solana. Revenue splits 50% nodes, 20% treasury, 20% data providers, 10% governance — fixed in the protocol.
Learn more →Verification nodes cross-check every response. Bad results are slashed from the staked 10,000 STRM, so accuracy is collateral, not a promise — the kind of guarantee an autonomous agent can act on.
Learn more →Multiple independent operators run from day one. If one disappears, every other operator is already serving traffic. There is no migration step.
Learn more →A dedicated zk-reconstruction node class rebuilds compressed account state from on-chain proofs, so you don’t have to run compute-heavy reconstruction yourself.
Learn more →How it works
One query races several operators. The fastest correct answer wins; verifiers confirm it; Solana settles the batch.
Honest comparisons
If agents or a live UI depend on these reads, a single-vendor RPC is a systemic risk. We benchmark honestly against the providers people actually use — pick what fits, and switch when the math changes.
Strong webhooks and developer UX, but a single vendor. StreamSync gives you the same query surface with multi-operator redundancy.
Geyser-grade validator streams. StreamSync sits a layer up and gives you SQL with an enforceable latency SLA.
Multi-chain hosting with friendly tooling. StreamSync is Solana-native and only bills when the SLA is met.
gRPC and webhooks on a managed stack. StreamSync mirrors the surface area but routes traffic through a competing operator marketplace.
FAQ
Agents that make payments, AI systems that act on decoded state, and UIs that render every block cannot tolerate tail-latency spikes, mid-quarter rate limits, or a provider that quietly degrades. StreamSync races independent operators for a sub-10ms answer and slashes wrong results — so the reads are fast and verifiable, and no single vendor can gate them.
No. It is a decentralized network (DePIN) — a protocol, not a company. You point your client at the StreamSync gateway, and queries are routed to whichever independent operators are racing fastest. There is no single vendor you have to trust.
Three things: NNG for inter-node messaging, query racing across nearest operators, and aggressive predictive caching by the cache-optimizer node class. The 10ms SLA is measured at the customer-facing gateway in the same region.
Through the payment gateway, which accepts STRM, SOL, USDC, or any whitelisted SPL token. Customers prepay a balance; the protocol debits per successful query and settles to operators in 5-minute batches on Solana.
Yes. Stake 10,000 STRM, run streamsync init, pick a role (speed runner, cache, ZK, or archive), and join the network. Cooldown to unstake is 7 days. Operators are scored on latency, accuracy, and uptime, and rewards scale with reputation.
Drop in the StreamSync gateway, set a prepay balance in USDC, and let independent operators race for every request. Fast, verifiable, and billed only when the SLA is met — settled on Solana in five minutes.