Biconomy uses a proxy contract approach to enable meta-transactions on your DApp. The two major implications it has on you as a developer are:
- Any transactions made by the user will have
fromparameter set as the user's proxy contract instead of user's account
- Biconomy runs the relayers and pays Gas fee upfront which is recovered from the DApp on monthly basis
- The smart contract accepting signed transactions will require no changes in the smart contract code whatsoever
The following tutorial builds upon a previous tutorial [link], where we built an Airbnb smart contract, followed by [link], where we deployed the complete DApp.
Biconomy offers their SDK that makes this integration seamless, called Mexa.
Integration with Mexa is a two step process:
- Register your DApp on Mexa Dashboard, a dashboard for developers, and copy API Key generated for your DApp.
- Integrate Mexa SDK in your DApp code using API Key you got from dashboard.
You'll first need your deployed smart contract address and it's ABI to register on the dashboard.
Registering on Biconomy dashboard
Follow the steps here, to register an account and add a DApp to get the keys, and configure functions that will accept signed transactions.
Integrate Mexa SDK in your DApp client code
dapp-ui to configure your client code to relay transactions
You have now enabled meta transactions in your DApp. Interact with web3 the way you have been doing it.