We’re reworking how our WebSocket streams deliver data. These changes are targeted for 5 August, starting with Solana.
No endpoint or subscription changes. Same URLs, same queries — the change is in how messages are delivered.
What you’ll notice
- More messages, each smaller, arriving faster. Data is pushed as it arrives instead of waiting for a full block to assemble.
- USD values on far more tokens.
- More concurrent subscriptions, depending on your plan.
- More stable subscriptions overall.
What’s changing under the hood
1. Message structure now mirrors Kafka streams
Instead of one message per block, each message carries a range of transactions from a block. Two consequences:
- A single message contains only part of a block, not the full block. If you rely on block-level completeness, you’ll need to aggregate messages on your side.
blockHashmay be absent, since it isn’t known at the time the message is emitted.
2. Lower latency
Removing the block-assembly step lets us push data as it arrives. We expect WebSocket latency to become comparable to Kafka.
3. Better stability
The stream no longer depends on the database. A leaner pipeline means fewer moving parts and fewer failure points.
4. USD prices from our own feed
Prices now come from our pricing feed rather than CEX data, so coverage extends to tokens that never list on a centralized exchange.
Rollout
Solana goes first on 5 August. Once it’s stable there, we’ll extend the same changes to EVM chains and the rest of our supported networks. We’ll post updates here as each stage goes live.
For most users nothing needs to change on your side. If you’re using blockHash in your stream, talk to us before the 5th — reply in this thread or ping us on Telegram and we’ll sort out the migration with you.