Files
aitbc/docs/advanced/01_blockchain/4_consensus.md
AITBC System dda703de10 feat: implement v0.2.0 release features - agent-first evolution
 v0.2 Release Preparation:
- Update version to 0.2.0 in pyproject.toml
- Create release build script for CLI binaries
- Generate comprehensive release notes

 OpenClaw DAO Governance:
- Implement complete on-chain voting system
- Create DAO smart contract with Governor framework
- Add comprehensive CLI commands for DAO operations
- Support for multiple proposal types and voting mechanisms

 GPU Acceleration CI:
- Complete GPU benchmark CI workflow
- Comprehensive performance testing suite
- Automated benchmark reports and comparison
- GPU optimization monitoring and alerts

 Agent SDK Documentation:
- Complete SDK documentation with examples
- Computing agent and oracle agent examples
- Comprehensive API reference and guides
- Security best practices and deployment guides

 Production Security Audit:
- Comprehensive security audit framework
- Detailed security assessment (72.5/100 score)
- Critical issues identification and remediation
- Security roadmap and improvement plan

 Mobile Wallet & One-Click Miner:
- Complete mobile wallet architecture design
- One-click miner implementation plan
- Cross-platform integration strategy
- Security and user experience considerations

 Documentation Updates:
- Add roadmap badge to README
- Update project status and achievements
- Comprehensive feature documentation
- Production readiness indicators

🚀 Ready for v0.2.0 release with agent-first architecture
2026-03-18 20:17:23 +01:00

1.5 KiB

Consensus Mechanism

Understand AITBC's proof-of-authority consensus mechanism.

Overview

AITBC uses a Proof-of-Authority (PoA) consensus mechanism with:

  • Fixed block time: 2 seconds
  • Authority set of validated proposers
  • Transaction finality on each block

Block Production

Proposer Selection

Proposers take turns producing blocks in a round-robin fashion. Each proposer gets a fixed time slot.

Block Structure

{
  "header": {
    "height": 100,
    "timestamp": "2026-02-13T10:00:00Z",
    "proposer": "ait-devnet-proposer-1",
    "parent_hash": "0xabc123...",
    "state_root": "0xdef456...",
    "tx_root": "0xghi789..."
  },
  "transactions": [...],
  "receipts": [...]
}

Consensus Rules

  1. Block Time: 2 seconds minimum
  2. Block Size: 1 MB maximum
  3. Transactions: 500 maximum per block
  4. Fee: Minimum 0 (configurable)

Validator Requirements

Requirement Value
Uptime 99% minimum
Latency < 100ms to peers
Stake 1000 AITBC

Fork Selection

Longest chain rule applies:

  • Validators always extend the longest known chain
  • Reorgs occur only on conflicting blocks within the last 10 blocks

Finality

Blocks are considered final after:

  • 1 confirmation for normal transactions
  • 3 confirmations for high-value transactions

Next