Frequently asked questions

StreamSync is a protocol-level indexing network for Solana. Every query is raced to 3–5 independent operators; the first correct response under a 10ms SLA wins 70% of the payment and verifiers split the rest. It is a marketplace, not a single hosted service.

No. It is a protocol. You point your client at the StreamSync gateway, and queries are routed to whichever independent operators are racing fastest. There is no single company you have to trust.

Account lookups, program-derived data, decoded SPL/Metaplex state, transaction traces, and analytical SQL across historical indices. The query layer is DuckDB, so anything expressible in SQL is fair game.

Phase 1 development is complete: core libraries (193+ tests), the STRM token program, payment gateway, settlement engine, racing competition, node specializations, gossip protocol, and cluster management. Devnet is next, mainnet follows.

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.

A hash ring partitions Solana state across operator clusters. Each operator runs DuckDB over its assigned partition and merges sub-query results locally before responding, so analytical SQL stays fast even at multi-billion-row scale.

A dedicated zk-reconstruction node class rebuilds compressed account state from on-chain proofs. These nodes earn a premium because the work is compute-heavy and customers value not having to run it themselves.

The query was raced to 3–5 nodes. Whoever else finishes first still wins. The offline operator earns nothing and accumulates uptime debt against its reputation score, which lowers future query selection probability.

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.

If no operator returns a verified answer within 10ms, the customer is not billed for that query. Payment flows only on a met SLA — the incentive to be fast sits entirely on the operators.

Per successful query, the winning node earns 70% and verifiers split the remaining 30%. Across the protocol, revenue splits 50% to nodes, 20% to treasury, 20% to data providers, and 10% to governance — fixed in the protocol, not a vendor decision.

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.

ZK reconstruction (high compute), cache optimizer (high memory), speed runner (low latency), and archive (high storage). Operators pick the role that fits their hardware and get matched to queries that play to it.

Verification nodes flag mismatched responses, and incorrect results are slashed from your staked 10,000 STRM. Accuracy is backed by capital at risk, not a service-level promise.