> For the complete documentation index, see [llms.txt](https://docs.propw.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.propw.com/announcement/propw-highlights/publish-your-docs-94.md).

# Challenge success/failure criteria

**First challenge phase**\
\
In this phase, the challenge will fail if any dimension such as the user’s transaction data does not meet the platform’s transaction requirements. See the table for details.\ <br>

<figure><img src="https://coinw.zendesk.com/hc/article_attachments/34111039193753" alt=""><figcaption></figcaption></figure>

&#x20;

**Second challenge phase**

&#x20;

The requirements are similar to the first challenge phase. The challenge will only succeed if the user's transaction data and other dimensions meet the platform's transaction requirements. See the table for details.

&#x20;

Although there is no registration fee required for this challenge phase, if the challenge fails, the user needs to pay the registration fee again and start a new challenge from the first challenge phase.

&#x20;

<figure><img src="https://coinw.zendesk.com/hc/article_attachments/34111062219161" alt=""><figcaption></figcaption></figure>

&#x20;

**After becoming a platform trader**

&#x20;

If the user has made it this far, congratulations, the user has passed the challenge. Users will be given a PropW trader's account to trade.

&#x20;

At this stage, the platform's requirements are partially lower than those in the challenge stage, but users still need to maintain good trading habits and maintain transaction data to meet the platform's requirements. If the trading principle is triggered, the user's account will be automatically frozen by the system. risks, see table for details.

&#x20;

<figure><img src="https://coinw.zendesk.com/hc/article_attachments/34111039200281" 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 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://docs.propw.com/announcement/propw-highlights/publish-your-docs-94.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.
