40The **Valopers** contract is designed to maintain a registry of **validator profiles**. This registry provides essential information to **GovDAO members**, enabling them to make informed decisions when voting on the inclusion of new validators into the **valset**.
41
42By registering your validator profile, you contribute to a transparent and well-informed governance process within **gno.land**.
43
44---
45
46## 📝 How to Register Your Validator Node
47
48To add your validator node to the registry, use the [**Register**](` + txlink.Call("Register") + `) function with the following parameters:
58 - Must include answers to the questions listed below
59
60- **Server Type** (Infrastructure Type)
61 - Must be one of the following values:
62 - **cloud**: For validators running on cloud infrastructure (AWS, GCP, Azure, etc.)
63 - **on-prem**: For validators running on on-premises infrastructure
64 - **data-center**: For validators running in dedicated data centers
65
66- **Operator Address**
67 - The ` + "`g1...`" + ` address of your operator account (from your ` + "`gnokey`" + ` keyring)
68 - **Must be controlled by the signer** of this transaction — the realm rejects the call if the signer doesn't control that address
69
70- **Validator Consensus Public Key**
71 - Your validator node's consensus public key, in the ` + "`gpub1...`" + ` format
72 - Retrieve it by running: ` + "`gnoland secrets get validator_key`" + `
73
74### ✍️ Required Information for the Description
75
76Please provide detailed answers to the following questions to ensure transparency and improve your chances of being accepted:
77
781. The name of your validator
792. Networks you are currently validating and your total AuM (assets under management)
803. Links to your **digital presence** (website, social media, etc.). Please include your Discord handle to be added to our main comms channel, the gno.land valoper Discord channel.
814. Contact details
825. Why are you interested in validating on **gno.land**?
836. What contributions have you made or are willing to make to **gno.land**?
84
85---
86
87## 🔄 Updating Your Validator Information
88
89After registration, you can update your validator details using the **update functions** provided by the contract.
90
91---
92
93## 📢 Submitting a Proposal to Join the Validator Set
94
95Once you're satisfied with your **valoper** profile, you need to notify GovDAO; only a GovDAO member can submit a proposal to add you to the validator set.
96
97If you are a GovDAO member, you can nominate yourself by executing the following function: [**r/gnops/valopers/proposal.ProposeNewValidator**](` + txlink.Realm("gno.land/r/gnops/valopers/proposal").Call("ProposeNewValidator") + `)
98
99This will initiate a governance process where **GovDAO** members will vote on your proposal.
100
101---
102
103🚀 **Register now and become a part of gno.land’s validator ecosystem!**
104
105Read more: [How to become a validator](https://github.com/gnolang/gno/tree/master/gno.land/cmd/gnoland#become-a-validator)
106
107Disclaimer: Please note, registering your validator profile and/or validating on testnets does not guarantee a validator slot on the gno.land beta mainnet. However, active participation and contributions to testnets will help establish credibility and may improve your chances for future validator acceptance. The initial validator amount and valset will ultimately be selected through GovDAO governance proposals and acceptance.
108
109---
110
111`
112}
113
vm/qrender output, sanitized (docs/render-security.md) and displayed in an empty-sandbox iframe — scripts, forms and popups cannot run. Links stay inert in-preview; right-click to open.