**Call for a Regular AllERCDevs**

# **Call for a Regular AllERCDevs** Canonical Link: https://hackmd.io/@xinbenlv/allercdevs Form: https://docs.google.com/forms/d/e/1FAIpQLSePeryTV1tgYrzVzTWfbPoIRv8kSwKlrBW5-ALQcVaH_ZUsQg/viewform Created: 2023-04-24 Last Updated: 2023-04-24 Author: xinbenlv@, jpitts@ (please feel free to add your name if you contributed) With input from: hudsonjameson@, kdenhartog@, anettrolikova@ ## **Background** Hi friends, My name is Victor ([twitter.com/ZainanZhou](http://twitter.com/ZainanZhou),[ github.com/xinbenlv](http://github.com/xinbenlv)). I am an EIP Author and one of the EIP Editors. Among other areas, I contribute the most to ERC standards. As some of our Ethereum friends know, we have been circulating an idea to hold a regular call for people involved in authoring ERCs, building dApps and smart contracts which depend on ERCs (they almost always do!), and to advocate for open standards and interoperability. We have received quite positive responses and interests to start it, and hence the proposal. ## **Motivation** **Provide a venue for synchronized collaboration:** Today, the discussion about ERCs (the application level of Ethereum on top of EVM) is overly asynchronous. You can discuss over Github Commits, EthMagicians and OpenZeppelin forum threads, and Discord servers including Ethereum Cat Herders and Eth R&D. While the asynchronous approach has many advantages, synchronized discussion (i.e., live meetings) could provide many complements. AllCoreDevs and AllWalletDevs are great examples of how developers, when they coordinate well, can help boost a discussion, improve productivity, and accelerate social consensus forming. **Bring people together:** We also hope to make it a place where great contributors can meet each other, learn from each other, and bring a touch of humanity to each other. ## **Specifics** 1. **Target participants:** ERC authors, contributors, smart contract devs, dApp devs, researchers, security experts, economists, and generally anyone who cares for bringing more openness and interoperability to smart contract and dApp developments. 2. **Frequency:** Bi-weekly, rotating between two time zones for maximal participation (to poll the early prospective participants). 3. **Length:** 1 hour main session + 0.5 optional social/breakout room discussions. 4. **Medium:** Video Conferencing. 5. **Persistency:** Recordings, transcriptions, and summaries will be considered for public records, just like AllCoreDevs, for people who didn’t make it or who want to refer to or research them. ### **Sample outline of a session** As we want to create a space to bring the target participants together, here is a typical outline of a session: 1. 20-minute show & tell sharing: finalized ERCs, reference implementations, dApps use cases, preso from AllWalletDev or AllCoreDev for cross-layer converstion. 2. 30-minute authors of pending ERCs to share their proposal and ask for peer review comments. 3. 10-minute other discussions. 4. [optional] 30-minute breakout room social chat. ## **Sign Up Form Design** 1. Name / Alias: 2. Email: (to receive invitation) 3. Type of Involvement: * ERC author&contributor * Smart Contract Dev * dApp Dev * Wallet Dev * Researcher * Security Expert * Economists * Other 4. Domains of Interest * Wallet / Account Abstraction * DID / ENS * Approval and Authentication * NFT * Lending 5. Your Current Timezone in UTC hours 6. Preferred Time for the Events * Slot1a Tue UTC2200-2259 * Slot1b Tue UTC2300-2359 * Slot2a Thu UTC1500-1559 * Slot2b Thu UTC1600-1659 7. (Optional) Are you interested in co-organize this call? * Serve as a rotating hosting * Serve as notes taker * Help w/ inviting speakers * Help w/ proposing & sorting agenda topics * Help w/ publishing video recordings * Help w/ publishing transcription and notes * Help w/ visual design * Other 8. (Optional) ENS name: 9. (Optional) Github handle: 10. (Optional) Twitter handle 11. (Optional) LinkedIn URL 12. (Optional) Reside at (if interested in local meetup) 13. (Optional) Brief self-intro about involvement and suggestions 14. (Optional) Who should we also invite to join?