> For the complete documentation index, see [llms.txt](https://ethernal-elves.gitbook.io/ethernal-elves/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://ethernal-elves.gitbook.io/ethernal-elves/archived/polygon-gameplay.md).

# Polygon Gameplay

Our Layer 2 Solution works by securely sending your Sentinel game state (DNA) between chains, Ethereum (L1) and Polygon (L2). This is achieved by only allowing a single operator to interact with the smart contract in Polygon, and by generating a single use signature to validate transactions back on Ethereum.

While your Elves are on Polygon, they are securely being held by our contract on Ethereum in a state of suspended animation. If you look up your Elf on the ETH view while it’s on Polygon you will see the last state it was in before the bridge.

When you bring assets back to ETH from Polygon, the DNA is transferred back into your Sentinel with the updated metadata.

Because the system is heavily dependent on the GUI, it is not possible to bridge out of Ethereum using the contract directly.

## **Bridging**

### Ethereum -> Polygon

1. Select *up to* 10 Elves that are not in Passive staking or in cooldown
2. **\[Transfer]** Initiate the Elves you are sending
3. **\[Approve Transfer]** Approve the Ethereum transaction and pay the minor gas fee
4. **\[Confirm Transfers]** Opens the transfer website to see approved but pending bridges
5. **\[Confirm Transfers to Polygon]** Select up to 10 Elves to finalize the bridging process

### Polygon -> Ethereum

1. The steps are the nearly identical, except when the gas fee is paid

{% hint style="danger" %}
**Warning:** When bridging an NFT from Polygon back to Ethereum, you *must* do an Action before initiating the bridge. If you do not do an Action, your NFT will get stuck.

The team will require an inconvenience tax of **10,000 $REN** to manually get the NFT unstuck (just kidding). But seriously, don't get your NFT stuck.
{% endhint %}

### Technical diagram

![](/files/G0jQynNtoEF34LsVWk9B)

{% tabs %}
{% tab title="L1 -> L2" %}
![](/files/ijSN874LFeRIiXRvEhAz)
{% endtab %}

{% tab title="L2 -> L1" %}
![](/files/xJOmxThUnrcpfMK5tl5G)
{% endtab %}
{% endtabs %}

## **Gasless Transactions**

Gameplay on Polygon is free, courtesy of the Ethernal Elves team. The operator is loaded with $MATIC to pay for all gameplay transactions done on Polygon. This does not include transactions paid with $REN, which is the token that powers the Elven universe.

{% hint style="warning" %}
**Note:** Be patient with metadata updates as it may take up to 10 minutes to process on Polygon. If you notice there are no changes to your NFT, press the top center green button to reset and restart your browser. 
{% endhint %}

{% tabs %}
{% tab title="Example gameplay on Ethereum" %}
![Diagram of an example interaction on Ethereum](/files/j5lu9SZnr1fT5OvHMyq5)
{% endtab %}

{% tab title="Example gameplay on Polygon" %}
![Diagram of an example interaction on Polygon](/files/loQyaj1wUPBh0WEEwzON)
{% endtab %}
{% endtabs %}

## **Transaction Limit**

While inconvenient for those with many Elves, for the security and stability of the project and to ensure smooth gameplay for all, there is currently a limit of **10 NFTs per transaction**.

As gameplay progresses, this may change this in the future.


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://ethernal-elves.gitbook.io/ethernal-elves/archived/polygon-gameplay.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.