> For the complete documentation index, see [llms.txt](https://whitepaper.memetheftauto.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://whitepaper.memetheftauto.com/verification-platform/how-it-works.md).

# How It Works

Profile Verification & Claim

Our verification process is meticulous to ensure users profiles are not able to be falsely registered, keeping players accounts and $MTA safe. We’ve developed a multi-step validation system that will keep the integrity of this process secure.<br>

1. After joining the project’s discord, users must fill out a registration form including the rockstar profile they intend to claim and Solana wallet address that will be permanently linked to the account.
2. Once accepted, users will visit our verification platform and enter their previously provided rockstar profile name, wallet address, and game system type.&#x20;
3. Users must upload a screen recorded video showing profile name and "Cash Earned (Total Earned)" from thier GTA5 online stats.&#x20;
4. Once submitted, a random crew name will be generated. Participants must join assigned crew through the social club and add crew tag. (*Once verified, keeping the crew tag is not mandatory.*)
5. The users request to join the crew will be verified before approval of application. This proves ownership of the profile.
6. Once approved, the user will be redirected to a launchpad where a free access nft can be minted with the linked wallet.&#x20;
7. The verification platform will only allow access to the user hub if NFT is present in the linked wallet for the account. To prevent the transfer of the access nft, each will be frozen indefinitely.&#x20;
8. In the user hub, the user will be able to view the number of accumulated in game-dollars, and  conversion rate to $MTA. Once claim is live, users will also be able to acquire allocated $MTA through their hub account.&#x20;

These steps are to minimize any risk factors for fraudulent or duplicate claims, while providing simplified - *from start to finish* - steps to participate.

<figure><img src="https://386784223-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FnnRUUlcWNZHniEsvyhAM%2Fuploads%2FYHoEodPDiRV2WecMwjQg%2FIMG_4880-ezgif.com-optimize.gif?alt=media&amp;token=3ed98fdc-4901-4b18-8a12-29484588c3ad" alt=""><figcaption></figcaption></figure>

{% hint style="info" %}
Verification Access NFT (above)
{% endhint %}


---

# 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://whitepaper.memetheftauto.com/verification-platform/how-it-works.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.
