852f2e5a8a
Some checks failed
Cross-Node Transaction Testing / transaction-test (push) Has been cancelled
Deploy to Testnet / deploy-testnet (push) Has been cancelled
Documentation Validation / validate-docs (push) Has been cancelled
Documentation Validation / validate-policies-strict (push) Has been cancelled
Multi-Node Stress Testing / stress-test (push) Has been cancelled
Node Failover Simulation / failover-test (push) Has been cancelled
Integration Tests / test-service-integration (push) Has been cancelled
Security Scanning / security-scan (push) Has been cancelled
Python Tests / test-python (push) Has been cancelled
CLI Tests / test-cli (push) Has been cancelled
Blockchain Synchronization Verification / sync-verification (push) Successful in 11s
Contract Performance Benchmarks / benchmark-gas-usage (push) Successful in 1m36s
Contract Performance Benchmarks / benchmark-execution-time (push) Successful in 1m24s
Contract Performance Benchmarks / benchmark-throughput (push) Successful in 1m25s
Cross-Chain Functionality Tests / test-cross-chain-sync (push) Successful in 2s
Cross-Chain Functionality Tests / test-cross-chain-transactions (push) Successful in 5s
Cross-Chain Functionality Tests / test-cross-chain-bridge (push) Has been skipped
Cross-Chain Functionality Tests / test-multi-chain-consensus (push) Successful in 3s
Cross-Chain Functionality Tests / aggregate-results (push) Has been skipped
Multi-Chain Island Architecture Tests / test-multi-chain-island (push) Successful in 2s
Multi-Node Blockchain Health Monitoring / health-check (push) Successful in 3s
P2P Network Verification / p2p-verification (push) Successful in 2s
Smart Contract Tests / test-solidity (map[name:aitbc-contracts path:contracts]) (push) Failing after 1m28s
Smart Contract Tests / test-solidity (map[name:aitbc-token path:packages/solidity/aitbc-token]) (push) Successful in 21s
Smart Contract Tests / test-foundry (push) Failing after 20s
Smart Contract Tests / lint-solidity (push) Successful in 30s
Smart Contract Tests / deploy-contracts (push) Successful in 1m40s
Systemd Sync / sync-systemd (push) Successful in 26s
Contract Performance Benchmarks / compare-benchmarks (push) Successful in 4s
- Update workflow paths from docs/openclaw to docs/hermes - Rename skill prefixes from openclaw-* to hermes-* - Update agent skill references in refactoring and analysis docs - Rename OPENCLAW_AITBC_MASTERY_PLAN.md to reflect hermes branding - Update CLI examples and command references throughout documentation
Blockchain Documentation
Generated: 2026-03-08 13:06:38 Last Updated: 2026-04-22 Total Files: 3
Documentation Files
- Adding gitea-runner as Third Blockchain Node (aitbc2) - Complete guide for adding a third node to the AITBC blockchain network, including configuration steps, issues encountered, and verification procedures.
- Blockchain Synchronization Issues and Fixes - Documentation of synchronization issues between AITBC nodes and their resolutions.
Multi-Node Blockchain Workflows
Comprehensive Windsurf workflows for multi-node blockchain deployment and operations:
- Core Setup - Prerequisites, environment configuration, and basic node setup
- Operations - Daily operations, monitoring, and troubleshooting
- Advanced Features - Smart contracts, security testing, and performance optimization
- Marketplace Testing - GPU provider testing, transaction tracking, and verification procedures
- Production Deployment - Security hardening, monitoring, and scaling strategies
- Reference - Configuration overview, verification commands, and best practices
Transaction Types
The AITBC blockchain supports the following transaction types:
- TRANSFER: Standard value transfer between accounts
- MESSAGE: On-chain messaging (value=0, fee-only) - allows sending short text messages without balance transfers
- RECEIPT_CLAIM: Claim rewards from job completion receipts
- GPU_MARKETPLACE: GPU marketplace transactions (bids, offers, purchases)
- EXCHANGE: Exchange transactions (orders, trades, swaps, liquidity)
MESSAGE Transaction Type
The MESSAGE transaction type allows users to send short on-chain messages without affecting account balances. The message is stored in the transaction payload and only the fee is deducted from the sender's balance.
Usage:
curl -X POST http://localhost:8006/rpc/transaction \
-H "Content-Type: application/json" \
-d '{"type":"MESSAGE","from":"address","to":"address","amount":0,"fee":1000,"nonce":1,"payload":{"message":"Hello blockchain!"},"sig":"signature"}'
Characteristics:
- value must be 0
- fee > 0
- recipient can be any address (or special "null" address)
- No balance transfers (only fee deduction)
- Message stored in transaction payload
Category Overview
This section contains documentation related to blockchain node setup, synchronization, and network configuration.
Manual index