Introducing the BNB Universal Bundle Payment Contract

On the BNB chain, due to the lock of coinbase control, block builders use custom fee recipient addresses for bundles. Meaning searchers have to send different bundles with different payment strategies to each builder.

Additionally, new builders have a really hard time gaining traction because bundles need to be customized for them. As an example, BlockRazor uses the address 0x1266C6bE60392A8Ff346E8d5ECCd3E69dD9c5F20 and Club48 uses the address 0x4848489f0b2BEdd788c696e2D79b6b69D7484848.

In cooperation with Club48 we designed the following MEVCoinbase contract:

contract MEVCoinbase {
  public address public coinbase;
  // last updated block
  public uint256 public lastUpdatedBlock;
  
  constructor() {
  }

  // anyone can set the coinbase
  function setCoinbase(address newCoinbase) public {
    require(block.number != lastUpdatedBlock, "Coinbase already set");

    coinbase = newCoinbase;
    lastUpdatedBlock = block.number;
  }

  function pay() public payable {
    payable(coinbase).transfer(msg.value);
  }
}

The universal bundle payment system is deployed at [TODO].

At the beginning of each block, the builder sets the mev coinbase using a 0gwei setCoinbase transaction. Every bundle using the unified bundle system will automatically pay the correct fee recipient.