> For the complete documentation index, see [llms.txt](https://docs.pantherprotocol.io/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.pantherprotocol.io/docs/changelog/overview-1/stage-6.md).

# Stage 6

**Status: Testing underway**

Panther’s test network is now live on Amoy, Polygon’s test network, and can be accessed [here](https://docs.pantherprotocol.io/docs/product-and-technological-components/product-versions/v1-testnet?ref=blog.pantherprotocol.io). Due to this network change, users will need to complete the onboarding process again and activate their test zAccount. Users who are using their old accounts, however, will not have to go through PureFi credential process again and will be moved directly to the account activation. This is a one-time activity required to access Panther.  

> For the current dApp, see the [entrypoint](/docs/panther-core/testnet.md). Note that, each stage's entrypoint is deprecated in favor of the next stage.

### Functionality

Stage 6 introduces two core functionalities with some extra details on the impact to UTXO Selection:

* [Fees](#fees) 
* [AMM Refilling with Protocol Fees](#amm-refilling-with-protocol-fees)
* [Limited Subsidy Rewards](#limited-subsidy-rewards)

#### Fees Testing

This release introduces the mechanism for charging different types of fees within the simulated testnet, including Protocol Fees, Network Gas Fees, KYT fees and KYC Fees. All simulated fees are paid from the Panther Gas account in tZKP.

#### AMM Refilling with Protocol Fees Testing

Simulated protocol fees collected during the testing will be deposited into the AMM’s pool of tZKP.

#### Limited Subsidy Rewards Testing

The production (mainnet) version of Panther Protocol may include feature that will allow to introduce additional rewards to partially or fully compensate costs like Network Gas Cost, KYC, KYT and Miner fees, in service of encouraging use of the platform. Stage 6 of our testnet simulates this feature for testing purposes.

**Note:** This feature is designed to cover only tZKP-nominated fees, and will not involved test MATIC or other native test network tokens unless using the relayer service.

<figure><img src="https://3222612406-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Ffjt2vLu9LbWbcWVioR8l%2Fuploads%2FdhGZGoZDsuerQyvRYIHH%2Fimage.png?alt=media&amp;token=7e5ce9b1-03dc-46f0-9432-393261821ce3" alt=""><figcaption></figcaption></figure>


---

# 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.pantherprotocol.io/docs/changelog/overview-1/stage-6.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.