Files
aitbc/apps/blockchain-node
aitbc a9adcc17b7
Some checks failed
Blockchain Synchronization Verification / sync-verification (push) Failing after 3s
Cross-Chain Functionality Tests / test-cross-chain-sync (push) Failing after 4s
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 3s
Cross-Chain Functionality Tests / aggregate-results (push) Has been skipped
Cross-Node Transaction Testing / transaction-test (push) Successful in 4s
Deploy to Testnet / deploy-testnet (push) Successful in 1m16s
Integration Tests / test-service-integration (push) Successful in 2m10s
Multi-Chain Island Architecture Tests / test-multi-chain-island (push) Failing after 2s
Multi-Node Blockchain Health Monitoring / health-check (push) Successful in 3s
Multi-Node Stress Testing / stress-test (push) Successful in 4s
Node Failover Simulation / failover-test (push) Failing after 2s
P2P Network Verification / p2p-verification (push) Successful in 2s
Python Tests / test-python (push) Failing after 43s
Security Scanning / security-scan (push) Successful in 39s
fix: ensure session_scope uses chain-specific databases for multi-chain support
- Modified main.py to pass chain_id to session_factory lambda functions
- Fixed session_scope calls in _ensure_genesis_for_chains, block processing, and proposer initialization
- Added debug logging to sync.py to track database queries during bulk sync
- Fixed state root validation skip during bulk import with skip_state_root_validation parameter

This fixes the issue where all chains were using the same default database,
causing cross-chain data corruption and sync failures.
2026-05-09 20:44:58 +02:00
..

Blockchain Node

Documentation has moved to: docs/apps/blockchain/blockchain-node.md


This file has been migrated to the central documentation location. Please update your bookmarks and references to point to the new location.

For the complete documentation including architecture, setup, API reference, and troubleshooting, see the Blockchain Node documentation.