EIPs VS besu

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

Daily Goerli: I've been testing this PR for besu for the past several days, and the stability of nimbus-besu has improved substantially. Looking forward to it getting merged into main.

Check out the Layered TX pool PR for more details and benchmarks - https://github.com/hyperledger/besu/pull/5290

you can check this spreadsheet for a comparison https://github.com/hyperledger/besu/files/11137473/Layered.Transaction.Pool.metrics.ods

Yes, it's gotten better. I don't recommend pairing with nimbus until this issue gets fixed or prysm until something is done to reduce the amount of time it takes to recover from being offline for a day or more.

Daily Goerli: On Friday, I reported a RocksDB issue that was causing besu to error and exit immediately. The bad commit has been identified and a fix has been issued. lodestar-nethermind somehow ended up on an invalid fork which isn't resolved by restarting either client. Waiting to see how each client team responds and if they need more info, but might need to do a resync.

https://github.com/hyperledger/besu 148 contributors

Download links and release notes here: https://github.com/hyperledger/besu/releases/tag/23.1.2

Now running into this error on my freshly synced Besu 23.1.0. 😔️