SEA Community Hub Proposal: Account Abstraction Hub

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:

  1. Seating for discussion groups
  2. Whiteboards
  3. Power Outlets
  4. Desks and tables
  5. TV-sized screen
  6. Signage
13 Likes

Hey all! Thanks for putting this together, the proposal looks really interesting and important!

General Update on the Process

  • The RFP is open until the end of August.
  • Shortly after this (early first week of September), we will share which Community Hub proposals got accepted and will work with those accepted teams to fine-tune the proposals/hubs and how we can best meet their production requirements.

We’ll keep you updated, should we have any more questions!

Thanks!

3 Likes

Soul wallet team would love to join the hub and support more smart wallets user and builders.

2 Likes

Me and my team at Ambire are highly interested in joining as well.

We’d love to support builders as well and participate in the AMA and guided demos.

We can further contribute with the following topics:

  • Demistifying smart account signatures and universal verification (EIP-6492) - achieving SSO that can replace Google
  • a gas-efficient approach to DKIM signature verification - achieving a practical option for account recovery
  • EIP-7702 in practice
3 Likes

This is a great initiative. Rhinestone would love to support!

We’d like to throw our hand up for all things modular accounts. Some ideas:

  • ERC-7579 technical overview, why it is important, and what it solves/unlocks
  • Smart account security and the Module Registry
  • Dev tooling for building and using smart account features
  • Using smart accounts to make credible commitments

Thanks for pulling this together!

4 Likes

Etherspot is excited to support this initiative! Our team has deep expertise in blockchain development and account abstraction. We are eager to join forces with other teams to inspire and educate developers/attendees on the potential of ERC-4337, the details of Shared mempools, the benefits and challenges of account abstraction implementation, AA dev tooling, and more.

2 Likes

The Alchemy team would also love to support an Account Abstraction Hub at DevCon! We’ll have several people from the AA team in attendance, and are happy to help cover the full stack including

  • 4337 infrastructure & 7702
  • the path to 7560 on rollups
  • modular smart accounts,
  • gas abstraction and chain abstraction
  • end user UX
4 Likes

Cool!
The AAStar community will join this hub!
We are glad to do some organization jobs.
We are building some dao/community tools based on paymaster and contract account.
Provide:

  1. Guided Demos for Cos72: https://cos72.netlify.app/, AA and passkey applications for communities, our practice demo on Passkey+BLS+DVT, not rely on EIP7212(be ready with Interchangeable off-chain encryption algorithm module for Post Quantum Computing).
  2. Office hours for this open source community tool: how to use it in 5 minutes.
  3. AMA: How can AA enhance sustainability in small communities using Cos72 and additional tools?

We will gladly help with this event as an organizer if Tom needs us(2-3 guys be BKK).

1 Like

Blocto and Bento Batch team for sure would love to contribute to this initiative along with all other AA builders. We can provide experiences and contribute as an application layer / middleware layer aspect. We’re also keen to learn more progress and future around 7702 implementation from tech/consumer side.

Hi!

Thank you so much for your patience as we review all the community hub proposals. A quick update: We have extended the deadline to submit a community hub application by one week, to the 7th of September 2024 (AoE time). You can now expect to hear from us about the outcome of your proposal by mid-September.

Thank you again! In the meantime, if you have any questions, please feel free to reach out to me.

4 Likes

Me and my team at Biconomy are highly interested to join as well. We are happy to cover the full stack. Some ideas:

ERC7579 technical overview
Modular smart accounts
Session keys and smart sessions for next generation UX
Applications of programmable MPC to empower AI agents using AA