Part of the challenge in contributing to ERC/EIP is the time to build and run tests in GitHub Actions. Today I spent a night debugging the problem and was able to cut the @ethereum ERCs CI time from 10+ minutes to ~1 minute per PR. Key fixes: - git-restore-mtime restores file timestamps after checkout so Jekyll's --incremental actually works - Always use --incremental (it creates .jekyll-metadata for future runs, falls back to full build when missing) - Split actions/cache into restore + save with if: always() — because the combined action silently skips saving on failure - Scoped HTMLProofer to only check changed ERC pages Verified: Jekyll build went from 407s to 10.8s on a single-file ERC change. PR: github.com/ethereum/ERCs/pul… Full debugging journey documented in the PR description for anyone interested in Jekyll CI optimization. Same approach can be applied to ethereum/EIPs. Would love feedback from @_SamWilsn_ @lightclients @Pandapip1 and other maintainers/contributors of EIP/ERC repos and infra. @ECHInstitute , @ProtocolGuild

Excited by @openclaw and autonomous agents, but trust and safety is the next big hurdle. As an EIP Editor, I’m pleased to see a wave of new standards designed to build a trusted Agentic future. (Thank you ERC authors💗) Here is a curated list of key ERCs I follow and watch:

ERC-5485 draft updated: we’ve expanded the standard to clearly define jurisdiction, accreditation, sovereignty, and enforcement pathways for smart contracts. This brings real-world institutional structure onto Ethereum — clearer interoperability across DAOs, RWA, stablecoins, and regulated systems. Draft: eips.ethereum.org/EIPS/eip-5… Feedback welcome: ethereum-magicians.org/t/erc…

Many were complaining about EF not doing enough. I think if EF is considered the "government" of Ethereum, shrinking it is the right direction. The best thing we can do is to continue to build Ethereum from outside of EF. One should not expect EF to be the god of Ethereum, nor the sole governance of Ethereum, just like Ethereum is not just its mainnet, but also many L1s of EVMs and L2s and L3s that connect to Ethereum. Personally, I have never been employed by EF, but every time I request collaborations from Ethereum contributors, regardless of whether they are on EF payroll or not, I often receive a very warm welcome and passionate collaboration. I also built trust and friendships with other Ethereum contributors who aren't EF employees. I think this is the good vibe of Ethereum contributorship. The internet was not built in one day, and Ethereum won't be either. With the growth of so many L2s and toolings built around Ethereum, and assets brought on EVMs, I have never been more optimistic about the future of Ethereum. Among the many aspects to contribute to Ethereum, I still believe open standardization is one of the best things that blockchain and Ethereum have brought to transform the software industry, and hence ERCs are fundamentally important. Therefore, I am still building it and intend to continue working on ERCs. My friends, who is also still building ERCs in 2025?

EIP/ERC friends, come join if you are in EdCon today!

Hi ERC builders, We'd like to invite you to a new session of #AllERCDevs (S2E7) happening in about 1 hour! Join us on June 25th at 11pm UTC / 4pm US Pacific. The upcoming session highlights: - ERC-7677 Paymaster Web Service Capability presented by @lukasrosario (Lukas Rosario) - CAIP-275 Domain Wallet Authentication by Chris and David We are glad to have invited peer reviewer: @_jxom lead author and dev wevm and viem, in additional to our frequent participants. Host: @ZainanZhou Meeting Links: meet.google.com/hvy-rqbv-fnu Recordings and Notes: github.com/ercref/AllERCDevs… #AllERCDevs is a regular meetup for ERC authors to bring contributors and dApp developers together to get tech peer feedback and advocate for standardization and adoption. We usually present ERCs (including drafts and final ones), smart contracts, libraries, and dApps. See github.com/ercref/AllERCDevs for more info or how to join. Contributor needed: we continue to recruit volunteers such as meeting hosts, visual designers, tech-writers. We also look for future presenters and reviewers. If you are building dApps, CEX, DEX, Wallets, DeFi, Explorers, or anything that intends to interoperate with EVM smart contracts, please join us. DM if you want to talk more. For more details, see the agenda: github.com/ercref/AllERCDevs…, or join our TG group. t.me/+j4px1GisBSkzMDZh Appreciate our volunteers for facilitating the session too, and @EthMagicians, @EthCatHerders, @EIPfun and @Namefi_io for supporting #AllERCDevs

Who is going to Edcon.io? (July 24-31 in Tokyo)? Thinking of holding an meet up for EIP/ERC and other standardizations. #ERC #EIP #AllERCDevs #ERCRef @ERCRef @ethereum @EthCatHerders @EIPFun @ethpanda_org

Hi ERC builders, We'd like to invite you to a new session of #AllERCDevs (S2E4) on May 16th, 10pm PT / UTC 1700. Which is about 3h away from now The upcoming session we will discuss - ERC-6066 Signature Validation Method for NFTs and its adoptions by @headcpx - ERC-712 and ERC-1271 by @optimizoor - ENSIP Governance Improvement by Premm (@nxt3d ) We are glad to have invited William Entriken(@fulldecent), @frangio_, Nick Johnson(@nicksdjohnson ),@gnidan be our peer reviewers The session is run by @ERCRef with help and support from @EthCatHerders, @EthMagicians, @EIPFun, @Udaya_dev, @namefi_io @ZainanZhou will be the organizers of this session. #AllERCDevs is a regular meetup for ERC authors to bring contributors and dApp developers together to get tech peer feedback and advocate for standardization and adoption. We usually present ERCs (including drafts and final ones), smart contracts, libraries, and dApps. See [README.md](README.md), github.com/ercref/AllERCDevs… for more info or how to join. Contributors needed: we continue to recruit volunteers such as meeting hosts, visual designers, tech-writers. We also look for future presenters and reviewers. Especially, we are especially looking for future presenters of ERCs or adoptions. We also look for peer reviewers who have authored ERCs or built apps on ERCs: if you are building dApps, CEX, DEX, Wallets, DeFi, Explorers, or generally anything that intends to interoperate with EVM smart contracts, please join us. DM if you want to talk more. For more details, see the agenda: github.com/ercref/AllERCDevs…, or join our TG group. t.me/+j4px1GisBSkzMDZh

Thank you all for coming! In this latest #AllERCDevs session (S2E3), we discussed EthDebug working group, ERC-5792, ERC-1202, and related topics. 1. Victor Zhou (@ZainanZhou) started by introducing the session's goals and structure. He mentioned that ERC-6066 is similar to ERC-1271 but signed with NFTs. The session aimed to bridge gaps between ERC authors and implementers through presentations and Q&A. 2. G. Nick (@gnidan) presented on the Ethereum debugging working group, discussing the challenges in developing debugging tools for EVM languages. His focus was on creating a debugging data format that could be used to make sense of EVM bytecode in high-level terms. This is vital for understanding complex contract functions without user knowledge. G. Nick’s talk sparked a detailed technical discussion with William Entriken (@fulldecent), who emphasized focusing on practical debugging uses like transaction tracing to prevent phishing. 3. Bumblefudge (@by_caballero) spoke about interlocking ERCs (including ERC-4337 wallets) and their implications for DApp developers. The discussion covered how these ERCs could enable features like recurring payments and sponsored transactions, enhancing user experience across different platforms. 4. Premm (@nxt3d) talks about the mission to make the ENS IP process more transparent and open source. Francisco (@frangio_) inquiries on ways to enhance the openness of the ENS IP process. 5. Zainan Victor Zhou (@ZainanZhou) proposes resuming work on the ERC-1202 voting standard, drafted in 2018. He emphasizes the need for flexibility and backward compatibility with existing standards. With upcoming developments like EIP-3074, implementing a more efficient voting standard becomes feasible. Zhou seeks collaboration to advance this initiative, highlighting the group's high-quality attention and the importance of completing this work. The session was well-attended by community members, including @ZainanZhou, @fulldecent,@frangio , @pedrouid, @Vectorized, @ricmoo and @danfinlay, providing diverse feedback and raising important technical and practical points. Appreciate our volunteer @sunnyguoyuan for facilitating the session too, and @EthMagicians, @EthCatHerders, @Udaya_dev @EIPfun, and @Namefi_io for supporting #AllERCDevs. A reminder to the community: AllERCDevs is actively recruiting volunteers for various roles, including meeting hosts and tech-writers, and is calling for future presenters and peer reviewers. If you're building anything related to interoperability with EVM smart contracts, such as dApps, CEX, DEX, wallets, DeFi, or explorers, your contribution and involvement would be highly valued. For those interested in joining the conversation, contributing to the standardization, or providing peer review, don't hesitate to reach out directly through DMs or join the TG group: t.me/+j4px1GisBSkzMDZh. The agenda for future sessions can be found at github.com/ercref/AllERCDevs… on May 1st, 2024 Tuesday UTC 23:00. Agenda of next AllERCDevs is open for sign-up. Stay tuned for the next AllERCDevs meetup, promising to bring even more innovative discussions to the table. #AllERCDevs

Starting in 5min

Starting in an hour

Hi ERC builders, We'd like to invite you to a new session of #AllERCDevs (S2E2) on April 2nd, 4pm PT / UTC 2300. #AllERCDevs is a regular meetup for ERC authors to bring contributors and dApp developers together to get tech peer feedback and advocate for standardization and adoption. We usually present ERCs (including drafts and final ones), smart contracts, libraries, and dApps. See README.md github.com/ercref/AllERCDevs for more info or how to join. The upcoming session highlights - Seaport v1.6 and hooks architecture shared by @z0age from @OpenSea - ERC-7529 DNS over HTTPS for contract discovery, and eTLD+1 Association @TtheBC01 - and ERC-7529 and ERC-5169 (Client Script URI) by @victorzh. We are glad to have @optimizoor (#Solady lead dev), @ricmoo (author of #EthersJS), @gnidan (driver of @ethdebug, formerly lead maintainer of @trufflesuite ), @frangio_ (formerly lead smart contract developer of @OpenZeppelin) planning to join and help review or discuss. (and we welcome more) The session is run by @ERCRef with help and support from @EthCatHerders, @EthMagicians, @EIPFun, @Udaya_dev, @namefi_io. @ZainanZhou and @alohalily668 will be the organizers of this session. (Contributor needed: we continue to recruit volunteers such as meeting hosts, visual designers, tech-writers. We also look for future presenters and reviewers. Especially, we are looking for future presenters of ERCs or adoptions. We also look for peer reviewers who have authored ERCs or built apps on ERCs: if you are building dApps, CEX, DEX, Wallets, DeFi, Explorers, or generally anything that intends to interoperate with EVM smart contracts, please join us. DM if you want to talk more. For more details, see the agenda: github.com/ercref/AllERCDevs…, or join our TG group. t.me/+j4px1GisBSkzMDZh

Thanks everyone who came and contributed: In this S2E1 AllERCDevs session, we delved into ERC-7651, ERC-7631, and ERC-7531 and DApp permission flow by Dan Finlay. The ERC-7651 (eips.ethereum.org/EIPS/eip-7…) was introduced by @0xAcme, a spec for fractionally represented NFTs within a single contract, addressing issues of liquidity and fractional representation in the NFT space. The discussion led to @fulldecent (William Entriken) expressing concerns about creating a new ecosystem and the compatibility challenges with existing infrastructures like OpenSea. William pushed for a strong coalition to move such an ambitious standard forward. @Vectorized (Vectorized) discussed ERC-7631 (eips.ethereum.org/EIPS/eip-7…), a standard for a dual nature token pair linking ERC-20 and ERC-721 tokens while preserving full standard compliance. Francesco Sullo provided feedback, encouraging consideration of a more interconnected approach between contracts to enhance compatibility. @sullof(Francesco Sullo) presented ERC-7531 (eips.ethereum.org/EIPS/eip-7…) a proposal to resolve staked ERC-721 ownership, allowing holders to retain certain rights while their NFTs are staked. This sparked a dialogue about the desirability of such features from projects like Bored Ape Yacht Club and others in the gaming industry. Francisco Giordano suggested an opt-in feature for tokens to declare different types of rights. The session also featured insights from @danfinlay (Dan Finlay) on an early draft of DApp permissions flow (blog.danfinlay.com/a-post-sm…), highlighting the potential for a new standard that could make user interactions with DApps more secure. This led to a discussion on the importance of specifying how wallets should present authorization information to users. @ZainanZhou also suggested to share the conversation in other venues such as #AllWalletDevs ran by @_SamWilsn_ and #EthDebug ran by @gnidan that cares about readability of what's being signed in a wallet. We appreciated contributions from @ZainanZhou, @fulldecent, @0xAcme, @Vectorized, @sullof, @frangio, @Amxx , and @danfinlay, as well as all participants who engaged in the conversations. Special thanks to @alohalily668 (Lily Wang) for facilitating the session and to @EthMagicians, @EthCatHerders, @EIPfun, and @Namefi_io for supporting #AllERCDevs. Raw full transcription and recordings can be found: app.fireflies.ai/view/AllERC… and later on github.com/ercref/AllERCDevs We Look forward to the next session and the continued collaboration to shape the future of Ethereum standards: 2024-04-02 Tuesday UTC 2300 You can sign up relevant topic you want to bring at this agenda issue: github.com/ercref/AllERCDevs… Spoiler alert: one of the next topics will be @z0age to share the @opensea's latest #Seaport contract v1.6 and its hooks architect. DM me if you want a calendar invite as a reminder.