mev-boost VS EIPs

FYI, this is fixed now: https://github.com/flashbots/mev-boost/issues/541

mev-boost v1.6 was released yesterday - it's often the part of the validator stack that gets neglected when it comes to updates.

For the setup, did you look at https://boost.flashbots.net/ ? Pretty straightforward, and examples of configuration for validator nodes are provided for each soft (prysm, lighthouse, nimbus...). I remember using that (and potentially doing one or two little adjustments). For the explanation, flashbot doc is nice, you can start here: https://docs.flashbots.net/new-to-mev

Are you also using MEV? Because a few people seem to have this same issue. Maybe it is a MEV-Geth thing. If so could you post your MEV logs?

Ahh I see yep, on the builder side not the validator side. Validators using https://github.com/flashbots/mev-boost but whichever builder gets chosen may likely be using those (especially if flashbots has the highest bid).

Personally I think the risk benefit is better to have mevboost activated. https://github.com/flashbots/mev-boost/issues/518

The same thing happened to me, I opened an issue in prysm and in mevboost, we are not the only ones with bad luck, https://github.com/prysmaticlabs/prysm/issues/12434 https://github.com/flashbots/mev-boost/issues/516 try adding the --build-block-parallel flag I also removed 2 relays, flashboot and brute. Hopefully next time we'll have better luck. sorry for my bad english

MEV-Boost is an implementation of proposer-builder separation (PBS) built by Flashbots for proof of stake Ethereum. Validators running MEV-Boost maximize their staking reward by selling blockspace to an open market of builders.

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