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
- 1Prepare node
Hardware profile: final testnet parameter.
Testnet TBD - 2Sync chain
State sync / snapshots planned for operators.
Planned - 3Create / secure validator keys
Operator key-management choice.
Planned - 4Acquire self-bond if required
Minimum self-bond: TBD / final testnet parameter.
Testnet TBD
Join
- 5Register validator
Registration flow ships with testnet.
Planned - 6Receive delegation
Counts toward effective stake up to 10M BTCAI.
Canonical - 7Enter active set / eligibility rules
Active-set size: TBD / final testnet parameter.
Testnet TBD
Operate
- 8Validate AIPoW + network state
Verification components still being engineered.
Engineering - 9Earn protocol / usage-based rewards
Distribution per current design; not guaranteed.
Current design - 10Maintain performance
Performance factor applies to weight.
Current design - 11Upgrade
Follow published upgrade notices.
Planned
Exit
- 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.
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.
| Parameter | Current value | Status | |
|---|---|---|---|
| AIPoW + DPoS architecture | Canonical | AIPoW + Delegated Proof of Stake | Canonical |
| 210M maximum BTCAI | Canonical | 210,000,000 | Canonical |
| 20% active AIPoW distribution | Canonical | 20% | Canonical |
| 40% work / 60% validator-delegator split | Canonical | 40% / 60% | Canonical |
| 1.00 / 1.05 work weight | Canonical | 1.00 / 1.05 | Canonical |
| 10M BTCAI effective stake cap | Canonical | 10,000,000 BTCAI | Canonical |
| 21-day target unbonding | Proposed | 21 days | Proposed |
| Annual PoS security pool | Current design | 250,000 BTCAI / year | Current design |
| Validator commission model | Current design | One commission rate per validator | Current design |
| Default commission example | Proposed | 5% | Proposed |
| Performance factor | Current design | EffectiveStake × PerformanceFactor | Current design |
| Performance scoring coefficients | Testnet TBD | Not yet set | Testnet TBD |
| Minimum self-bond | Testnet TBD | Not yet set | Testnet TBD |
| Active validator-set size | Testnet TBD | Not yet set | Testnet TBD |
| Slashing matrix | Proposed | Pending testnet specification | Proposed |
| Jail / re-entry rules | Testnet TBD | Not yet set | Testnet TBD |
| Fee distribution rules | Engineering | Being specified | Engineering |
| BATT validator share | Canonical | 10% | Canonical |
| Auto-compound UX | Planned | Wallet concept | Planned |
| Auto-delegate mined BTCAI UX | Planned | Wallet / dashboard concept | Planned |
| Testnet hardware minimum | Testnet TBD | Not yet set | Testnet TBD |
| Mainnet hardware recommendation | Testnet TBD | Not yet set | Testnet TBD |
Open parameters are shown on purpose. Each will be published before it applies on testnet or mainnet.
