208ms Block Time. 307ms Block Finality. 65% Less CPU. Meet (The Rebuilt) commonware Alto.

Verify Alto’s consensus outputs from 50 globally deployed validators (spread evenly across 10 regions) and measure latency in your browser (now via a 22% faster @exowarexyz):

Read about how we reduced block time by 20% (and CPU usage by 65%) by buffering signatures:

Reproduce our results (or start building your own blockchain) with our free and open-source code:

Think $BTC has topped? Think again. Past cycles show: 2012-13: Topped 367 days post-halving. 2016-17: 526 days. 2020-21: 548 days. 2024? We’re only 237 days in. There’s still a long way to go. 👉 Subscribe now and join 130K+ investors prepping for the next big move.

@commonwarexyz very underappreciated how insane this is for a globally distributed network

@commonwarexyz i just wanna be as chad as the @commonwarexyz team

@commonwarexyz everything about this is incredible. latency, verifiability, running on low cost boxes. what kind of throughput can it support?

commonware-consensus is entirely agnostic to the data it is agreeing over (and only requires a digest to be provided): As such, it is up to the application to decide how they want to propagate data/execute transactions in a way that strikes the right balance between expressiveness and performance (consensus is none the wiser). That being said, we are working on some stuff that should stress test how many "simple-ish" transactions can be pushed over our p2p implementation (while it is concurrently running consensus): (we only release blogs when we have code and the code isn't ready yet 😉)

@commonwarexyz

@commonwarexyz Chill brother, we like old world handcrafted bespoke blocks every 12 seconds like god intended

@commonwarexyz block printer go brrrrr