# Getting Started

* **For Voters/Stakers**: Staking on Viction[ Masternodes](https://vicmaster.xyz/) secures the network and earns rewards. More information can be in our guide on [how to connect wallets to ](https://docs.viction.xyz/general/how-to-connect-to-viction-network)Viction and [how to vote](https://youtu.be/tXp4WHl_sxY).
* **For Masternode Owners**: 150 Masternodes work to secure the entire Viction ecosystem. Each Masternode is a server that uses its computing power to create and sign blocks. For this contribution, Masternodes receive rewards in the form of VIC. A Masternode must satisfy [minimum system requirements](https://docs.viction.xyz/masternode/requirements) in computing power, RAM, and storage to stably maintain the network. A financial requirement of 50,000 VIC is needed to [apply](https://docs.viction.xyz/masternode/apply-your-node) to become a Masternode Candidate. Masternode owners should carefully read our dedicated guide to [running a Masternode](https://docs.viction.xyz/masternode/run-a-full-node), using [tmn](https://docs.viction.xyz/masternode/run-a-full-node/tmn) and [Docker](https://docs.viction.xyz/masternode/run-a-full-node/docker), along with our [tutorial](https://medium.com/Viction/how-to-run-a-Viction-masternode-from-a-to-z-3793752dc3d1) on the Viction Medium page and [wiki page](https://github.com/BuildOnViction/docs/wiki).
* **For Developers**: To support the development of Viction's ecosystem growth, we are maintaining a set of tutorials and documents on developing Dapps to be run on Viction. This [Dapp tutorial ](https://docs.viction.xyz/developer-guide/building-dapp-on-Viction)shows how to deploy a smart contract on Viction. For developers who are curious about Viction's source code, this [private Viction testnet](https://docs.viction.xyz/developer-guide/working-with-Viction/Viction-private-testnet-setup) guides how to set up a private Viction testnet.

| **Documentation**                                                           | Description                                                                      |
| --------------------------------------------------------------------------- | -------------------------------------------------------------------------------- |
| [General](https://docs.viction.xyz/general)                                 | Guidelines for getting started with Viction and Viction World Wide Chain         |
| [Developer Guide](https://docs.viction.xyz/developer-guide)                 | Guides to build Dapps and services using Viction and Viction World Wide Chain    |
| [Masternode](https://docs.viction.xyz/masternode)                           | Step-by-step guide on how to run and vote for Masternodes                        |
| [APIs](https://buildonviction.github.io/rpc-swagger/)                       | This document explains how to use Viction APIs                                   |
| [FAQ](https://docs.viction.xyz/faq)                                         | Frequently asked questions about Viction                                         |
| [Whitepaper and Research](https://docs.viction.xyz/whitepaper-and-research) | Official Whitepaper documents and research papers on new technology developments |
| [Legal](https://docs.viction.xyz/legal)                                     | Terms and conditions for the use of Viction technology                           |


---

# Agent Instructions: 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:

```
GET https://docs.viction.xyz/readme.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.