Welcome, @tempo
Today, we're thrilled to share that Tempo is building with the @commonwarexyz Library, supporting our growth as a new core contributor, and accelerating our research and engineering with a strategic investment.
https://t.co/9oUc7mMZQV
9/ The catch is head-of-line blocking: if one instance stalls (crashed leader), it holds up the merged log. So there's an optimal K, which we derive in closed form. More reliable validator set → more barrels you can run.
7/ We built Gatling from the production Simplex deployment by @commonwarexyz@_patrickogrady with a deliberately unoptimized 500ms per-instance block time, on a global cluster. Result: 214ms end-to-end transaction latency and 10ms inter-proposal time. Rotating leaders every 10ms.
5/ Each instance still obeys the 3Δ confirmation bound. The speedup comes purely from composition, not from tuning any single protocol. Crank K up and the inter-proposal time shrinks toward zero, below the network delay itself.
4/ Gatling does exactly that. Run K parallel instances of an off-the-shelf consensus protocol (PBFT, Tendermint, Simplex) each with the same proposal cadence, but offset by 1/K. A deterministic merge rule interleaves their outputs into a single totally-ordered log.
3/ A single-shot rifle has the same problem: you fire, reload, fire. Latency is capped by one barrel's cycle time. Richard Gatling's 1862 answer: don't make one barrel faster, spin several, staggered, and fire them in rapid succession. Same per-barrel speed, higher rate of fire.
2/ In major chains each block points to its parent, so you can't start consensus on the next block until you've seen the previous one. That floors block time at one network delay. Confirmation latency is at its proven lower bound. The only knob left is the gap between proposals.
1/ Bitcoin 2009: 10min block times
Ethereum 2014: 12s block times
Solana 2020: 400ms block times
New chains in 2026: still 400ms!
Gatling 2026: 10ms slots with 214ms end-to-end tx latency
Gatling: Rapid-Fire Consensus from Parallel Composition, w/ @jneu_net & @MaxResnick 🧵
Commonware chains on Celestia are now possible.
Launching a Commonware chain on Celestia gets you 10x faster blocks without the infrastructure overhead and the launch delays of having to recruit a validator set.
Check out coro, a data availability library with a minimal Commonware single sequencer crate:
a huge shout to @web3gb and and Javed Khan for quickly adapting alto and constantinople to use coro, and to my colleague @VGonkivskyi for his initial work on this poc.
and ofc mandatory s/o to @_patrickogrady and the @commonwarexyz team and contributors!
https://t.co/HDLjtNkQEs
We’ve built coro, a crate that lets developers build rollups using the commonware library in a day, allowing them to achieve: 20ms block times (a 10x speedup compared to alto with simplex) without the infrastructure overhead from expensive / bulky validator sets