> For the complete documentation index, see [llms.txt](https://raretyperesearch.gitbook.io/stockmon/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://raretyperesearch.gitbook.io/stockmon/hunt/pvp-coming-soon.md).

# PVP — coming soon

PVP is Stockmon’s coming-soon creature-versus-creature competition layer. You will bring an eligible Stockmon into a match while its Genesis Feed basket stays completely separate.

{% hint style="warning" %}
**PVP is coming soon.** Matchmaking, battles, rankings, rewards, items, and PVP wallet actions are not available today.
{% endhint %}

## What you see before every match

* which exact Stockmon is entering;
* which collection and token ID it belongs to;
* what ruleset and version apply;
* which traits or progression inputs matter;
* whether any fee, reward, cooldown, or consumable exists;
* what data is public;
* what can be cancelled; and
* what becomes final after the match.

If the app cannot show those rules, the match does not open.

## PVP is separate from Hunt

| Hunt                                                        | PVP                                                   |
| ----------------------------------------------------------- | ----------------------------------------------------- |
| One bounded position against an external territory or venue | Direct competition between eligible creatures         |
| Normal return and intact rescue                             | Match rules, resolution, and ranking                  |
| Position custody and reconciliation matter                  | Competitive integrity and outcome verification matter |
| Genesis Feed basket stays separate                          | Genesis Feed basket stays separate                    |

Neither system can debit a Genesis token’s sealed Feed accounting.

## What launches with PVP

PVP launches with:

1. eligibility and matchmaking rules;
2. the exact inputs that affect an outcome;
3. replay, disconnect, timeout, and dispute behavior;
4. anti-cheat and multi-account policy;
5. result provenance and receipt format;
6. ranking, season, and reset rules;
7. wallet and privacy boundaries; and
8. any economic terms, separately from cosmetic progression.

Every result names the server, oracle, randomness source, or operator decision that produced it. Stockmon does not label an opaque server result as trustless.

## `$MON`, rewards, and entry costs

PVP has no `$MON` entry fee, boost, reward, staking requirement, or pay-to-win mechanic today. The coming-soon page never asks for payment.

## Still being designed

These details are not decided:

* battle format or team size;
* real-time versus turn-based play;
* which stats derive from DNA;
* items, abilities, or energy systems;
* matchmaking rating and seasons;
* spectator or tournament features; and
* whether rewards are cosmetic, reputation-based, or economic.

Next: [Aetheryn descendants](/stockmon/aetheryn.md) or [Agent payments — coming soon](/stockmon/agent-payments-coming-soon.md).


---

# 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://raretyperesearch.gitbook.io/stockmon/hunt/pvp-coming-soon.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.