1. Register Artifacts on the Dashboard
Changes to be done on the dashboard to enable EIP-2771 gasless transactions.
After having your dApp registered, on the “Add Smart Contract” page, enter the contract name, address and ABI, then set the Meta Transaction Type to “Trusted Forwarder” and click “Add”.
The ABI is the description of the contract interface. It contains no code and cannot be run by itself. Example of an ABI of a test contract:
TestConract.sol
ABI of TestContract.sol
pragma solidity ^0.5.0;
contract TestContract {
constructor() public { b = hex"12345678901234567890123456789012"; }
event Event(uint indexed a, bytes32 b);
event Event2(uint indexed a, bytes32 b);
function foo(uint a) public { emit Event(a, b); }
bytes32 b;
}
[
{
"type": "event",
"inputs": [
{
"name": "a",
"type": "uint256",
"indexed": true
},
{
"name": "b",
"type": "bytes32",
"indexed": false
}
],
"name": "Event"
},
{
"type": "event",
"inputs": [
{
"name": "a",
"type": "uint256",
"indexed": true
},
{
"name": "b",
"type": "bytes32",
"indexed": false
}
],
"name": "Event2"
},
{
"type": "function",
"inputs": [
{
"name": "a",
"type": "uint256"
}
],
"name": "foo",
"outputs": []
}
]
Before using this API and SDK make sure you have native meta transaction support in your smart contracts i.e., you have removed the dependency on the msg.sender property from your smart contracts.
After uploading your smart contract, the next step is to select the smart contract method which needs to be called from client side.
After adding the smart contract and methods on the dashboard, the next step is to integrate Biconomy SDK or API in the client side code.
Last modified 8mo ago