> For the complete documentation index, see [llms.txt](https://wiki.gen6.life/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://wiki.gen6.life/education/support-guides/validator-hosting-and-sla-guide.md). # Validator Hosting & SLA Guide Running a Gen6 validator is an important part of supporting the network. Validators help secure the ecosystem, maintain infrastructure and participate in the long-term growth of Gen6. For users who do not want to run or host their own validator, Gen6 is preparing a list of trusted **SLA Validator Providers** in this wiki. These providers can help operate and maintain a Gen6 validator on your behalf, making it easier to participate in the network without managing the technical setup yourself. We will list the Gen6 SLA validators in this wiki, so you can contact them if you don't want to run/host your Validator on your own. Currently, we have partnered with 5 trusted entities that will offer running Gen6 (and other) validators for you. ### What Is an SLA Validator Provider? An SLA Validator Provider is an external infrastructure partner that offers validator hosting and maintenance services. This may include: * validator node setup; * hosting and uptime monitoring; * software updates; * basic infrastructure maintenance; * technical support; * validator operation guidance. This option is designed for users who want validator participation, but prefer to rely on experienced infrastructure providers instead of running the validator independently. ### Current Status At the moment, Gen6 has partnered with **5 entities** that plan to offer validator hosting services for Gen6 and other blockchain networks. We will publish the list of available SLA Validator Providers in this wiki so community members can contact them directly. ### Estimated Cost The expected monthly cost for running **1 SLA-hosted validator** is currently estimated to be approximately: > **$35 – $80 per month** The final cost may depend on the provider, server specifications, support level, and additional services included. ### Important Note Gen6 does not require every validator owner to use an SLA provider. You are free to run and host your validator independently if you have the technical knowledge and infrastructure to do so. In fact, this is the preferred way for security and decentralization. The SLA provider option is simply a more convenient path for users who want professional hosting support. ### In Short > **You can run your Gen6 validator yourself (best) or pay an SLA Validator Provider to handle the technical operation for you.** The goal is to make validator participation accessible, reliable and scalable as the Gen6 network grows. ## Running Your Own Validator If you prefer to operate your validator independently, Gen6 fully supports self-hosting. Please note that self-hosting is only available for validators with 100% ownership rights. Validators with shared ownership (for example, 50% ownership) cannot be self-hosted, as they represent a shared validator managed by a single Blockchain Administrator. Running your own validator gives you complete control over your infrastructure and contributes directly to the decentralization, resilience and security of the Gen6 network. Before getting started, make sure you have a suitable VPS or dedicated server, a stable internet connection and the recommended operating system. While running your own validator requires basic Linux and server administration knowledge, the installation process has been designed to be as simple as possible. ### **Step 1**: Renting and setting up the VPS \ Rent a VPS, then install the operating system on it. **Recommended specs**: * AMD, 2 vCPU, 4 GB RAM, 80 GB SSD * ⚠️ This value may change over time as Gen6 node requirements grow — always check the current recommendation. **Recommended OS**: Debian 13. Stop the VPS → install OS → select Debian 13 → set the root password → install → start the VPS. Wait until the server shows a RUNNING status. ### Step 2: SSH into VPS Open a terminal (Mac: cmd+Space → Terminal) and connect to the VPS: ssh root@\ The first time, it will ask you to accept the fingerprint → type yes. Then enter the root password *(\)*. ### Step 3: Update the system apt update && apt upgrade -y This may take 1–2 minutes. Wait until you get the command prompt back.
### Step 4: Download and install Gen6 Manager The Manager automatically handles node download, key generation, chainspec setup, and on-chain registration.\ \ **Link**: *⚠️*Secure Notice!*⚠️* Before downloading the Gen6 Manager, always verify that you are using the official download link through **Gen6 RealSeal**. This ensures the download source has been officially verified and has not been modified. **RealSeal verification**: ** \ **Installation in Terminal:** curl -fsSL -o gen6-manager\ chmod u+x gen6-manager\ ./gen6-manager install **The installer asks two questions**: * *“Did you read and understood the text above?”* → type YES → Enter * *“Do you wish to start the Gen6 Manager now?”* → type YES → Enter The installer then adds the Podman repository in the background, installs dependencies, starts Podman, and prints: *“Installation complete.”* — answering YES to this as well starts the service, and the Manager’s address is displayed: Service should be available at: \
### Step 5: Open an SSH tunnel and activate the Manager \ The Manager’s web interface is only accessible through an SSH tunnel. Open a new terminal tab *(cmd+T)* and run: ssh -L \:127.0.0.1:\ root@\ This command both logs into the VPS AND opens the tunnel — this window must be left open. Then open the Manager URL in your browser *(\)*. On the “Welcome” screen, the “Register with remote service” panel appears, with an “Activation password” field: *“Please register your manager with the remote service. Use the password you received from Gen6.”* Enter the password you received from Gen6 (\), then click Register — this activates the Manager. ### Step 6: Adding and activating validator Before adding a validator in the Manager, get your validator ID ready: you can find it at . By default, an average user will only have the Validator ID available — the keys/secrets are provided by Gen6 itself. ***Gen6 shares these exclusively via NCrypt***, and only with the legitimate owner of the validator. If you don’t have such a secret, the “Setting up your own keys” step below can be skipped — in that case the Manager will generate the required keys itself during setup. Next, in the Gen6 Manager interface *(left-hand menu)*, go to Services → Validators. Click “Show available validators” — the available validator cards will appear (with the validator ID, e.g. GSV108, GSN038, and the chain they belong to, e.g. Gen6 Public Chain / Gen6 Development Chain): * *✅ green checkmark = the node can become an active member, produce blocks, and earn rewards.* * *⚠️ red warning = the node already has a registered address — it can only be used if you have the corresponding seed phrases, otherwise it cannot participate in the blockchain.*
*(If your own validator is not listed, you can also enter the ID manually using the “Show custom validator addition” button.)* Click Add on the card of the appropriate validator ID — this adds the validator (initially in an inactive state, “Status: not running”) On the added validator’s card, click “Details & Configuration”. **On the Container config panel that opens**: * Active → switch ON * Archive → leave off, unless specifically needed * Validate → leave OFF for now * Click Save
This starts the node and synchronization — shown in the Validators list as “Status: syncing… X%” — but the validator is not yet validating.
#### Setting up your own keys *(secrets)*
This step is only needed if you received specific keys/secrets for a given validator from Gen6 *(via NCrypt, as the legitimate owner)* — for example when restoring an existing validator or rotating keys. If you don’t have such a secret, skip this section and continue at “Enabling validation.” 1. On the validator’s Details page, find the “secret-inject” (Validator secrets) section. 2. Paste in the keys/secrets you received, then click Save. 3. Click the “reinject keys node” button (red button in the “container op” section). This deletes any previous (possibly auto-generated) keys and chainspec, and queues the validator for recreation — indicated by the message *“Validator \[ID] chainspec and keys were removed, queued for recreation.”* 4. Wait until the node’s status changes from “starting” back to “running.”
#### Enabling validation **Once the reinject has completed and the node is running, go back to the Container config panel**: * Validate → switch ON * Click Save
This actually starts validating with the injected keys — the validator will then show as “active node” / running and validating in the Validators list. \ \ \ \ \