oib/aitbc
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity
Files
ca7da25b9dfd4f858759b2df4314bb4d148514d2
aitbc/docs/advanced/01_blockchain/P2P_MESH_UPDATE.md
aitbc f57a8b2cc2
Some checks failed
Security Scanning / security-scan (push) Has been cancelled
Details
Documentation Validation / validate-docs (push) Has been cancelled
Details
CLI Tests / test-cli (push) Has been cancelled
Details
feat: add extended CLI command routing and update P2P architecture documentation 
- Added 135-line command interceptor in unified_cli.py for 75+ advanced commands
- Implemented routing for contract, mining, agent, network, wallet, AI, resource, ollama, marketplace, economics, analytics, automate, cluster, performance, security, compliance, script, and API commands
- Added dynamic kwargs extraction from raw_args for command parameters
- Added fallback to extended_features.py backend for stateful command
2026-04-09 13:46:49 +02:00

1.7 KiB
Raw Blame History

Direct TCP P2P Mesh Network Update

The AITBC blockchain network has been upgraded from a Redis-backed PubSub gossip model to a Direct TCP P2P Mesh Network running on port 7070.

Architecture Changes

  • The P2PNetworkService (p2p_network.py) now directly binds to port 7070 via asyncio.start_server.
  • The gossip_backend variable is now strictly set to memory since external block/transaction propagation is handled via P2P TCP streams rather than a centralized Redis bus.
  • Nodes identify themselves securely via a JSON handshake ({'type': 'handshake', 'node_id': '...'}).

Configuration Flags

The /etc/aitbc/blockchain.env configuration now requires explicit peer targeting instead of Redis connection strings:

# Removed:
# gossip_backend=broadcast
# gossip_broadcast_url=redis://localhost:6379

# Updated/Added:
gossip_backend=memory
p2p_bind_host=0.0.0.0
p2p_bind_port=7070
p2p_peers=aitbc1:7070,aitbc2:7070 # Comma-separated list of known nodes

Systemd Service

The systemd service (/etc/systemd/system/aitbc-blockchain-p2p.service) has been updated to reflect the new CLI arguments:

ExecStart=/opt/aitbc/venv/bin/python -m aitbc_chain.p2p_network \
  --host ${p2p_bind_host} \
  --port ${p2p_bind_port} \
  --peers ${p2p_peers} \
  --node-id ${proposer_id}

Troubleshooting

If a node is failing to sync, verify that TCP port 7070 is open between the nodes (ufw allow 7070/tcp), and check the mesh connectivity status using the journal logs:

journalctl -u aitbc-blockchain-p2p -n 50 --no-pager

You should see output similar to Successfully dialed outbound peer at aitbc1:7070 or Handshake accepted from node...