Validators

Validator FAQ

Frequently asked questions about becoming and running a validator on the BitSong network.

Validator FAQ

Find answers to common questions about the role of Validators in the BitSong network, from basic concepts and incentives to technical requirements and security practices.

If you are looking for information on how to stake your tokens without running a node, please visit the Delegators section.

General Concepts

Becoming a Validator

Testnet Repository

View the official repository for testnet details.

Validators manage two primary types of keys:

  1. Tendermint Key
    • Unique key used to sign consensus votes.
    • Associated with cosmosvalconspub.
    • Generated during node creation (gaiad init).
  2. Application Key
    • Used to sign transactions.
    • Associated with cosmospub (public) and cosmos (address).
    • Derived from gaiad keys add.
A validator's operator key uses reserved prefixes cosmosvaloper and cosmosvaloperpub.

After sending create-validator, a validator exists in one of three states:

  • in validator set Active: In the top 64. Participating in consensus, earning rewards, subject to slashing.
  • jailed Jailed: Misbehaved (downtime or double-signing). Not participating or earning.
    • Offline: Can unjail to return.
    • Double-signing: Cannot unjail.
  • unbonded Unbonded: Not in the active set. Not signing or earning. Cannot be slashed.

Self-delegation is the amount of BTSG a Validator bonds from their own wallet to themselves. It demonstrates "skin in the game."

  • Minimum: 1 ubtsg (micro-unit) or effectively 1 BTSG depending on network config.
  • Increasing: Send a delegate transaction from your application key.

Delegators typically consider:

  • Self-delegation: Higher amounts imply more trust and risk-sharing.
  • Total Stake: Indicates voting power. Larger validators produce more blocks but dilute rewards among more delegators.
  • Commission Rate: Lower commission means higher rewards for delegators, but validators need revenue to sustain operations.
  • Track Record: Seniority, uptime history, and governance participation.
  • Reputation: Audits, community contributions, and transparency.
Check out this guide on due diligence for more insights.

Responsibilities & Governance

Incentives & Rewards

Technical Requirements

Copyright © 2026