Excited to announce that I've been leading research at Blockspace for multiple months now.
More than 90% of blocks are constructed out-of-protocol. Improving this process will benefit Ethereum, originators, validators, builders...
When Ethereum and ETH win, Blockspace wins.
Expect tangible improvements within weeks.
Blockspace @Blockspace_ETH Aug 4 Article Blockspace: Connecting the World to Ethereum We are announcing Blockspace, an Ethereum Infrastructure Company. Ethereum is in the business of selling blockspace, and it produces the highest grade blockspace in the world. Today, more than 90% of
This is an ambitious proposal. Great!
I like anchoring problems to fundamentals.
Ethereum is moving to cryptography with less structure and assumptions ("hash-based").
This leaves less foothold for attacks (AI, Quantum..).
The main trade-off is signature size. This means blocks become harder to propagate and verify.
We can address this in three ways:
(1) Reduce what needs to be processed.
(2) Increase the time for processing.
(3) Make processing faster.
I believe out-of-protocol mechanisms like MPBC can help a lot with these.
We can reduce what needs to be processed by aggregating signatures. This is what EIP-8288 proposes.
I believe that MPBC operators / relays are well-placed to aggregate signatures.
This is because they have processing power, and are connected to almost all validators.
We can increase the time for processing by structuring the slot better or reducing networking distance.
Pipelining from ePBS helps with slot structure.
Through MPBC heavy TXs like blobs are frequently included in multi-party blocks last-mile before delivery.
This is because the block has less travel time left on the network and so making it larger is less risky.
This exact mechanism can be used for large TXs like Frames.
We can make processing faster through algorithms or hardware.
There's much work to be done, but I believe economic competition between multiple entities like in the block auction is a good way to incentivize speed.
Overall, excited for an ambitious pqai roadmap.
pqai27: Our view on post-quantum and post-AI timelines.
We shared this on Ethereum Magicians as input into the Ethereum governance process.
ethereum-magicians.org/t/pqa…
Payload Sharing is a new win<>win addition to multi-party block construction.
This allows multiple operators to propagate the block signed by the proposer together.
As a result, blocks reach the network more reliably.
Reducing delivery risk benefits Ethereum users, validators, builders..
1/ MPBC operators now support Payload Sharing. This improves Ethereum’s robustness as block propagation moves from one party to multiple parties. With Payload Sharing, we observed blocks reliant on one operator fell from 47% to 9% and on avg. blocks were delivered by +2 parties.
Multi-party block construction may be the "best chart in crypto".
Now at 13.4% of blocks over the last 24h and closing in on 500k included user transactions.
Out-of-protocol has much to give to Ethereum and users.
This is especially true as in-protocol shifts to addressing PQ.
Today: 12.6% of Ethereum blocks are multi-party.
This means almost 40k transactions were added to blocks by multiple builders over the last 24h.
This is equivalent to about 126h in user wait time saved!
Delivering. Expect this share to go up even further.
Today: 12.6% of Ethereum blocks are multi-party.
This means almost 40k transactions were added to blocks by multiple builders over the last 24h.
This is equivalent to about 126h in user wait time saved!
Delivering. Expect this share to go up even further.
My rather detailed take on validator bid selection follows.
Validators can select:
- Latest bid, which allows builders to cancel older bids.
- Highest bid, which does not allow that.
Selecting the latest bid is likely more profitable longer-term.
When validators select the highest bid, traders are exposed to additional risks which they have to price into their transactions.
Let's unpack it:
The block auction can end at any time. The bid at time t is right at that time t.
If there is a risk that this old bid gets taken at t+1 then that is a distinct risk factor.
If I’m a trader and I know my bid only gets taken when I submit it then I have to price some risks, mainly market risk.
If I know that it can also get taken later, then I have to add a new risk term for this distinct adverse selection risk.
Because of this distinct new risk, my bid is lower in expectation.
Because the exposure window is unknown, I can’t price the risk properly so I add a margin on top of the expected loss which means that EV goes down.
This affects small proposers especially because of their varying setups.
This risk can also surface in other ways.
Let’s say instead of pricing lower, I want to avoid adverse selection by just submitting a single bid.
This means I have to identify the exact moment at which the auction ends.
This varies with different proposer setups, to the disadvantage of small proposers especially.
As a result, delivery risk goes up (eg missed slot) and expected value goes down.
An analogy is an RFQ you get from multiple market makers.
This has an expiry time and if that expiry time is stretched and old quotes can get taken, then each quote will be worse to take that risk into account.
We also continue to support and grow the Ethereum ecosystem.
On August 4, we announced a strategic investment in @BlockSpace_ETH. Blockspace’s team helped develop the systems that build most of Ethereum’s blocks, and it’s now making them faster and more reliable.
It adds to our support for @ethlabs_org, @ethereuminsti and @eth_systems, which work on Ethereum's core protocol, institutional adoption and privacy.
Participated in workshops on Frame Transactions (EIP-8141) last week.
Great EIP. More flexibility for users is great.
Most excited about support for different concurrent signing methods, e.g. different cryptography. Really key for PQ.
Frame Transactions have new requirements. For example, they can be very large.
For this reason I see much overlap with multi-party block construction.
MPBC frequently adds a lot of gas to blocks, including transactions and blobs.
For example, just today a block with +44.8m gas landed. Multiple blocks exceeding 20m gas added also landed.
I think frame transactions can be great for users, and MPBC is a very efficient way of getting them included.
Looking forward to that.
Some Devcon takeaways:
- While I enjoyed visiting India, the location did limit attendance from the Americas in particular.
- Security and specifically PQ is the absolute focus and will determine the roadmap now and until solved.
- 10%+ Ethereum blocks are multi-party now. More people should know about this. This share will keep climbing.
- Frame transactions are a good, general solution and address many problems. A multi-sig using multiple types of cryptography is an example (PQ!)
- Bear market is clearly felt. However, I believe doubling down on the upside and neutral tech is very worthwhile.
- A lot of M&A activity. Often small, profitable teams getting acquired.
- Always good catching up with friends old and new.
I’m particularly excited about the low latency variance Silver has.
This means that edge cases are consistently covered. It’s a sign of elegant engineering.
This risk reduction is a key requirement for larger blocks, such as multi-party blocks.
I hope other clients follow suit.
Gattaca @gattacahq Oct 29 Article Introducing Silver Today we’re introducing Silver, Gattaca’s new Ethereum consensus client, built from the ground up for performance and robustness. Our ambition is to see a faster Ethereum with shorter slot times and
A little data puzzle from MPBC.
While total gas added to blocks appears roughly log-normally distributed with a fat right tail, blobs do not appear to follow a clear distribution.
Why is that?
Let's examine blobs in more detail:
The bucket containing 5-6 blobs is the largest, followed by the buckets containing 3 blobs and 1 blob.
The likely solution:
L2s typically post batches of blobs in fixed sizes that fit these large buckets.
These are then included through MPBC in one go.
For example, the standard OP batcher configuration recommends 6 blobs per TX, corresponding to the largest bucket in our data.
When I wrote "Sharding the Builder" in 2022, my naive solution to builder centralization was multiple builders competing to each win a chunk (Near nightshade style) of the execution block. There would be three competitive MEV auctions per block enforcing a gas cap on each, along with one non-competitive censorship resistance chunk. The proposer would aggregate the winning chunks. This was a multi builder design with an inclusion list in it, written before the Merge.
Seeing the concept come to fruition over the years with contributions from many brilliant researchers, developers, operators, and teams is pretty sweet.
It was even sweeter to get to talk to @mostlyblocks about @Blockspace_ETH MPBC design and its growing adoption (Shout out to TOOL and BuilderNet as well!) We spent a good chunk of the episode going over the mechanism and dashboard including a few thought experiments. There is a ton of alpha in this episode if you listen carefully.
Enjoyed the conversation with aPriori!
Wide-ranging from block construction basics, to data on MPBC, down to API details.
Improving Ethereum for users is a total win<>win.
Hope the episode sheds light on how MPBC contributes to this, and where it may go.
What FOCIL does is provide hard guarantees for the transactions the Ethereum protocol sees.
What Multi-Party Block Construction (MPBC) provides is softer fast inclusion guarantees for transactions that are known by any block builder.
Now you have multiple builders contributing to blocks. In particular, the base builder and the contributing builder work with the MPBC operator and proposer to deliver the most valuable block to the Ethereum network.
In the future, both FOCIL and MPBC can continue to scale up and get bigger together, making Ethereum more robust.
In the endgame it maybe that FOCIL includers construct most of the block, with the MPBC pipeline doing the rest. The builder role then becomes an "off-to-the-side function", simply adding a few transactions to capture MEV.
@mostlyblocks from @Blockspace_ETH touches on these topics and more as he eloquently provides a comprehensive first principles overview of MPBC on Ethereum in this quintessential episode of Credible Commitments.