> For the complete documentation index, see [llms.txt](https://whitepaper.luxeya.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://whitepaper.luxeya.io/game-mechanics/pvp-battles-and-trades.md).

# PvP Battles & Trades

𝙇𝙐𝙓𝙀𝙔𝘼 PvP battles add a competitive edge, giving players more ways to win, strategize, and complete their puzzles faster.

{% stepper %}
{% step %}

### Find Your Opponent&#x20;

Need a specific NFT puzzle piece? Browse the PvP Battle Arena to find players who have what you need.
{% endstep %}

{% step %}

## Challenge & Wager

Offer a PvP duel by wagering your NFTs and/or $𝙇𝙐𝙓𝘼 against an opponent. If they accept, the battle begins.
{% endstep %}

{% step %}

## Rock-Paper-Scissors Duel

Engage in a Winner-Takes-All *Rock-Paper-Scissors* match, where strategy and quick thinking determine the outcome.
{% endstep %}

{% step %}

### Instant Smart Contract Settlement

All NFTs and tokens are locked in a smart contract, ensuring 100% fair, trustless execution—the winner takes all automatically.
{% endstep %}
{% endstepper %}


---

# 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://whitepaper.luxeya.io/game-mechanics/pvp-battles-and-trades.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.
