> For the complete documentation index, see [llms.txt](https://rangersprotocol.gitbook.io/rangersprotocol/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://rangersprotocol.gitbook.io/rangersprotocol/become-a-verification-node/how-to-apply-to-be-a-verification-node.md).
# How to Apply to Be a Verification Node
Step 1. Log in to with your existing account, or sign up directly if you do not have one.
Step 2. To apply to be a verification node, you need to purchase a node server first. Visit to add a credit card, upgrade your account to an Advanced one.
Step 3. Click “Nodes” on the menu on the left, and click "Create One Now" to initiate your node server purchase.
Step 4. Input corresponding parameters, click “Launch” to pay the fee, and complete the node server purchase. Select Chain: Rangers; Node Name: Custom; Region: Custom; Resource: Recommended;
Step 5. After clicking on launch, please link your account to Google Authenticator on mobile devices.
Step 6. After a successful link to Google Authenticator, click “Launch” again, and submit your payment method.
Tips:
1. Recommended configuration of Rangers verification nodes: CPU – 8 Cores, Memory – 16G, Disk – 1TB
2. When paying, the system will automatically deduct the corresponding fee from your authorized credit card. Please choose your card with discretion.
Step 7. After a successful purchase, please wait until the node server status changes from “Launching” to "Syncing" which indicates a successful node launch. Click the list to view the server details, and copy all the content in the “Address” section.
Tips:
1. If you want to cancel a node server purchase, please click the drop-down menu in the upper right corner of the Nodes List page and select "Terminate" to cancel the service.
Step 8. Enter the page, switch Metamask to Rangers Protocol Mainnet, and select the address to connect to the page.
Step 9. Input the content copied in step 9, the number of RPGs to be staked, and the reward address.
Tips:
1. To become a verification node, you need to stake at least 400 RPG. Please make sure you have enough RPGs in your wallet.
2. Please keep the private key of the reward address properly to avoid unnecessary losses.
Click "Confirm" to complete the on-chain signature transaction and successfully become a Rangers Protocol verification node.
Step 10. If you need to change the node reward address, please click [here](/rangersprotocol/become-a-verification-node/node-reward-address-replacement.md) to view the relevant guideline.
Step 11. To cancel the node service, please connect to the page with the node address and input the amount of RPGs to be unstaked. Click "Confirm" to complete the on-chain transaction, thus releasing the staked RPGs and canceling the node service.
---
# 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://rangersprotocol.gitbook.io/rangersprotocol/become-a-verification-node/how-to-apply-to-be-a-verification-node.md?ask=&goal=
```
`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.