Validators
Rewards and economics
The reward sources and stake mechanics behind validator participation, kept separate from the validator overview.
Security budget
Security should not require perpetual high inflation.
250,000
BTCAI per year · annual PoS security pool
- A fixed annual PoS security pool of 250,000 BTCAI under the current design.
- No separate Bitcoin-style PoS halving.
- If more BTCAI becomes bonded while the pool stays fixed, the base BTCAI rate from this pool naturally declines.
- Network fees and AI-service revenue can become more important as usage grows.
The pool size is a current-design parameter. Governance could change it; the page does not assume it stays fixed forever.
Base PoS rate is approximately the annual PoS pool divided by total effective bonded stake.
Simplified protocol-level modeling.
Worked example
250,000 BTCAI ÷ 100,000,000 BTCAI = 0.25% base PoS pool contribution alone.
This is the PoS security pool alone. The validator/delegator AIPoW share (60% of active distribution), BATT fee share and network fees are separate, additional streams.
Real network usage
As BitcoinAI is used, fees can become a larger part of security economics.
Transfers
Native BTCAI transactions.
Smart contracts
Contract execution and state.
AI settlement
Settlement of verified AI jobs.
Cross-chain
Interoperability messages and routes.
Appchain services
Services for connected appchains.
Future application fees
New fee classes approved through governance.
The objective is to increase the share of validator economics supported by real network activity rather than relying only on new token issuance.
Future fee revenue is not guaranteed; it depends on real network usage.
Decentralization by design
More stake increases absolute rewards — up to a 10M BTCAI effective cap.
Effective stake of validator v equals the smaller of self-bond plus delegated stake, and 10,000,000 BTCAI.
Validator weight equals effective stake times performance factor.
Validator share equals validator weight divided by the sum of all validator weights.
Stake weighting: Linear up to the effective-stake cap.
Validator A
- Actual stake
- 2M
- Effective stake
- 2M
10M capValidator B
- Actual stake
- 7M
- Effective stake
- 7M
10M capValidator C
Above cap- Actual stake
- 12M
- Effective stake
- 10M
10M cap2M above the cap adds no weight.
Effective stake (counts toward weight)Stake above the cap (no additional weight)
Stake above 10M BTCAI does not increase consensus or reward weight under the current design. Wallet UX should encourage excess delegation toward under-cap validators.
Known limitation
A per-validator cap reduces concentration at the validator-identity level but does not by itself prevent one operator from controlling multiple validator identities.
Examples are illustrative.
Secure the network
Stake BTCAI. Validate AIPoW. Share in network activity.
Validators and their delegators draw on four distinct, protocol-defined reward sources. Amounts depend on network activity; no yield is promised.
PoS Security Pool
Fixed security budget architecture — no separate PoS halving.
AIPoW Validator Share
60% of active AIPoW distribution → validators/delegators.
BATT AI Fee Share
10% of qualifying BATT AI-service fees → validators/delegators.
Network Fees
Transaction, smart-contract, AI and cross-chain fees.
Delegation
BTCAI holders can delegate without operating infrastructure.
- 1Hold BTCAI
- 2Choose Validator
- 3Delegate
- 4Validator Secures BitcoinAI
- 5Rewards Shared
21-day target unbonding period (proposed parameter).
Stake cap
10,000,000 BTCAI
maximum effective stake per validator
Rewards and voting power are linear up to the cap. Additional stake should be directed toward other validators to encourage broader distribution.
Canonical