Skip to main content
Every Allium stream is fed by one of two ingestion modes: lagged or zerolag. Pick lagged when you need data that won’t change underneath you. Pick zerolag when you need to react to a block the moment it’s produced.

Lagged streams

Lagged streams wait until a block is a set number of blocks behind the chain tip before publishing it. That buffer is the block lag. It means the data you receive matches what ends up in Allium’s historical tables. The trade-off is latency: your data trails the tip by the chain’s block lag.
A block lag of 0 means the chain has fast or deterministic finality, so the lagged stream already publishes at the tip.

Block lag by chain

Testnets

Zerolag streams

Zerolag streams publish each block as soon as it’s produced at the chain tip, with no confirmation buffer. You see activity seconds earlier than on the lagged stream for the same chain.

Next steps

Allium Beam

Filter and transform streams, then deliver them to your own infrastructure.

Websockets

Subscribe to realtime blockchain data over a persistent connection.