patrickogrady.xyz Profile picture
May 12 8 tweets 2 min read Read on X
Today, we’re announcing Route 66 (a new initiative co-led by @coinbase to make it faster and cheaper to connect to specialized blockchains) and a strategic investment from @cbventures.

commonware.xyz/blogs/route-66
Blockchains look and feel less like blockchains each month (and that’s a good thing).

To better compete with today's web, onchain products are blurring the line between blockchain and application.

Whether stablecoins with dedicated blockspace, tighter spreads with encrypted mempools, or games with fair randomness, blockchains are modded more than ever. Image
This win for users is a massive nightmare for wallets, exchanges, custodians, and data providers.

With frequent hard forks, novel cryptography, and complex transactions at 10k+ TPS, these new stacks are slow to integrate and expensive to maintain. Image
The result? Only a handful of new blockchains are widely integrated each year, often with only minimal support (just transfers).

At @commonwarexyz, we believe this is a "dollars and sense" problem.
Make novel blockchains cheaper to integrate and we'll see more of them.

Lower the barrier to experiment and we’ll see even more exciting uses of blockspace.

Fortunately, Coinbase sees things the same way.
Today, Commonware and Coinbase are launching a new initiative to “pave the road” for a new era of onchain applications.

Via standards, common libraries, and shared tools, we will lay a highway that new applications can leverage to reduce cost and time to market.
Want to get your blocks on Route 66?

Help pave the road at route66@commonware.xyz!

• • •

Missing some Tweet in this thread? You can try to force a refresh
 

Keep Current with patrickogrady.xyz

patrickogrady.xyz Profile picture

Stay in touch and get notified when new unrolls are available from this author!

Read all threads

This Thread may be Removed Anytime!

PDF

Twitter may remove this content at anytime! Save it as PDF for later use!

Try unrolling a thread yourself!

how to unroll video
  1. Follow @ThreadReaderApp to mention us!

  2. From a Twitter thread mention us with a keyword "unroll"
@threadreaderapp unroll

Practice here first or read more on our help page!

More from @_patrickogrady

Dec 9, 2025
With @tempo, what you can see is just as impressive as what you don't.

In each round of consensus, Tempo validators emit a set of BLS12-381 threshold signatures that can be verified against a static network key (maintained across validator set changes) 🔐
The first of these signatures provides an embedded VRF.

It powers just-in-time leader election (no one knows who the next leader will be until the previous round is notarized/nullified) and provides onchain randomness (for blind auctions backed by Timelock Encryption). Image
The second of these signatures is over the block (attesting to its finalization in ~48B).

This "certificate" can be used by users to verify the validity of chain data provided by RPCs and to drive interop with other chains (just verify a proof against the static network key). Image
Read 6 tweets
Nov 14, 2024
Anyone aware of a consensus paper that uses a “loss-y model” for message delivery rather than the typical “eventually delivered” assumption?
The papers I’ve read recently uniformly assume messages will eventually be delivered but never dropped (unlike a real-world setting over a WAN with periodically rebooting nodes) and leave it as an exercise to the reader to craft sound mechanisms to recover from “inevitable gaps”.
While the proofs might be near impossible to write, curious if there isn’t more peer-reviewed work on balancing robustness vs bandwidth/efficiency at different message failure rates or in different recovery scenarios.
Read 8 tweets
Aug 8, 2024
I am launching a new company, @commonwarexyz, because I think the communities that will be leaders in the onchain era will take a different path than the ones already paved: specialization.
To accelerate developers that share this perspective, Commonware is building an open, Rust-based blockchain framework architected for excessive throughput, tractable modification, and embedded interoperability.
Today, we are taking the first step towards launching the Commonware Framework. p2p, our first primitive, is now available (in ALPHA) under both Apache-2 and MIT:

docs.rs/commonware-p2p
Read 4 tweets
Jun 25, 2024
Is it possible to make a large (> 500 validators) and robust (liveness and safety up to f < n/3 byzantine faults) blockchain snappy (~1s finality)?
1/ Over the last few months, @stephenbuttolph and I explored this question. Image
2/ After many rounds of iteration (i.e. Stephen poking holes in my ideas), we arrived at Vena.

Vena drives finality at network speed, provides strong liveness guarantees, and natively outputs confirmation artifacts (aggregate signature for each block) over large validator sets.
Image
Image
Read 12 tweets
Jun 10, 2024
Vena: Optimistically Responsive Consensus Over Large Validator Sets

hackmd.io/@patrickogrady…
1/ Vena is an optimistically responsive consensus protocol in the partially synchronous network model tailored for deployment on public blockchains with large validator sets.
2/ Vena employs a form of "optimistic" aggregation committee broadcast that when successful results in all participants, including the leader, sending less than n messages in a given round.
Read 8 tweets
May 23, 2024
1/ 🛠️ 🛠️ #Avalanche Durango 6 is out: 🛠️ 🛠️

This version (v1.11.6) is backwards compatible to v1.11.0. It is optional but recommended for all operators.

🔍 Focus: secp256r1 Staking Keys + Improve C-Chain State Sync Reliability + Fix Connection Tracking github.com/ava-labs/avala…

Image
Image
2/ 🚧 Attn Node Operators: Metrics Refresh 🚧

Durango 6 overhauls the format of many of AvalancheGo's exported metrics. This new format is easier to work with when creating dashboards and cheaper for hosted metrics platforms to ingest.

This work will continue in Durango 7.
Image
Image
3/ ✅ Compatibility Check: VM Interface (v35) ✅

Durango 6 DOES NOT modify the VM interface. If you are running a Custom VM on v1.11.3-v1.11.5 (like Subnet-EVM@v0.6.3), it will work with v1.11.6.

github.com/ava-labs/subne…
Read 8 tweets

Did Thread Reader help you today?

Support us! We are indie developers!


This site is made by just two indie developers on a laptop doing marketing, support and development! Read more about the story.

Become a Premium Member ($3/month or $30/year) and get exclusive features!

Become Premium

Don't want to be a Premium member but still want to support us?

Make a small donation by buying us coffee ($5) or help with server cost ($10)

Donate via Paypal

Or Donate anonymously using crypto!

Ethereum

0xfe58350B80634f60Fa6Dc149a72b4DFbc17D341E copy

Bitcoin

3ATGMxNzCUFzxpMCHL5sWSt4DVtS8UqXpi copy

Thank you for your support!

Follow Us!

:(