Skip to content

Validators

Lifecycle and status

Institutional considerations and current validator implementation status.

From candidate to active validator

A clear path from infrastructure setup to active consensus participation.

Prepare

  1. 1Prepare node

    Hardware profile: final testnet parameter.

    Testnet TBD
  2. 2Sync chain

    State sync / snapshots planned for operators.

    Planned
  3. 3Create / secure validator keys

    Operator key-management choice.

    Planned
  4. 4Acquire self-bond if required

    Minimum self-bond: TBD / final testnet parameter.

    Testnet TBD

Join

  1. 5Register validator

    Registration flow ships with testnet.

    Planned
  2. 6Receive delegation

    Counts toward effective stake up to 10M BTCAI.

    Canonical
  3. 7Enter active set / eligibility rules

    Active-set size: TBD / final testnet parameter.

    Testnet TBD

Operate

  1. 8Validate AIPoW + network state

    Verification components still being engineered.

    Engineering
  2. 9Earn protocol / usage-based rewards

    Distribution per current design; not guaranteed.

    Current design
  3. 10Maintain performance

    Performance factor applies to weight.

    Current design
  4. 11Upgrade

    Follow published upgrade notices.

    Planned

Exit

  1. 12Unbond / exit

    Target unbonding: 21 days.

    Proposed

For professional operators

BitcoinAI is designed to support professional validator infrastructure.

  • Cosmos validators
  • Institutional staking providers
  • Exchanges
  • Custodians
  • Mining pools
  • Data-center operators
  • Infrastructure companies

Future operator capabilities

Planned
  • Validator APIs
  • Monitoring endpoints
  • Structured chain metadata
  • Upgrade notices
  • Genesis files
  • State sync / snapshots
  • Sentry architecture guidance
  • Institutional key-management compatibility
  • Governance tooling

Operator registration opens with testnet. Until then, follow developer updates for the contact channel.

Reliable validation depends on professional operations, monitoring and infrastructure discipline.Photo by Lucas Franco · Unsplash

What is defined vs. what remains open

Validator economics should be transparent before mainnet.

  • CanonicalPart of the current canonical protocol design. Not yet live; may change before mainnet through the published specification process.
  • Current designThe current working value in the protocol design. Expected to hold, but may be adjusted before mainnet or by governance.
  • ProposedA proposed design parameter subject to review, governance and change.
  • PlannedPart of the current design and roadmap. Not yet launched.
  • EngineeringBeing specified and engineered. Exact parameters and rules are not final.
  • Testnet TBDNot yet set. The value will be defined in the testnet specification and published before it applies.
Validator economics parameters and their status
AIPoW + DPoS architectureCanonicalAIPoW + Delegated Proof of Stake
210M maximum BTCAICanonical210,000,000
20% active AIPoW distributionCanonical20%
40% work / 60% validator-delegator splitCanonical40% / 60%
1.00 / 1.05 work weightCanonical1.00 / 1.05
10M BTCAI effective stake capCanonical10,000,000 BTCAI
21-day target unbondingProposed21 days
Annual PoS security poolCurrent design250,000 BTCAI / year
Validator commission modelCurrent designOne commission rate per validator
Default commission exampleProposed5%
Performance factorCurrent designEffectiveStake × PerformanceFactor
Performance scoring coefficientsTestnet TBDNot yet set
Minimum self-bondTestnet TBDNot yet set
Active validator-set sizeTestnet TBDNot yet set
Slashing matrixProposedPending testnet specification
Jail / re-entry rulesTestnet TBDNot yet set
Fee distribution rulesEngineeringBeing specified
BATT validator shareCanonical10%
Auto-compound UXPlannedWallet concept
Auto-delegate mined BTCAI UXPlannedWallet / dashboard concept
Testnet hardware minimumTestnet TBDNot yet set
Mainnet hardware recommendationTestnet TBDNot yet set

Open parameters are shown on purpose. Each will be published before it applies on testnet or mainnet.