BEP-311: Implement EIP-3651: Warm COINBASE

1. Summary

As part of Shanghai upgrade, EIP-3651: Warm COINBASE is required to be implemented to BSC.

2. Abstract

The COINBASE address shall be warm at the start of transaction execution, in accordance with the actual cost of reading that account.

3. Motivation

Direct COINBASE payments are becoming increasingly popular because they allow conditional payments, which provide benefits such as implicit cancellation of transactions that would revert.
But accessing COINBASE is overpriced; the address is initially cold under the access list framework introduced in EIP-2929.
This gas cost mismatch can incentivize alternative payments besides ETH, such as ERC-20, but ETH should be the primary means of paying for transactions on Ethereum.

4. Specification

At the start of transaction execution, accessed_addresses shall be initialized to also include the address returned by COINBASE (0x41).

5. Rationale

The addresses currently initialized warm are the addresses that should already be loaded at the start of transaction validation.
The ORIGIN address is always loaded to check its balance against the gas limit and the gas price.
The address is always loaded to begin execution.
The COINBASE address should also be always be loaded because it receives the block reward and the transaction fees.

6. Backwards Compatibility

There are no known backward compatibility issues presented by this change.

7. Security Considerations

There are no known security considerations introduced by this change.

8. License

The content is licensed under CC0.

9. Reference

William Morriss (@wjmelements), “EIP-3651: Warm COINBASE,” Ethereum Improvement Proposals, no. 3651, July 2021. [Online serial]. Available: EIP-3651: Warm COINBASE.

1 Like