The one statement that’s perhaps been repeated ad nauseam by more web3 projects than any other group is, “We will onboard the next billion web3 users.”
Why do Web3 Developers Need The Ultimate Toolkit?
The one statement that’s perhaps been repeated ad nauseam by more web3 projects than any other group is, “We will onboard the next billion web3 users.”
We think Madhavan Malolan of Quesbook contextualized it well when he said:
“The biggest problem isn’t bringing the next billion to web3. We need to bring only 10M developers to web3, and they will take web3 to the Billion.”
The growth of any technology relies on the success of its developers — this is especially true in Web3.
Web3 apps need to handle complex logic because central servers have been replaced with P2P networks and expensive smart contracts.
Imagine having thousands of books on a bookshelf arranged in alphabetical order. Each new book you add means you have to manually line up every single book alphabetically, all over again.
This is the web3 developer's headache. Each new Web3 protocol that gets developed has its own "bookshelf," which only compounds the time needed to maintain and grow the Web3 development ecosystem.
Don’t Rebuild the Stack, Leverage it!
One of the biggest pain points for Web3 developers is how to create a simple UX that allows easy onboarding to their dApps.
In an age of rapid, open-source, and complex web3 dApps development, there is no denying the absolute need for highly customizable and composable infrastructure toolkits.
The ultimate developer toolkit can help to abstract away all processes of creating and deploying the underlying consensus core. Pre-built modules allow flexibility and customization while optimizing for development speed and standardization.
Quick example: How it looks to build a seamless dApp UX using the ultimate Web3 toolkit
Going cross-chain in minutes? Nice!
.png)
Developers can simply plug-and-play chainless modules to leverage cross-chain message passing. No complicated dev efforts are required, and the toolkit can save development time by aggregating protocols such as Wormhole and Axelar. Just add a few lines of code and your users will never worry about chains and bridges.
This makes you ‘free’ to focus on building a beautiful front-end.
You’d be surprised, but some developers want to avoid that hassle too!
What if there was a developer toolkit that offers a 3-minute widget integration with an in-dApp UI and extremely sticky UX? Wouldn’t that be sublime?
I don’t own ETH, but can I still use your dApp?
We’ve been very vocal here at Biconomy about how dApps today require too many complicated steps in user onboarding:
1. The average Joe is expected to buy ETH
2. Pay for gas for gas fees
3. Confirm transactions
4. Manage private keys
5. Engage with multi-step transactions the first time they onboard your dApp
Abstracting this cumbersome process will greatly benefit Web 3 developers.
With an ‘Ultimate Web3 Development Toolkit’, these issues will no longer matter.
Scenario 1: 100% Gas abstraction:
Remove the no-coiner trilemma by sponsoring gas for all your users with gasless meta-transactions!
Meta transactions allow Web 3 dApps to abstract seed phrases and gas fees.
Meta transactions are created on a simple and elegant concept: Using relayers, so the users don’t need to pay gas fees themselves every step of the way. Also called gasless transactions, they involve a trusted forwarder to handle the transaction and its cost.
Scenario 2: Let your users pay for gas and offer a better UX by allowing gas payment in any ERC-20 token:
Honestly, your users don’t need to know:
1. What chains they are interacting with
2. What native tokens they need to pay gas with
The benefits? Your users experience faster onboarding, they don’t need to worry about gas, and your token enjoys increased utility.
Scenario 3: Sponsor gas with conditional logic:
Conditions allow developers to decide which users they’re willing to sponsor gas fees for within their dApp.
There may be varying reasons for doing this, but the premise is simple — to eliminate gas fees for top users. The end result is comparable to a targeted ad campaign, where developers are willing to pay a higher acquisition cost (in this case, gas fees) for users with a higher LTV as specified by the whitelist conditions.
It’s 10 pm, I don’t know where my mnemonic is, but it’s ok!
What if the Ultimate Web 3 developer toolkit could leverage Smart Contract Wallets?
Each smart contract wallet is a smart contract associated with each user's EOA (Externally Owned Account — e.g. traditional MetaMask-like wallets or addresses generated using Web3Auth flow). It is a non-custodial account and provides added security compared to EOAs with a single private key.
There are even more benefits with Smart Contract Wallets!
Eliminate security risk that comes with seed phrases and private key management. The Ultimate toolkit could offer social recovery modules (customizable logic) and allow developers to choose a social recovery method based on trusted contracts, third parties, etc.
The user deposits funds using a fiat on-ramp, centralized exchange, or from any other EOA on the same chain. In this case, the wallet will be created when the user does their first transaction from the wallet. The underlying infrastructure will identify this case and append a wallet creation transaction along with the user’s first action.
Ser, this is a ONE-click transaction
With EOAs, you need the contract you want to interact with to support multi-calls to be able to batch transactions. With AA, you get this for free: Just pass an entire array of functions+parameters to your transaction and see the magic happen.
Now you can approve+transfer+revoke in a single transaction rather than three ?
Combined with session keys and other hybrid tech, including MetaMask Snap, users will be able to create their smart accounts and sessions, allowing interactions with any application similar to web2 applications. All interactions will be one-click interactions without any signatures or gas fees.
What can the Ultimate Developer Toolkit do for Games?
2 words: Session keys!
The idea of session keys is that the dApp generates the temporary key in the user's browser and prompts the user to approve the keys with a set of underlying conditions.
For example, the dApp receives permission to sign all transactions for the next 10 mins while making a particular call. It is up to the user to approve or decline. If approved, the dApp can send the interaction directly to your account, approving the transaction automatically.
While session keys achieve all of this, they also enable tighter security since the dApp can only execute the approved conditions.
Imagine this playing out in an on-chain high-frequency game where you’ll need to sign transactions. Imagine clicking “approve” 200 times on MetaMask just to play a game.
With session keys, every interaction is pulled behind the scenes ensuring a seamless experience with some very powerful network effects!
Will the Ultimate Developer Toolkit Be Reliable or Scalable?
At Biconomy, we’re grateful for a runway of 2.5 years of live testing products, best-in-class infrastructure, and a strong community network and feedback.
We’re super proud to be providing development tools that are powering projects like dYdX, Perpetual Protocol, Sandbox, Curve Finance, Coinshit UNXD, Aavegotchi, and more.
