476eb496e8
Some checks failed
Blockchain Synchronization Verification / sync-verification (push) Failing after 3s
Cross-Chain Functionality Tests / test-cross-chain-sync (push) Failing after 5s
Cross-Chain Functionality Tests / test-cross-chain-transactions (push) Successful in 3s
Cross-Chain Functionality Tests / test-cross-chain-bridge (push) Has been skipped
Cross-Chain Functionality Tests / test-multi-chain-consensus (push) Failing after 2s
Cross-Chain Functionality Tests / aggregate-results (push) Has been skipped
Cross-Node Transaction Testing / transaction-test (push) Successful in 3s
Deploy to Testnet / deploy-testnet (push) Successful in 1m16s
Integration Tests / test-service-integration (push) Successful in 2m8s
Multi-Chain Island Architecture Tests / test-multi-chain-island (push) Successful in 2s
Multi-Node Blockchain Health Monitoring / health-check (push) Successful in 2s
Multi-Node Stress Testing / stress-test (push) Successful in 2s
Node Failover Simulation / failover-test (push) Failing after 3s
P2P Network Verification / p2p-verification (push) Successful in 3s
Python Tests / test-python (push) Failing after 46s
Security Scanning / security-scan (push) Successful in 24s
- Modify _load_genesis_allocations_from_rpc() to extract and return genesis_state_root from RPC response - Update _initialize_genesis_allocations() to receive and store the RPC genesis_state_root - Modify _ensure_genesis_block() to use RPC-provided state_root instead of computing it locally - Remove state root recomputation after account initialization This fixes the state root mismatch between aitbc and aitbc1 genesis blocks that was preventing successful block sync. When aitbc1 bootstraps via RPC, it now uses the original genesis state_root from aitbc instead of recomputing it locally, ensuring state roots match during sync.