<aside> ❗ This is an evolving document. Open up a discussion thread on Biconomy Forum; the specification will evolve with your contributions

</aside>

What is it?

The Biconomy Relayer Protocol is a network of computers that run multiple instances of the Biconomy relayer specification. These computers are referred to as nodes, and their primary purpose is to listen to clients for user transactions containing a set of instructions for on-chain execution and to carry out those instructions.

What is a relayer, and why is it needed?

All EVM transactions must be signed using an externally owned account (EOA). The EOA must have gas tokens to pay for transactions, and the set of functions an EOA can handle is limited. In order to offer web3 users a better experience, Biconomy leverages a standardized set of EVM configurations in order to allow an entity other than the user’s EOA to sign and pay for transactions on their behalf. This entity is referred to as a meta transaction “relayer” or sometimes an “executor.” Accounts of the future would be smarter than EOAs, and relayers would play an important role for us to achieve that vision.

Which user functions are enabled with relayers?

Some typical use cases made better/possible with a relayer:

1. User transaction fee subsidies
2. Transaction fees paid in ERC 20 tokens
3. Cross-chain message passing and token transfers
4. Protocol automation (keeper services)
5. DevOps automation (e.g. including L2 state writes to L1)

Protocol Actors

Third-Party relayers (Node Operators): tx relay infrastructure provided to the Biconomy Relay Network by a non-dApp entity that is not affiliated with the Biconomy Foundation.

Delegators: Stake $BICO tokens by delegating them to top-performing node operators that agree to share network fees and rewards in return.

Developers: applications/independent devs that integrate Biconomy Relay Network Infrastructure

End-Users: the entity that initiated the tx

Biconomy DAO: entity responsible for the governance of the Biconomy Relay Network.