- Add Step 12: Chain ID Configuration Verification
- Include detection of chain ID inconsistencies between nodes
- Add automatic chain ID synchronization procedures
- Include configuration file verification and fixes
- Add cross-chain communication testing
- Provide warnings for null chain ID issues
- Ensure both nodes operate on same chain (ait-mainnet)
This section addresses the chain ID null issue and ensures
both nodes are properly configured for the same blockchain
network with verification and troubleshooting procedures.
- Add Step 11: Blockchain Synchronization Verification
- Include genesis block verification to ensure same blockchain
- Add height difference monitoring and automatic sync completion
- Include cross-node blockchain data verification
- Add wallet consistency checks across nodes
- Provide success criteria for blockchain synchronization
- Ensure both nodes are operating on identical blockchain data
This section ensures both aitbc1 and aitbc nodes are fully synchronized
and operating on the same blockchain with verification procedures.
- Add Step 10: Gift Delivery Completion with 3-phase approach
- Include complete sync verification and transaction monitoring
- Add transaction resubmission with correct nonce handling
- Include final verification with success criteria
- Add comprehensive troubleshooting for gift delivery
- Provide automated gift delivery monitoring and verification
This section ensures the 1000 AIT gift is successfully delivered
to the aitbc wallet with proper verification and fallback mechanisms.
- Add comprehensive transaction verification and mining monitoring
- Add advanced monitoring section with real-time blockchain monitoring
- Add performance testing section with transaction throughput testing
- Add network statistics and genesis wallet status checks
- Include detailed step-by-step transaction verification process
- Add final verification commands for complete workflow validation
The workflow now provides complete monitoring, performance testing,
and transaction verification capabilities for production deployment.
- Add batch sync optimization for faster initial setup
- Add complete sync section for full demonstration
- Add enhanced final verification with network health checks
- Add success criteria section with clear validation metrics
- Add Step 8 for complete sync continuation
- Include transaction verification and balance checking
- Add quick health check commands for validation
- Provide comprehensive workflow completion summary
This workflow now provides a complete, tested, and optimized
multi-node blockchain deployment with all necessary verification
steps and success criteria.
- Add prominent section about genesis block architecture
- Clarify that only aitbc1 should have the genesis block
- Explicitly warn against copying genesis block to follower nodes
- Explain wallet attachment process and coin access mechanism
- Detail how new wallets attach to existing blockchain
- Emphasize that AIT coins are transferred, not created
- Add specific DO NOT and INSTEAD examples
- Include wallet attachment explanation in wallet creation section
This prevents critical architecture mistakes and ensures proper
blockchain setup with single genesis source and correct wallet
attachment process.
- Add comprehensive systemd fixes for main files, drop-ins, and overrides
- Include keystore password file creation in pre-flight setup
- Add detailed troubleshooting section with specific solutions
- Update genesis creation to use Python script with automatic address extraction
- Update wallet and transaction creation to use Python scripts (CLI not fully implemented)
- Add comprehensive performance optimization section
- Include monitoring and metrics commands
- Add system resource optimization tips
- Provide real-time monitoring commands
- Include network and database performance tuning
This workflow is now more robust, efficient, and includes solutions
for all issues encountered during the first run.
- Add comprehensive pre-flight setup section covering all required steps
- Include systemd service updates, CLI setup, and config relocation
- Update aitbc1 and aitbc setup sections to reflect pre-flight completion
- Remove redundant steps from main workflow (moved to pre-flight)
- Add verification commands to ensure setup is correct
- Streamline workflow execution by handling prerequisites upfront
This makes the workflow more robust and ensures all prerequisites
are met before starting the actual blockchain deployment.
- Remove sed commands updating EnvironmentFile paths in both aitbc1 and aitbc sections
- Central .env file is already at /etc/aitbc/blockchain.env location
- Systemd services should already be configured to use standard config location
- Focus workflow on configuration file updates, not systemd modifications
- Cleaner workflow that assumes proper systemd configuration
- Remove redundant sed commands for WorkingDirectory and ExecStart
- Keep only necessary EnvironmentFile update to /etc/aitbc/blockchain.env
- Simplify systemd service configuration steps
- Remove unnecessary path updates that don't change anything
- Maintain focus on essential configuration changes only
- Replace direct Python script calls with aitbc CLI commands
- Use 'aitbc blockchain setup' for genesis block creation
- Use 'aitbc wallet create' for wallet creation
- Use 'aitbc transaction send' for sending transactions
- Remove complex manual RPC calls and private key handling
- Simplify workflow with user-friendly CLI interface
- Add AITBC CLI tool to prerequisites
- Maintain same functionality with cleaner, more maintainable commands
This makes the workflow more accessible and reduces the chance of
errors from manual private key handling and RPC formatting.
- Move central configuration from /opt/aitbc/.env to /etc/aitbc/blockchain.env
- Follow system standards for configuration file placement
- Update all workflow steps to use new config location
- Update systemd services to use /etc/aitbc/blockchain.env
- Update environment management section with new paths
- Maintain backup strategy with .backup files
- Standardize configuration location across all AITBC services
This aligns with Linux filesystem hierarchy standards where
/etc/ is the proper location for system configuration files.
- Add verification step before creating directories
- Check if /var/lib/aitbc/ structure already exists
- Provide feedback if directories need to be created
- Apply to both aitbc1 (localhost) and aitbc (remote) setup sections
- More robust directory handling for existing installations
- Remove SSH command for aitbc1 since running on localhost
- Update workflow to reflect aitbc1 is local, aitbc is remote
- Clarify genesis sync approach (aitbc syncs from blockchain, not copy)
- Update final verification section to show localhost vs remote commands
- Maintain proper separation between genesis authority (local) and follower (remote)
- Merge blockchain-node/.env.production into central /opt/aitbc/.env
- Update all blockchain paths to use standardized /var/lib/aitbc/ structure
- Remove separate .env.production file (merged into central config)
- Update systemd services to remove references to .env.production
- Standardize Coordinator API paths and RPC port (8006)
- Add trusted_proposers setting for follower nodes
- Update multi-node workflow to reflect merged configuration
- Use aitbc1genesis as default proposer in central .env
- All services now use single central .env file with standardized paths
This eliminates configuration file duplication and ensures consistent
directory structure across all AITBC services.
- Replace separate blockchain.env files with adaptations of central /opt/aitbc/.env
- Add environment configuration section explaining the centralized approach
- Update both aitbc1 (genesis) and aitbc (follower) setup to use central .env
- Add backup strategy for .env files before modification
- Remove genesis copying from aitbc1 to aitbc (follower should sync via blockchain)
- Add comprehensive environment management section with troubleshooting
- Maintain standardized directory structure while using single .env file
- Include commands for viewing and restoring .env configurations
- Comprehensive workflow for setting up two-node AITBC blockchain
- aitbc1 as genesis authority, aitbc as follower node
- Includes wallet creation, genesis setup, and cross-node transactions
- Uses standardized directory structure with /var/lib/aitbc and /etc/aitbc
- Step-by-step commands for Redis gossip sync and RPC configuration
