# BEP-311: Implement EIP-3651: Warm COINBASE

**URL:** https://forum.bnbchain.org/t/bep-311-implement-eip-3651-warm-coinbase/2127
**Category:** BEP
**Created:** [October 30, 2023, 7:09am UTC](https://forum.bnbchain.org/t/bep-311-implement-eip-3651-warm-coinbase/2127 "2023-10-30T07:09:09Z")
**Posts on this page:** 1
**Page:** 1

<div class="post-metadata">

### Author: ![buddh0](https://sea2.discourse-cdn.com/flex020/user_avatar/forum.bnbchain.org/buddh0/32/571_2.png) [@buddh0](https://forum.bnbchain.org/u/buddh0)
#### Post date: [October 30, 2023, 7:09am UTC](https://forum.bnbchain.org/t/bep-311-implement-eip-3651-warm-coinbase/2127/1 "2023-10-30T07:09:09Z")

</div>

## 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 `tx.to` 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](https://creativecommons.org/publicdomain/zero/1.0/).

## 9. Reference

William Morriss (@wjmelements), “EIP-3651: Warm COINBASE,” Ethereum Improvement Proposals, no. 3651, July 2021. [Online serial]. Available: [EIP-3651: Warm COINBASE](https://eips.ethereum.org/EIPS/eip-3651).