


Connecting the world to Ethereum.


Great thread
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.

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.


6/ Payload Sharing could also improve delivery latency and variance. These effects may crystallize in the longer term. To stay up to date, follow @blockspaceforum. To learn more, check out the MPBC docs and live-track multi-party blocks on their dashboard.

5/ We have observed slots in which the delivery fallback from Payload Sharing prevented a failed delivery. When one operator fails to release the payload in time, the other parties cover.

4/ Previously, 47% of blocks were delivered by a single relay or operator. With Payload Sharing and for MPBC blocks, this is down to 9%!

3/ As part of MPBC, operators now provide Payload Sharing, which allows the block chosen by the proposer to be shared amongst operators. This allows multiple operators to pool their resources & propagate the block across the network more reliably, improving the robustness of Ethereum.

2/ Since PBS was introduced, relays have provided validators with valuable blocks from block builders. The proposer signs the highest-bid block. The relay then propagates the block to the rest of the network with propagation frequently reliant on this single party.

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.

MPBC makes Ethereum better to use for users
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.

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.


7/ The coming weeks will bring additional improvements to performance and other areas like operator communication. As a result, we expect even more blocks and users to benefit from MPBC going forward.

6/ MPBC is improving UX transparency beyond single-party block construction. Inclusion Tracing allows users to check how transactions eligible for MPBC are handled by operators. See last week’s announcement for more:
1/ MPBC now supports Inclusion Tracing. This means that users can check how transactions eligible for MPBC are handled by operators. This feature is from conversations at the Blockspace Forum, and a step towards transparent UX that goes beyond single-party block construction.