The latest articles on DEV Community by Seiji Ito (@seiji_ito_2ab3f2c476cf649). https://dev.to/seiji_ito_2ab3f2c476cf649 https://media2.dev.to/dynamic/image/width=90,height=90,fit=cover,gravity=auto,format=auto/https:%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F1677647%2Ff2d6c9a5-3dc5-4b4a-ac7b-c09456f98fed.jpg https://dev.to/seiji_ito_2ab3f2c476cf649 en Seiji Ito Tue, 06 Oct 2026 23:14:45 +0000 https://dev.to/seiji_ito_2ab3f2c476cf649/how-do-you-connect-a-blockchain-node-with-multiple-trading-bots-without-adding-tcphttp-overhead-54db https://dev.to/seiji_ito_2ab3f2c476cf649/how-do-you-connect-a-blockchain-node-with-multiple-trading-bots-without-adding-tcphttp-overhead-54db <p>What happens when a blockchain node needs to communicate with multiple trading bots running as separate processes?</p> <p>Instead of adding another network layer, <strong>go-ipc</strong> uses local IPC.</p> <p>The flow is surprisingly interesting:</p> <p>➡️ Bot registers with the node<br> ➡️ Bot creates its dedicated subscription pipe<br> ➡️ Node connects and starts streaming events<br> ➡️ Node creates a dedicated transaction-submit channel<br> ➡️ Bot sends signed transactions back<br> ➡️ Heartbeats keep the connection healthy<br> ➡️ Stale bots are automatically removed</p> <p>One architecture. Two directions. Multiple independent bots.</p> <p>And because the transport uses OS-level IPC rather than TCP/HTTP, communication stays local to the machine.</p> <p>I mapped the architecture and workflow in the diagram below.</p> <p>🔗 <a href="https://github.com/seiji0411/go-ipc" rel="noopener noreferrer">https://github.com/seiji0411/go-ipc</a></p> github blockchain go ipc