Gasless SDK (EOA)

Enable meta transactions or gasless transactions in your Dapp by integrating Gasless SDK (EOA) in your DApp in a few lines of code


Gasless SDK (EOA) enables meta transactions or gasless transactions in your DApp (Decentralized Application) out of the box without any change in your smart contracts and just a few lines of code in your DApp to integrate Gasless SDK (EOA).
By using Gasless SDK (EOA), DApp users are able to use the DApp and send transactions free of cost while developer pays the gas fee on their behalf as a part of user acquisition cost.

Let’s Get Started

  1. 1.
    Go to Dashboard to register your DApp and methods on which to enable meta transactions and copy your API Key.
  2. 2.
    Install Gasless SDK (EOA)

1. Installing and importing SDK

Gasless SDK (EOA) can be installed either via npm repository or using standalone javascript file using html <script/> tag
Standalone JS File
npm install @biconomy/mexa
// Install Biconomy
<script src=""></script>
// Import Biconomy
let Biconomy = window.Biconomy.default;

2. Initializing Gasless SDK (EOA)

You can use Gasless SDK (EOA) either with Web3.js or Ethers.js library. It works with both libraries.
import {Biconomy} from "@biconomy/mexa";
const biconomy = new Biconomy(<web3 provider>,{apiKey: <API Key>, debug: true});
web3 = new Web3(biconomy);
import {Biconomy} from "@biconomy/mexa";
const biconomy = new Biconomy(<web3 provider>,{apiKey: <API Key>, debug: true});
let ethersProvider = new ethers.providers.Web3Provider(biconomy);
Note: <web3 provider> could be window.ethereum for Metamask or portis.provider for Portis and so on. It should be a provider object not RPC url.

3. Initialize your DApp after Biconomy Gasless SDK (EOA) initialization

biconomy.onEvent(biconomy.READY, () => {
// Initialize your dapp here like getting user accounts etc
}).onEvent(biconomy.ERROR, (error, message) => {
// Handle error while initializing mexa
Congratulations 👏
You have now enabled meta transactions in your DApp. Interact with web3 the way you have been doing it.
Now whenever there is a write transaction action (registered in dashboard also) initiated from the user Gasless SDK (EOA) will ask for user’s signature either EIP-712 format or personal signature as instructed and handle the transaction rather than sending signed transaction directly to blockchain from user’s wallet.
Checkout how you can use Gasless SDK (EOA) to do gasless transactions in different ways either by sponsoring all the gas fee for your users or let your users pay the gas fee in ERC20 tokens.