[FINAL] Proposal to enable Account Abstraction (ERC 4337) On Celo’s upcoming L2 leveraging Biconomy’s AA infrastructure

Gm everyone,

Monike here - leading enterprise and ecosystem partnerships at Biconomy. Would love to hear your thoughts and feedback regarding this proposal we’d like to submit. Thank you for your help and looking forward to supporting the Celo community and builders!

Proposal to deploy Biconomy’s AA stack on Celo’s upcoming L2

Abstract

This proposal aims to accelerate the growth and long-term adoption of the Celo ecosystem by strategically allocating CELO from the Community Fund toward the deployment of Biconomy’s Account Abstraction infrastructure on Celo’s upcoming L2, to enable builders to create web2-like UX for their dApps.

In this proposal, we’re asking for 200,000 CELO tokens to cover the integration costs of deploying our whole Account Abstraction stack (including Bundlers, Paymasters, and Smart Accounts) on the chain, and the support & maintenance of the infrastructure in the future.

Background

In alignment with Celo’s mission to bring prosperity to all, Biconomy is helping builders create seamless UX for their dApps so everyone can easily leverage the power of web3.

As pioneers of Account Abstraction (ERC-4337), we accelerate the mass adoption of Web3 by simplifying the user experience. Our decentralized UX stack equips developers with powerful tools to eliminate complexities, onboard users, and scale their dApps.

Since establishing the company in 2019, we have partnered with over 400 dApps for our Relayer SDK and API. Our partners include industry leaders such as JPMorgan, 100 Thieves, Dolce & Gabbana, and Mercedes Benz. We also collaborate with top-tier DeFi and NFT platforms like DYDX, Perpetual Finance, Curve Finance, Aavegotchi, Decentraland, Sandbox, Animoca Brands, and Zed Run. With our infrastructure, we handle more than 100,000 daily transactions and have successfully relayed over 36 million transactions. Our comprehensive and adaptable SDK and APIs serve a diverse clientele, now reaching over 3.5 million individuals.

Our latest infrastructure, the Biconomy Smart Accounts, Bundler APIs, and Paymaster APIs, revolutionize user onboarding by leveraging EIP-4337 and Smart Contract Wallets. This infrastructure allows developers to create a fully personalized transaction journey for their users, from wallet creation using social logins to batching multiple transactions into a single transaction. The result is an unparalleled user experience that is seamless and efficient, leveraged by industry leaders such as Trust wallet, Zeal wallet, JP Morgan and hundreds more. We provide services for blockchains such as Ethereum, Polygon, BNB Chain, Base, Avalanche, Optimism, and Arbitrum. Currently, we hold the majority market share across all major EVM chains. We support 25+ chains and 200+ tokens.

Docs: https://docs.biconomy.io/
Website: https://www.biconomy.io/
Twitter: x.com

Proposal

We are asking for 200,000 CELO to deploy our whole infrastructure on Celo’s upcoming L2 and unlock features (listed below) for builders and users. We will work closely with the Celo Foundation to deploy this infrastructure and support builder onboarding.

Project Goals and Aspirations

The Biconomy SDK simplifies blockchain development for dApp developers, providing an array of features that offer a seamless Web2-like experience to end-users. Once enabled within the chain, developers can build a wide range of use cases, from token transfers to smart contract interactions. The SDK is secure and reliable, ensuring dApps are safe from attacks and hacks. It is an essential tool for developers looking to build superior dApps on the blockchain.

1. Custom Signature Schemes & Biometric Passkeys - Biometric logins, BLS signature aggregation, and quantum-resistant digital signatures such as Schnorr can be supported with Biconomy. Users can enjoy a more secure and robust digital signature scheme that is simpler and less susceptible to attack vectors.

2. Gas-less transactions - Improve user onboarding and engagement with a gasless flow. With Biconomy, users can enjoy a gasless flow, making transaction execution faster and more straightforward.

3. Transactions and gas payments in non-native tokens - Allow users to pay for transactions and gas any ERC20 token (200+ tokens across 25+ chains and counting). This feature makes it easier for users to have a seamless transaction experience without having to go through the hassle of exchanging their tokens into native tokens.

4. Transaction Batching - Group common transactions to offer gas-light execution and one-click experiences. With Biconomy, common transactions can be batched to offer a gas-light execution that saves users gas fees, thereby making the transaction process more efficient.

5. MultiChain Signatures - This features allows for dispatching multiple userOps to different EVM chains and execute the same transactions on all chains in parallel, with a single user signature.

6. Session Keys - You can create a login session for your user, within which the user can use the dApp without repeatedly signing in. This feature makes it more convenient for users to use dApps without having to sign in repeatedly.

7. Automations - Users can set up recurring payments, Dollar Cost Averaging, or even CEX-like features such as automating purchase/sell based on on-chain triggers like price.

8. Limits, Allowlists, and Access Control - You can apply custom transaction execution limits and whitelist/blacklist addresses at the contract level. With Biconomy, users can enjoy more flexibility and control over their transactions, allowing them to customize their transaction execution limits and whitelist or blacklist addresses at the contract level.

Budget and Milestones

We will approach chain support with an on-chain and an off-chain tech stack. These are mutually exclusive and can be used separately or together to provide the best experience for developers. Our stack is ERC4337 compliant, it’s compatible with all ERC4337 compliant providers’ infra and Smart Accounts and we do not have any vendor lock-in for builders.

Milestones

Here’s the estimated timeline for the integration, you can find below the detailed explanation of each item.

1. Independent On-chain Stack:
The on-chain stack comprises all critical contracts necessary for EIP 4337. Once deployed, any developer or project can utilize these contracts to offer services related to 4337. The EntryPoint acts as a universal entry point for all ERC-4337-compliant smart contract wallets. Module extends the functionality of these smart accounts, and Paymasters sponsor transactions for users, enabling various use cases.

a. EntryPoint Contract (Core Singleton Contract)

Explanation:
The EntryPoint contract is a pivotal global singleton contract that acts as the universal entry point for all ERC-4337-compliant smart contract wallets. This essential component standardizes interactions between wallets and the Ethereum network and streamlines and secures transaction handling. By systematically managing multiple user operations through the EntryPoint contract’s handleOps() function, which features verification and execution loops, each operation is executed with utmost security and efficiency.

Timelines for deployment and integration: Week 2-5
Costing for deployment and future maintenance: None

b. Smart Contracts of Module & Extensions

Explanation:
Smart Contract Wallet Modules under the EIP-4337 standard are pivotal in bolstering the functionality and scalability of the blockchain ecosystem. These modules are instrumental in handling the UserOperation signatures, granting users an enhanced level of control and security over their transactions. Specifically, they provide a modular approach to wallet design, enabling customization based on user preferences. This adaptability ensures that the wallet can evolve alongside the ever-changing dynamics of the blockchain industry, further promoting seamless user interaction and safeguarding assets. You can check out our modules here.

Timelines for deployment and integration: Week 2-5
KPI : Total transactions processed via the Smart Contract Wallet Module, signifying the module’s efficiency in streamlining the transaction process as per EIP-4337.

c. Paymaster Smart Contracts

Explanation:
Paymasters play a pivotal role in sponsoring transactions for users, opening the door to various use cases, such as fee subsidies, ERC-20 token payments, off-chain payment methods, and on-chain credit services. By fostering a more inclusive ecosystem and enabling frictionless transactions for users, Paymasters drive innovation and adoption across the platform.

Timelines for deployment and integration: Week 2-5
KPI: Number of sponsored transactions processed by Paymaster contracts

d. Smart Contract Wallet Standard & Factory

Explanation:
The Smart Contract Wallet Standard establishes a comprehensive, unified framework for smart contract wallets, ensuring seamless interoperability and smooth integration within the broader ecosystem. Paired with the Wallet Factory, a contract that streamlines wallet creation by deploying standardized wallet instances, developers benefit from cost-efficient and simplified wallet deployment, significantly lowering barriers to entry.

Timelines for deployment and integration: Week 2-5
KPI: Number of wallets created using the factory.

2. Independent Off-chain Stack
We are developing an off-chain stack that includes bundlers and off-chain memepool creation. This will be offered as a service, so that other dapps can use this bundler and the entire off-chain stack even if they make their own Smart Wallets or Paymaster contracts.

The off-chain stack provides bundlers to optimize transaction processing and reduce network congestion, alternative mempool and node connectivity for efficient off-chain transaction processing, and developer tools such as a dashboard and documentation to facilitate integration.

a. Bundler API (with full backend)

Explanation:

Bundlers are essential off-chain nodes designed to optimize the Ethereum network. They constantly monitor the UserOperation mempool, intelligently grouping multiple UserOperations together. This bundling process enhances transaction processing efficiency, prioritizes fee distribution, and significantly reduces network congestion, ultimately leading to a smoother, more reliable ecosystem.

Timelines for deployment and integration: Week 4-7
KPI: Number of active bundlers and UserOperations processed by them at scale in a given timeframe

b. Aggregated Paymaster API (with full backend)

Explanation:
This API streamlines transactions, facilitating easy transitions between Sponsorship and ERC20 modes. Through our solution, users can opt for gasless transactions or utilize an array of supported ERC20 tokens for gas payments, underscoring the adaptability and user-centric design of the system. You can check out list of supported tokens here.

Timelines for deployment and integration: Week 4-7

KPI: Number of sponsored transactions processed by Paymaster API and Number of tokens supported for ERC20 gas by Paymaster API

c. Developer Tools: Comprehensive Dashboard, SDK, Documentation, and Code Samples

Explanation:
This component is focused on providing an all-in-one solution for developers by creating extensive documentation, practical code samples, and a feature-rich developer dashboard. The dashboard offers a unified view of user operations, paymasters, and bundlers, enabling developers to manage and monitor all aspects of their EIP-4337 integration seamlessly. By empowering developers with a single, intuitive interface and invaluable resources, we aim to drive innovation and adoption of the EIP-4337 infrastructure across the ecosystem.

Timelines for support: Week 4-7
KPI: The number of successful integrations

Biconomy infrastructure revolutionizes user onboarding by leveraging EIP-4337 and Smart Contract Wallets. The infrastructure simplifies blockchain development for dApp developers, providing an array of features that offer a seamless Web2-like experience to end-users. With Biconomy, developers can build a wide range of use cases, from token transfers to smart contract interactions.

Reporting

Once the proposal is approved and we can start working on the integration, we’ll provide regular updates on the Celo Governance Forum to the community after each Milestone.

Milestone 1 - Integration is scheduled
Milestone 2 - Independent On-chain Stack is deployed
Milestone 3 - Independent Off-chain Stack is deployed
Milestone 4 - Final testing and bug fixes have been completed, integration is live

Support Requirement

We require the following resources to facilitate our integration with Celo and maintain the infrastructure on the chain:

Fees - The necessary funds for this integration are 200,000 CELO. This covers integration and maintenance costs and can help kickstart the adoption of Smart Accounts on Celo’s upcoming L2.

Terms - The fees will cover the integration costs and maintenance fees of our infra on Celo’s upcoming L2 for the next 2 years after the approval of this proposal.

Disbursement - Upon accepting this proposal, an upfront amount of 200,000 CELO will be provided to kickstart the development process, and make our AA stack live on Celo.

Allocation of Funds - The whole fund will be directed towards the development, deployment, and maintenance of our infrastructure on Celo.

Edits

Addressing Governance Call Feedback

Biconomy benefits

The most affordable AA solution for builders and users
Compared to other providers, Biconomy does not charge a monthly subscription fee and our stack is available for builders, making it easy to get started with Account Abstraction even for projects without funding. Secondly, we do not charge any premiums on our Sponsorship Paymaster or the Bundler, which can reach up to 30% in additional fees with other providers.

No vendor lock-in

Compared to other providers who might not ask for grants to deploy on Celo, Biconomy’s stack is fully ERC4337 compliant and modular*, allowing developers to easily switch parts of the AA stack to other providers (ie: Safe Smart Accounts with Biconomy Bundlers and Paymasters) if they prefer to with a few lines of code.
*We’re also actively contributing to the new ERC7579 standard.

The most powerful AA infrastructure

We’re auto-scaling Bundlers to meet any demand, guaranteeing 99,99% uptime to ensure all transactions are processed within the shortest possible time. Biconomy supports the largest number of networks (30+) and tokens (200+) and continues to expand cross-chain, making it the default choice for multi-chain projects such as Trust Wallet.

Supporting AA adoption on Celo

We commit to supporting the Celo team and builders with marketing, workshops, educational content, and potentially hackathons to help AA adoption across the chain. Our world-class devrel team and integration specialists are available to help builders make the best out of our stack.

6 Likes

Hey @martinvol , I see you reviewed quite a few proposals and Anna said you’re technical so I’m wondering if you have any thoughts on this one?

Also, @harpaljadeja I heard some builders have been requesting Biconomy already? Feel free to tag them here.

@CeloAfricaDAO I’d love to hear your thoughts on this as well, we see the best use cases and largest difference for UX in projects with non-crypto native users. Anyone has been looking into this already?

2 Likes

Account Abstraction is SO important, and it is goint to have the most significant impact, to make th non-Web3 native user to join the advantages of the Web3 revolution.

1 Like

So glad to hear that you guys think so too! Excited to help make this happen!

I think that this is a vital option for product adoption, especially in the Global South. I had the opportunity to use Bitconomy’s stack in our Impactvoice.xyz’s needs assessment tool. This is a tool that we used in Nigeria in order to assist community members with proposal creations. It seemed, from our notes, that the paymaster and AA played a key role for our product user adoption. All though it was initially deployed on Optimism, we look to deploy on Celo and with Bitconomy, the transition will be a lot smoother.

2 Likes

@Decentralizedceo that’s really great to hear, thank you! Hope to deploy our stack very soon on Celo! :slight_smile:

1 Like

Hi @monika-bico

Glad to see that Biconomy is interested in deploying on CEL2.

The requested grant seems well-priced. However, it’s still critical to make sure we have sufficient demand now or a clear plan (from your side and the wider Celo ecosystem) on how Biconomy AA would play a big role in CEL2.

Could you share an overview of some Celo projects that have shown concrete demand for wanting to leverage Biconomy’s AA infra in their application?

6 Likes

I am happy to see Biconomy coming to Celo. @monika-bico answered all the questions I asked as regards flexibility of integration, support, and stability of the SDK.

4 Likes

Great to see a proposal from Biconomy!

@monika-bico thank you for explaning the roadmap, goals and allocation of funds in detail.

I do want to highlight that Celo ecosystem already has many of these features via services like Pimlico (Bundler and Paymasters) and Thirdweb (Smart Account and Factory).

Not trying to compare Biconomy and Pimlico, but Pimlico also has great support with the viem library which is very widely used among the entire Web3 ecosystem as a whole.

What are some offerings and usecases that Biconomy will unlock for the Celo ecosystem other than the existing ones?

Are there any customers of Biconomy that are looking to add Celo support and hence bring more activity/liquidity to the network? That would be a good argument to support the proposal.

P.S: Pimlico deployed on Celo for free.

4 Likes

Hi everyone, thank you all for the questions and support, changing this to FINAL now and submitting the proposal via Github shortly. Incorporated the feedback received via comments and during the Q&A on the Gov. call to the final proposal.

@harpaljadeja thank you for the questions! We’re also working with the Viem team, and it’s one of our main priorities this quarter to ensure Biconomy works seamlessly with Viem. If everything goes well it should be ready by the time the Celo integration is done.

Your concerns regarding paying for an integration that is partially supported by other providers already are completely understandable. Addressing these, I’ve incorporated the answer to the proposal above, under “Biconomy Benefits”.

Tldr: Biconomy is a more scalable, flexible, and affordable solution for both builders and users, with no vendor lock-in compared to those providers.

@LuukDAO - thank you for the feedback! Also addressed this in the Proposal, under “Supporting AA adoption on Celo”. I’ve heard from the Celo team that builders have been inquiring about Biconomy, there have been positive comments under this post as well, but unfortunately, I don’t have a specific list of projects with documented interest to share with you.

However, we’re committed to working closely with the Celo team to raise awareness (this can include social media, workshops, hackathons, etc.), educate builders and support them through the integration process in multiple ways. We’re also happy to support Cel2 by connecting you to the hundreds of projects we’re working with (as mentioned, Biconomy is popular amongst multi-chain wallets, DeFi, DEX) to help expand the ecosystem.

1 Like

Important Reminder: Transparency for Proposals

When submitting a proposal for funds, it’s crucial to disclose all Multisign addresses involved and who is behind each address.

Additionally, each individual associated with these addresses should confirm their wallet address in a comment from their Forum Account. This is a requirement from the Approvers, so let’s ensure we meet their standards for transparency.

Your cooperation is greatly appreciated.

6 Likes

Hi all, I’m Arshita Khetan, Head of Finance at Biconomy and hereby confirm the wallet address listed in the proposal belongs to me and I’m one of the signers!

3 Likes

Hi @0xGoldo , our founders have some security concerns around sharing these addresses publicly (founder doxxing). Is there a workaround for this?

Hi @monika-bico. The address you associate with the proposal multisig doesn’t matter. It has not to be the personal address that your founders are using in their everyday life but it can be a new address derived from a new seed phrase. What matters is associating a wallet to a forum response on the proposal so that voters can vet now and in the future.

2 Likes

Sharing the multisig address and signers as requested, will add it to the Proposal shortly too

Celo Safe Multisig: 0x151F6b3D9E894b7E619327EDea5D1113539c4dB3

Signers

  • Sachin Tomar, Co-founder & CTO: 0x129443cA2a9Dec2020808a2868b38dDA457eaCC7
  • Aniket Jindal, Co-founder & COO: 0x2DfC6dDd5230f391f0cb8f35095f32dD1DC3A14c
  • Ahmed Al-Balaghi, Co-founder & CEO: 0x274FB5777c24DaD3c7dF80987B9fac04931AD885
  • Arshita Khetan, Head Of Finance: 0x672386C9bCf0089516c5e6B9205Ed7512a8d1c63
1 Like

Hi, I’m Sachin Tomar, Co-founder & CTO at Biconomy and I confirm the wallet address 0x129443cA2a9Dec2020808a2868b38dDA457eaCC7 listed above belongs to me and I’m one of the signers of the multisig.

3 Likes

Hey everyone!
Love this proposal and looking forward to supporting Celo!

I’m Ahmed Al-Balaghi, Co-founder & CEO at Biconomy and I can confirm the wallet address 0x274FB5777c24DaD3c7dF80987B9fac04931AD885 listed above belongs to me and I’m one of the signers of the multisig.

Thanks again!

2 Likes

I find this comment somewhat concerning. Do the founders of a project wanting to deploy ERC-4337 on an EVM network not understand how addresses can be generated? Aren’t the founders already doxxed? I guess I can chalk it up to to it not being clear exactly what @0xGoldo was asking for here.

@0xGoldo What would be an improvement on the governance process here would be that the proposers each sign a message with the addresses wanting to be the keys of the Safe, so that we can safely know they control those addresses (at least at one point in time) so the funds have less chance of being sent to a misconfigured Safe.

To steelman the response from @monika-bico here, it would make sense for a technical founder to think “I don’t want to use an address that proves my provenance because it’s my personal address, because I know that simply rolling a virgin address and posting it in a forum has zero cost and could be done by sybils anyway, so they must be asking for an address with my identity history, which I don’t think is appropriate to provide”

I’ll take my tinfoil hat off now and see myself out =)

3 Likes

Gm, I’m Aniket Jindal, Co-founder & COO at Biconomy and I can confirm the wallet address 0x2DfC6dDd5230f391f0cb8f35095f32dD1DC3A14c listed above belongs to me and I’m one of the signers of the multisig.

1 Like

GM, Arshita Khetan here, I am the Head of finance at Biconomy and I can confirm the wallet 0x672386C9bCf0089516c5e6B9205Ed7512a8d1c63 belongs to me and I’m one of the signers of the multisig

1 Like