Biconomy Network is a Modular Execution Environment (MEE) - a permissionless P2P gossip network, providing crypto-economically guaranteed execution of Supertransactions.
Traditional blockchain interactions force users to sign multiple transactions across different chains while choosing between exact transactions and intent-based execution. Supertransactions eliminate these limitations. Users can now encode both specific actions and general intents spanning multiple chains in a single operation with one signature, getting the best of both worlds: precision where it matters and near-instant optimisation where speed and efficiency are crucial.
Supertransactions represent a breakthrough in blockchain technology by enabling hybrid, multi-chain execution - the ability to combine precise transaction instructions with high-level intents across any number of blockchains, all authorised with a single user signature. This unified approach allows developers to orchestrate complex single and cross-chain operations while leveraging lightning-fast intent resolution.
As a Modular Execution Environment, the Biconomy Network is the execution layer for Supertransactions.
Learn more about:
Node Operator Requirements, Specifications and How to Run a Node
debug_traceCall endpointRunning a new node instance involves several steps. We recommend first setting up the node to support testnets only. Once everything is working properly, you can proceed with activating mainnet support. It will be up to you to select whether you would like to run Node on mainnet or testnet.
The node doesn't require any specific hardware or software dependencies beyond what was mentioned in the requirements section above.
Generate a fresh EOA and fund it on all chains the Node Operator wishes to support. Caution: Store the EOA address in a secure environment and maintain it properly. Losing or mismanaging this private key will result in loss of funds.
This generated EOA will serve as an input for the Node configuration.
Clone our GitHub repository containing the Node's docker compose files using the following command on your host machine:
$ git clone <https://github.com/bcnmy/mee-node-deployment>
Before spinning up the node, configure these two main components:
Create a /chains folder in the cloned /mee-node-deployment folder and add all the chains you wish to support, as explained in the Node Deployment repository. You can use our predefined testnet or mainnet examples in your /chains folder.
Ensure the /chains folder is properly referenced in the volumes section of the docker-compose.yml file.
Supported chains are described by their respective JSON files, with each file named according to its chainId. In our examples, you'll see various {chainId}.json files demonstrating how each chain descriptor should be formatted.
Most importantly, add your RPC URL for every supported chain at the top of the chain config file. Remember that all supported RPCs must meet the requirements specified in the requirements section.
The node will accept either a plain hex private key or an encrypted private key.
If you want to work with an encrypted key, use the env-enc tool to encrypt the key using a password of your choice. The encrypted key should be stored as the /mee-node-deployment/keystore/key.enc file.
In the docker-compose.yml file, provide either:
KEY="${your plain private key}"
if you're using the plain key, or:
ENV_ENC_PASSWORD="${password you used to encrypt the key}"
if you're using the encrypted key file.
Once you've properly configured both the chains and the key, you can spin up a node by running the following command from the mee-node-deployment folder:
$ docker compose up -d
This will spin up a fresh MEE node instance. If everything is working correctly, you should see the following output in the logs:
The MEE Node will boot up and expose endpoints at:
http://localhost:3000/
To see the documentation, navigate to:
http://localhost:3000/docs
After your node is up and running, expose it on a publicly accessible API endpoint.
Send us the NODE URL (IMPORTANT) within the dedicated Discord channel #node-url - ensure that you are present in our Discord server for further coordination and comms.
Node operators should monitor the logs and ensure the node is behaving as expected.
Node operators must also monitor EOA balances across all chains and maintain at least the minimum suggested native coin balance ($100) on each chain at all times.
Remember, nodes will receive payment in various tokens for executing Supertransactions. Periodically, node operators may need to swap these received tokens for native coins and rebalance liquidity to meet the minimum funding requirement.
From time to time, we will push new updates containing not only new features but also improvements in terms of chain integrations, gas estimate accuracy, and latency.
To upgrade to a new version, simply replace the version specified in the docker-compose.yml file with the new one, then rerun the docker compose command to update your node.
We will publish changelogs with version updates and notify our partners when updates are available so you can upgrade promptly.
Details on what chains to support, please check the document below.