> For the complete documentation index, see [llms.txt](https://docs.rallyprotocol.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.rallyprotocol.com/unity/gasless-transactions/guides/add-erc2771recipient.md).

# Add ERC2771Recipient

## Overview

Contracts that are [ERC2771](https://eips.ethereum.org/EIPS/eip-2771) compatible are natively supported by the RallyMobile SDK to perform gasless transactions. Contracts that are not ERC2771 compatible, but are whitelisted by us, can also perform gasless transactions

## If you are able to update the contract:

1. [Add `ERC2771Recipient` to your token contract](https://docs.opengsn.org/contracts/#install-opengsn-contracts) to make it compatible with our SDK. 
2. Set the trusted forwarder:
   1. Amoy: `0x0ae8FC9867CB4a124d7114B8bd15C4c78C4D40E5`   
   2. Mainnet: `0xB2b5841DBeF766d4b521221732F9B618fCf34A87`
3. [View code example](https://gist.github.com/DonGambas/230389f11dc5f10137a510527175e01e)

{% hint style="info" %}
For ERC721 contracts, follow [Opensea's guide](https://docs.opensea.io/docs/polygon-basic-integration) to enable meta transactions for your NFTs.
{% endhint %}

## If you are unable to update the contract:

Contact us on [Discord](https://discord.gg/rlynetwork) with the contract address and [gasless transaction method](/unity/gasless-transactions/guides/determining-the-gasless-transaction-method.md) (`permit` or `executeMetaTransaction`) to have it reviewed and whitelisted by our team.  


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.rallyprotocol.com/unity/gasless-transactions/guides/add-erc2771recipient.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.