SEA Community Hub Proposal: Account Abstraction Hub
Please give a short description of the topic/cause for your Community Hub
The Account Abstraction Community Hub would be a gathering point for various sub-communities in the Account Abstraction ecosystem. This includes communities focused around development and maintenance of Account Abstraction SDKs and libraries, wallets, block indexers, bundlers, paymasters, relevant protocol standards (e.g. ERC-4337, RIP-7560, RIP-7217, ERC-6900, ERC-7579 …), dapps leveraging AA, social recovery such as ZK Email, and more.
Account Abstraction has garnered a lot of attention this past year, as many people believe it will play a key role in getting the next 1B users onchain, by removing numerous onboarding and UX pain points for users, while preserving the core values of Ethereum (censorship resistance, decentralization, privacy, etc.). There are dozens of teams building in this space, and it would be beneficial to have a dedicated space for everyone to meet and collaborate - both for those teams for cross-pollination and alignment, but also for the builders looking to use Account Abstraction in their projects and can learn and collaborate with them and other builders.
Such a space will be useful for all types of attendees, enabling a wide variety of discussions:
- Highly technical, such as native AA implementation or storage management in modular accounts
- UX design questions surrounding global vs embedded wallets
- Economics and game theory in regards to the new public mempool and paymasters design
- Security considerations around key management and account recovery
- And more
What will you offer to the Devcon attendees?
The Hub would have three primary “use cases.”
Firstly, the AA Community Hub can be a space for AA teams and sub-communities to run informal events. These teams will register the space in advance for roundtable discussions, office hours, etc. Such events would be less structured than a workshop or presentation registered specifically under the official Devcon tracks; they would be more informal, accessible, and open-ended.
Secondly, there will be a number of official AA presentations and workshops throughout Devcon, and the AA Community Hub can serve as the default follow up spot for AA track presenters to hang out after their sessions.
Finally, the AA Community Hub may serve as a default “hangout” spot or Schelling Point for AA-focused attendees.
To dig deeper into the first use case, which we expect to be the core “driver” of usage of the Community Hub: teams or individuals in the AA space may “reserve” one of five 60 minute slots per day, during which they would lead informal activities that are open to the AA community broadly.
We expect that informal activities could include:
Office hours: An AA team may host a meet-and-greet for builders who are interested in developing on top of their libraries and services, giving them a chance to ask their team both technical and non-technical questions
AMA: A chance for community members to pick the brains of relevant thought leaders in the space (e.g authors of EIPs, researchers, senior developers, etc.)
Guided demos: Informal sessions where community members can drop by the Community Hub to i.e. try out an AA application / wallet / SDK with guidance from a team member.
Fireside chats or round-table discussions: These would be guided discussions on specific topics, led by a domain expert where anyone at Devcon who is interested in the topic may participate in.
We would invite various teams from across the ecosystem to host these activities and help manage the hub. Some of them have already expressed a strong interest in taking part.
Add a rough outline of your Community Hubs program
The space will be operated from 10am - 3pm (or longer if we have support and interest from other teams).
Each day, this period is broken up into five 60 minute slots.
We’ll find four teams per day that will sign up for slots to “own” the space for 60 minutes each. During a slot, the chosen team will drive a “primary activity” (see the examples above).
Additionally, we imagine that the space will be used informally for follow ups with speakers on the official tracks, or from other side events.
List the people who will organise, oversee and be responsible for the Community Hub
The Ethereum Foundation Account Abstraction PM (Tom Teman) will take the lead, supported by his team members - the co-authors of ERC-4337 (Yoav Weiss, Dror Tirosh, Alex Forshtat and Shahaf Nacson).
In addition, we’ve already spoken with numerous other AA community members and teams in the space who said they would be happy to participate (i.e help manage the hub in addition to filling up slots). If this proposal gets accepted, we will make sure there is sufficient coverage from our community during open hours, by coordinating AA teams to sign up for slots.
List the equipment or production needs (see what’s possible in the RFP)
In decreasing order of priority:
- Seating for discussion groups
- Whiteboards
- Power Outlets
- Desks and tables
- TV-sized screen
- Signage