legacy-docs.biconomy.io
Open in
urlscan Pro
2606:4700::6812:18fa
Public Scan
URL:
https://legacy-docs.biconomy.io/
Submission: On October 19 via api from JP — Scanned from JP
Submission: On October 19 via api from JP — Scanned from JP
Form analysis
0 forms found in the DOMText Content
Skip to main content BiconomyDocsBlogAdd Ons SDK V4 (latest) * SDK V4 (latest) * SDK V3 Discussions DashboardGitHub SearchK * Overview * Quickstart: React * Quickstart: Core SDK * React * Paymaster * Tutorials * Smart Accounts * Bundler * Gas Estimations SDK * Dashboard * Modules * Troubleshooting * Contract Addresses * Audits * FAQ * Supported Networks & Tokens * * Overview Version: SDK V4 (latest) On this page OVERVIEW The Biconomy SDK is an Account Abstraction toolkit that enables the simplest UX on your dApp, wallet, or appchain. Built on top of ERC 4337, we offer a full-stack solution for tapping into the power of our Smart Accounts Platform, Paymasters, and Bundlers. Introduction to Account Abstraction Account Abstraction aims to enhance user experience by making user accounts more flexible and functional. Instead of using an Externally Owned Account, a Smart Contract can act as your account, powered by code instead of the Elliptic Curve Digital Signature Algorithm (ECDSA). USEROP A userOperation or a userOp is a data structure that describes a transaction to be sent on behalf of a user. It is not an actual Blockchain Transaction but has all the necessary fields to become one. These are fields like “sender,” “to,” “calldata,” “nonce,” and more. You can find the userOp structure here. ENTRY POINT CONTRACT The Entry Point contract is the singleton smart contract, the core of the Account Abstraction Flow. This singleton contract is used as an entry point to execute bundles of userOps. Refer to this blog series for a comprehensive understanding of the Entry Point. SMART ACCOUNT This smart contract acts as a user wallet where all user assets are stored. You can program it to validate transactions before executing them. Unlike a traditional wallet, the Smart Account cannot initiate a transaction independently and will need a signer to help it do so. BUNDLER The Bundler collects, bundles, and submits userOps to an EVM network. One can make a JSON RPC call to a bundler client to have a userOp added to an ERC 4337 mempool. PAYMASTER The Paymaster is a smart contract that acts as a gas tank and is used to sponsor transactions where the dApp or another third party pays the transaction fee on behalf of the user. The userOp contains a field for adding data about a Paymaster and if it should sponsor the userOp when pushed on-chain to become a transaction. A smart account sends a userOp to execute a transaction. Bundlers then watch the mempool for userOps and send them on-chain by calling the Entry Point contract. Now, you have a basic understanding of the ERC 4337 flow for account abstraction. SMART ACCOUNTS PLATFORM The Biconomy's Modular Smart Account is an ERC 4337-compliant solution that works with any Paymaster and Bundler service. Biconomy Smart Accounts are signer agnostic, which means you can use any authorization package as long as a signer is passed to our SDK during Smart Account creation. Explore different methods for creating Smart Accounts here. MODULES Modular architecture enables developers to easily & securely plug-in programmable modules to extend smart account capabilities. These modules leverage the power of Account Abstraction to allow for custom validation schemes and execution environments. As a developer, this allows you to build additional modules while leveraging existing ones like session keys, multi-chain validation, passkeys, and beyond. If you want to start diving into Smart Accounts you can begin here. For those, who are already familiar with Smart Accounts and prefer to start with modules, you can check out here or follow this step-by-step tutorial on how to build a dApp that utilizes session key modules. View the audit reports for smart accounts and Modules here. BUNDLER The Bundler is a service that tracks userOps that exist in an alternative mem pool and as the name suggests, bundles them together to send to an Entry Point Contract for eventual execution onchain. This is the final piece of the flow where after constructing your userOp and then potentially signing it with data from a paymaster, you send the userOp on-chain to be handled and executed as a transaction on the EVM. You can start using our Bundlers right now in your dApps. Each of our tutorials will walk you through how to use them in different scenarios. View the list of supported networks by Biconomy bundler here. If you are looking to integrate account abstraction using APIs, checkout the bundler APIs and tutorials. PAYMASTER Biconomy's paymaster service enables Dapps to sponsor transactions and, also allows users to use ERC-20 tokens as payment for gas. Log in to the Biconomy dashboard to get the paymaster URL and switch modes between our sponsorship and token Paymaster. Make use of different Spending limits to customize the paymaster usage. SPONSORSHIP PAYMASTER Enabling the Sponsored mode facilitates gasless transactions, eliminating the necessity for users to have native tokens to cover gas fees. Learn how to set up your paymaster here. TOKEN PAYMASTER Switching your Paymaster mode to ERC20 enables users to pay gas fees with ERC20 tokens across networks See the latest supported networks tokens here. Learn how to utilize either of these Paymasters by checking out our How To Guide on Executing transactions Next: Checkout the quickstart guide to start the integration. Next Quickstart: React * UserOp * Entry Point Contract * Smart Account * Bundler * Paymaster * Smart Accounts Platform * Modules * Bundler * Paymaster * Sponsorship Paymaster * Token Paymaster Was this page helpful? Yes No Docs * Quick Start * Smart Accounts * Paymaster * Bundler Community * Github Discussion * Discord * Twitter More * GitHub Copyright © 2024 Biconomy Built with Docusaurus.