🥗Proposer/Builder Separation

Data Availability Sampling (DAS) reduces the burden of nodes verifying Blob, achieving low configuration and decentralized verification. However, to create a block, it is necessary to possess complete Blob data and perform encoding processing, raising significant requirements for full nodes in Origins. Proposer/Builder Separation (PBS) proposes to divide nodes into two roles: builders, responsible for packing, and proposers, responsible for proposing.

Currently, Origins nodes are divided into two types: full nodes and light nodes. Full nodes need to synchronize all data on Origins, such as transaction lists and block bodies, and they play roles in block packing and verifying. Because full nodes can see all information within a block, they can reorder or add/delete transactions to gain MEV value. Light nodes do not need to synchronize all data; they only need to synchronize block headers to verify blocks.

After implementing Proposer/Builder Separation (PBS):

Nodes with high-performance configurations can become builders. Builders only need to download Blob data for encoding and create blocks, then broadcast them to other nodes for sampling. For builders, because of the high synchronization data and bandwidth requirements, it tends to be more centralized.

Nodes with lower-performance configurations can become proposers. Proposers only need to verify the validity of data, create and broadcast block headers. For proposers, the requirements for synchronization data and bandwidth are lower, leading to decentralization.