Easy User Onboarding, Seamless Web3 UX, Gasless Transactions, A Chainless Experience. It’s possible!

Today all web3 dApps are moving towards providing web2-like experiences without users having to give away ownership and control over their assets. But enabling such magical experiences is tough and time-consuming. What if dApp developers could easily abstract away these complexities?

That’s where Biconomy SDK comes in.

<aside> 🛠 Biconomy SDK is the ultimate Web3 suite for developers to leverage smart accounts & simplify user journeys from complex multi-step into a simple one-click experience.

</aside>

What’s possible?

Features and modules include easy onboarding, chainless value transfers, gas fee abstraction, custom transaction bundles, conditional transaction logic, and paying gas fees in any token. It brings blockchain agnostic, web2-like experiences to your dApp in a non-custodial manner.

• Easy User Onboarding: Social wallet login, creation & recovery, and fiat on-ramps to seamlessly onboard web2 users.
• Paying gas fee in other ERC20 tokens. Users can utilize the assets in their wallets to pay gas fees.
• Chainless transactions: Cross-chain smart contract calls and transfers so the user doesn’t care which chain/L2 your dApp is on. They can simply start interacting from wherever their funds are.
• Gasless transactions: dApps can sponsor gas fees to make interactions as simple as web2 transactions.
• Custom Transaction Bundling: Allow developers to build methods to do transaction batching which enables users to execute multiple actions, even across multiple chains, in a single transaction. Eg. Approve and Deposit can be done in the same transaction.

How does it work?

The backbone of the Biconomy SDK is a Smart Contract Wallet which will ****be created when any new user onboards a dApp or your use case.

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. Users can deposit funds that no one else can control and transfer at any point in time.

Once the user onboarding is done, each user gets a smart contract wallet, rather than a simple cryptographic key pair, and dApps can customize all sorts of seamless interactions using transaction bundles via this SC wallet for the user.

Specifications of transactions done via SCW

1. There’s an EOA attached to the SC Wallet, which acts as an owner of the wallet.
2. SC Wallet supports Modules to extend wallet functionality without upgrading it. Examples of Modules are MultiSig, Social Recovery Module, Recurring Transaction Module, Transaction Automation, etc.
3. Whenever any transaction is executed via this SC Wallet, it is initiated by the EOA in the form of a cryptographic signature which is then relayed by a Relayer.