EIPs VS execution-specs

Even more relevant would be the Ethereum Improvement Proposal repo (where people submit proposals to change the spec):

https://github.com/ethereum/EIPs

Or the go-ethereum execution client (the most popular execution client):

https://github.com/ethereum/go-ethereum

It’s early in the life of the xERC20 standard, but progress is quickly being made. The standard has been audited and is already live with a few projects. The EIP to adopt the standard has been created, and implementation has begun. Alchemix recently announced support for the xERC20 standard. And Defi Wonderland has published a suggested implementation on their GitHub. This implementation has an interface for the xERC20 contract with eight core functions that the token issuer must implement. These are functions related to setting the Lockbox contract (setLockbox), issuance limits for bridges (setLimits, mintingMaxLimitOf, burningMaxLimitOf, etc.), and the core mint and burn functions.

Check out EIP-7517: Giving Consent for AI Data Mining on the Blockchain

ERC223 is not widely implemented, and there is some debate in the ERC discussion thread about backward compatibility and trade-offs between implementing changes at the contract interface level versus the user interface.

Ethereum Improvement Proposals (EIPs): These are proposals to change various aspects of Ethereum. They often contain detailed technical discussion and can be a good resource for understanding the finer points of how Ethereum works. EIPs can be found here: https://eips.ethereum.org/

Worth looking at: EIP6968: Contract Secured Revenue on an EVM based L2 https://github.com/ethereum/EIPs/pull/6969/files

Additionally, I have made an EIP that can help standardise and maintain official contract registry of each DApp. This can help identify official contracts of a protocol vs scammers using fraud contracts but presenting like official protocol. https://github.com/ethereum/EIPs/pull/6807

EIP6780 (SELFDESTRUCT only in same transaction) is planned for the Dencun upgrade. (See Cancun included EIPs https://github.com/ethereum/execution-specs/blob/master/network-upgrades/mainnet-upgrades/cancun.md)

I followed the link which took me to https://github.com/ethereum/execution-specs/blob/master/network-upgrades/mainnet-upgrades/shanghai.md and then I started getting a little lost on the details.

@ TimBeiko: teams felt comfortable moving forward with Goerli, which we agreed to fork on March 14, 10:25pm UTC. I've opened a PR to update the specs accordingly: https://github.com/ethereum/execution-specs/pull/724

Mar 01 08:37:30 computername geth[402568]: INFO [03-01|08:37:30.496] - Homestead: 1150000 (https://github.com/ethereum/execution-specs/blob/master/network-upgrades/mainnet-upgrades/homestead.md)

EIP-4844 is slated for the Cancun Fork.

If you know Python you can read around the execution layer specs, namely for the EVM. Technically the "source of truth" for execution layer specs is still the yellow paper and EIPs but there's ongoing effort to turn it all into testable and executable specs. Otherwise this paper specifically goes in depth on the data structures used throughout the execution layer

You can see them here https://github.com/ethereum/execution-specs/pull/633/files

EIP-4895 for staking withdrawals is the main proposal members cared about, and it was upgraded from "EIPs Considered for Inclusion" to "Included EIPs" in the latest Shanghai specs. The other 3 are just minor changes.

The following EIPs have now been upgraded from "EIPs Considered for Inclusion" to "Included EIPs" in the latest Shanghai specs.