> For the complete documentation index, see [llms.txt](https://docs.ramestta.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.ramestta.com/welcome-to-ramestta/validate/how-to-become-a-validator-testnet.md).

# How to Become a Validator(Testnet)

In order to become a Ramestta Network validator (on the Testnet), you must stake a [**minimum of 10K** ](#user-content-fn-1)[^1]**RAMA**. Remember you will need test RAMA and MATIC on the Polygon Mumbai network. 

You can claim test MATIC at <https://mumbaifaucet.com/>\
You can claim test RAMA at [https://testnet.ramascan.com/](https://ramascan.com/tokens)[faucet](https://beta.shibariumtech.com/faucet)

**During Testnet**, anyone can become a validator (there's up to 10 slots). \
While this is a test environment, validators who don't behave correctly can be turned off to allow others to join the board.\
\
Also remember that during Testnet, validators will be receiving test Bone (they have no real monetary value).

1. Users can stake test RAMA using the Validator Dashboard.
2. Users are able to login using MetaMask or any wallet that has Wallet Connect enabled. In order to log in, users must use the same address where their tokens are stored.

Once you login , you will see the landing page and an option to become a Validator.

<figure><img src="/files/Cb80Rsl1XpKwX8FkwH7Y" alt=""><figcaption></figcaption></figure>

3. You can initiate the process by clicking Become a validator. Initially, you will be asked to configure the node.

<figure><img src="/files/DtO0ahDe9TrwrSNUZgrb" alt=""><figcaption></figcaption></figure>

4. Select Ansible or Binaries for setting the node.
5. Next button will be enabled.

<figure><img src="/files/zo0DD5nRShVXoHVkMv0j" alt=""><figcaption></figcaption></figure>

6. Clicking on Next will send you to next step, where you can add Validator details and the staking amount.
7. Confirm the checkbox and click on continue.

<figure><img src="/files/0mcvB8xAo7ctepRayep0" alt=""><figcaption></figcaption></figure>

8. The next section will appear after you click continue, where all the details are required.

<figure><img src="/files/aVukqDpI2YjcpMdPXzAG" alt=""><figcaption></figcaption></figure>

9. Upon clicking on next, you will be directed to the required staked amount section, where you can also enter the maximum amount by clicking the max button, the minimum staked amount is 10k.

<figure><img src="/files/I1A8uhAmBYlXtN6V7I5X" alt=""><figcaption></figcaption></figure>

10. Next you need to approve the permission from MetaMask.

<figure><img src="/files/IOH0HepPmHzDXiatynmJ" alt=""><figcaption></figcaption></figure>

<figure><img src="/files/rybvCv56myuOF7p1WBH1" alt=""><figcaption></figcaption></figure>

11. After confirming the transaction the data will get saved in db.

<figure><img src="/files/jsaJelxDf0hWpMjLZHum" alt=""><figcaption></figcaption></figure>

13. Confirm the transaction.

<figure><img src="/files/VBjw6QWR8aEAzmLnfivg" alt=""><figcaption></figcaption></figure>

14. As soon as the transaction is confirmed, the setup of the node will be completed.

<figure><img src="/files/VBjw6QWR8aEAzmLnfivg" alt=""><figcaption></figcaption></figure>

[^1]:


---

# 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.ramestta.com/welcome-to-ramestta/validate/how-to-become-a-validator-testnet.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.