Skip to content

Validators

Infrastructure and operations

The operational stack behind reliable validation, monitoring, keys, uptime and performance.

Full validator stack

BitcoinAI validators do more than sign blocks.

  1. Governance

    Planned
    • Participate in network upgrade and governance processes according to protocol rules
  2. Multichain

    Planned
    • Process supported cross-chain messages
    • Enforce timeout / acknowledgement state
    • Verify configured interoperability routes
  3. Smart contracts

    Planned
    • Execute / verify application state
    • Enforce deterministic transitions
    • Maintain application-level settlement
  4. AI verification

    Engineering
    • Verify supported Proof-of-AI receipt structure
    • Verify commitments and signatures
    • Enforce receipt anti-replay rules
    • Verify Merkle inclusion where batching is used
  5. Bitcoin / AIPoW

    Engineering
    • Maintain required Bitcoin-aware verification state
    • Validate acceptable AuxPoW / merge-mining proof
    • Validate AIPoW epoch eligibility and work weight
    • Reject replayed or invalid claims
  6. Consensus

    Canonical
    • Participate in CometBFT-style consensus
    • Propose and vote on blocks
    • Maintain canonical state
    • Observe slashing and liveness rules

Layers are shown top to bottom; consensus is the foundation every other layer depends on.

The operators behind finality

Validators turn distributed infrastructure into one agreed network state.

Running a validator is an operational role: servers, monitoring, keys, uptime and governance all matter. Delegation allows other BTCAI holders to participate without running that infrastructure themselves.

Temporary Unsplash placeholder · Photo by Kevin Ache

Operator requirements

Validators need reliable infrastructure — not mining hardware.

Rows of validator server racks in a quiet, well-lit data-center aisle

Required / expected

  • Modern multi-core CPU
  • Substantial RAM
  • High-performance NVMe storage
  • Redundant internet connectivity
  • Static / public networking as required
  • Monitoring and alerting
  • Key management
  • Backups
  • Sentry / topology strategy where appropriate
  • Bitcoin-aware data per the final light-client implementation

Not inherently required

  • Bitcoin ASIC miner
  • GPU
  • AI model server
  • Dedicated BatteryAGI provider hardware

GPU and AI-provider hardware are only needed if the same operator chooses to provide AI services.

Testnet minimum
Not yet publishedTestnet TBD
Recommended production
Not yet publishedTestnet TBD
Archive / RPC profile
Not yet publishedTestnet TBD

No minimum hardware figures are published yet. They will come from testnet benchmarks.

Reliable validation depends on disciplined operators, monitoring systems and professional infrastructure.Photo by TECNIC Bioprocess Solutions · Unsplash

Operate professionally

Uptime, observability, key security, and upgrade discipline matter.

  • 01Uptime

    Redundant power, networking and failover planning.

  • 02Key Security

    Protected signing keys; never double-sign.

  • 03Monitoring

    Metrics, logs and health checks for every node.

  • 04Upgrade Readiness

    Follow upgrade notices and test in advance.

  • 05Network Connectivity

    Stable peering and sentry topology.

  • 06Incident Response

    Runbooks, alerts and on-call ownership.

Reference topology
Validator
  • Sentry / edge nodesPublic-facing peers
  • Monitoringe.g. Prometheus, Grafana
  • Alertinge.g. an alerting service
  • Key managemente.g. HSM / remote signer
  • Backup / snapshotState snapshots
  • Bitcoin-aware verification servicesPer final light-client design

Tools named are examples only · Operator choice / implementation dependent.

Performance matters

Stake determines capacity. Performance determines whether that stake is fully effective.

Current design

Validator weight equals effective stake times performance factor.

Possible performance inputs:AvailabilityMissed-block rateCorrect participationProtocol complianceTestnet TBD

Softer · reward weight

Performance weighting

May reduce reward weight. Final scoring coefficients are not yet set.

Effective stake 10M BTCAI at different performance factors
  • 100%10M
  • 90%9M
  • 75%7.5M

Performance factor → resulting validator weight (BTCAI-equivalent)

Illustrative factors only — they show the mechanism, not a published scoring rule.

Serious violations

Proposed

Slashing

May apply to serious violations according to final protocol rules.

  • Double signing / equivocation
  • Provably malicious consensus behaviour
  • Other explicitly defined violations

Final slashing matrix — proposed / pending testnet specification

Downtime slashing is not assumed; it applies only if the final rules say so.

Jail / re-entry rulesTestnet TBD