Optimum

My team @get_optimum built the p2p networking efficiency improvement that @VitalikButerin is talking about in his second point here, and it's live on Ethereum mainnet today. We use Random Linear Network Coding, which is a provably optimum coding scheme for broadcasting data across decentralized networks. It's already making an impact with 90% of blocks reaching validators ~2x faster. We released it as a free sidecar, so any validator can run it with no consensus changes required. High performance p2p networking matters even more as Ethereum moves towards shorter slots and PQ security. RLNC is designed so that propagation speeds won't slow down when large data objects like PQ signatures need to be transmitted across the network.

Point 2 is exactly the class of coded propagation we @get_optimum have been shipping with mump2p (RLNC). already live as a sidecar on Ethereum mainnet. Indeed, it is not consensus code.

When we started building @get_optimum two years ago there wasn't much institutional crypto adoption taking place at all. However, there were a few signals that the pace might be picking up soon, such as the first ETH ETFs being launched. What we recognized back then was that networking HAD to be improved if serious adoption was going to take place. You simply can't run a complex financial system on a decentralized network if it's prone to congestion when traffic spikes. At that point, barely anyone was acknowledging the networking bottleneck, much less actually building a solution. Fast forward to today, we're seeing institutional adoption accelerating at a rate not many people thought possible two years ago. The financial markets are starting to recognize just how valuable it is to have worldwide 24/7 trading access for all kinds of assets. I think a lot more people are now seeing the path we're on, and the question of "can the infrastructure handle the incoming adoption?" is becoming much more relevant. @get_optimum is here to make sure the answer to that question is yes.

If you’ve been in crypto for a while, you’ve seen those days when the markets go crazy and everyone is jumping in or out at the same time. The resulting congestion leaves traders uncertain about when their transaction will go through. This is a networking problem. I like to think of blockchain networking as a supply chain, taking the raw inputs of submitted transactions and outputting finalized blocks. As with any supply chain, one of the most important factors in scaling up is removing the uncertainty around when deliveries arrive. The underrated part of @get_optimum is how much more consistent it makes data delivery timing, even when transaction volumes spike. We can’t be certain when these spikes will happen, but if you’re trading on a chain equipped with RLNC-powered networking, you won’t be left uncertain about when your transaction will land.