EIPs VS 1559-outreach

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

If I became a HOP delegate, this would be my first time doing any type of delegated governance work. So I can understand some hesitation in delegating to a new coming. However, between the general knowledge throughout my history in the space and my involvement in other projects I think I can do a good job at it. Some examples where I've been part of projects to better the Ethereum ecosystem include content creation for Support1559.org (no longer functional, so here is the GitHub referencing that as part of a bigger EIP1559 signaling project), ethsunshine.com (commits), and ethmerge.com (joint commit). I also took a stab an aggregating commitments to 22% staking caps (GitHub Page), as well as am one of the multisig members of the EVMavericks project. Those have all had varying degrees of success, but they have been steps in my goal of being more than a passive investor. As noted above, I think trying out the delegate space is sort of a new mountain to conquer, hence my hemming and hawing about it broadly.

u/superphiz made a post 'yesterday' (yup, that time of night where it's technically yesterday but I didn't sleep and it's way past my bedtime) about asking staking entities to limit validator control to 22% of the network. I decided to make a GitHub list inspired by https://github.com/ethereum-cat-herders/1559-outreach/blob/main/README.md to track entities that have committed to the 22% limit.

Trent Van Epps and Tim Beiko catalog application sentiment on #EIP1559: "Almost every project / team supports this change".

Trent Van Epps has put together a GitHub catalog of applications & projects that have shown their support of EIP-1559 – HERE!

I don't really know much about how GitHub works but I think clicking the "Issue" tab and clicking "New Issue" will do it. However, I think they really want you to use "Pull Requests" based on https://github.com/ethereum-cat-herders/1559-outreach/issues/1

The 1559 Support GitHub looks to have added 1inch within the last hour. As well as Hayden Adams from Uniswap supporting on Twitter. (Do note, some at Uniswap were neutral and that's why Uniswap isn't a full "Support" on the GitHub).