THALER
Sign in

Validator onboarding

Preflight guide — registration not yet open.

This guide is a preflight. No validator installer is released and the registration steps have not yet been tested from an outside host. Running the follower node never gives voting power. Test TLR has no value; there are no rewards and this is not mainnet.

Live network facts

Chain ID
7121905
Genesis SHA-256
3cc2331b84b05ecf621421bb38f439264069dff50f74b837130080a6a4d29852
Native denomination
atlr (TLR, 18 decimals)
Seed peer
49b38c8c3e5b04efc8fcb9d2d5bd7091bc4536c9@167.99.189.84:27656
Validator set today
1 validator, 100 TLR bonded
Staking parameters
Max 100 validators · 21-day unbonding

Readiness checklist

Validator onboarding is not complete. Items marked Pending are waiting on the operator; this page will not mark them done without a real test.

  • VerifiedChain ID, genesis hash and seed peer publishedValues on this page match the running pilot.
  • VerifiedFollower node release (pilot r2, Linux x86-64)Public download with SHA-256 checksum.
  • VerifiedStaking parametersObserved: max 100 validators, 21-day unbonding, 1 validator with 100 TLR bonded.
  • PendingFollower on an independent Windows (WSL2) PCNot yet tested outside the team's machines.
  • PendingRequired self-bond amount for new validatorsOperator has not set it. 100 TLR is today's single validator, not a requirement.
  • PendingOperator funding processHow new operators receive bond funds is not published.
  • PendingIndependent validator hostsNo second validator on a separate host has joined yet.
  • PendingKey generation and backup procedureExact commands not published. Each validator must create its own keys.
  • PendingRegistration (create-validator) commandNot tested from an outside host; not published.
  • PendingSigning and health checks after joiningNot yet demonstrated for a second validator.

Joining does not promise equal voting power or any rewards. Voting power follows bonded stake.

  1. 1. Use your own host and public IP

    Ubuntu 24.04 x86-64 on a machine you control. One directly connected node per public IP, so a validator cannot share an IP with another node. Keep it online and its clock synced.

  2. 2. Install and sync the follower node

    Install the public follower package from the Developers page. Confirm the genesis hash above matches, then wait until http://127.0.0.1:29657/status reports catching_up: false and the height keeps rising. Restart once and confirm the node keeps the same identity.

  3. 3. Create your own validator identity

    Generate a new consensus key and a new operator account on your host (exact commands pending). Never register a follower using another node's validator identity, and never copy priv_validator_key.json or signing state from another node — two nodes signing with one key can be punished as double-signing.

  4. 4. Get operator funding

    Pending operator: the required self-bond amount and how operators receive it are not published yet. The faucet's 1 TLR is for testing transfers, not for bonding.

  5. 5. Register and self-bond (pending activation test)

    Registration uses the node's own CLI to submit a create-validator transaction with your consensus key and self-bond in atlr. The exact command will be published here after the team tests it from an outside host.

    Fees must be nonzero. A bank transfer with gas 200,000 and fee 2matlr was accepted; a minimum gas price of 0 does not mean transactions are free.

  6. 6. Check health

    Confirm your validator appears in the active set with the expected voting power, blocks continue, your node signs, and it stays healthy after a restart. Use Explorer to watch blocks.