The EVOTE code-base on GitHub (https://github.com/netpipe/EVOTE/tree/main/new) is already about 90 % finished. What remains is the peer-to-peer side: reliable node discovery, fast data synchronisation, and bullet-proof transaction validation. Everything else—wallet logic, ledger rules, CLI, and basic networking stubs—is in place and compiling; I simply haven’t had time to wire the last mile. I designed a lightweight custom protocol for EVOTE but, to be honest, it lives only in my head and in a handful of comments. Your first step will be to study the existing code and extract whatever hints are there. From that point we can iterate together: you propose the handshake, message formats and state machines; I’ll confirm they stay true to EVOTE’s consensus model. Because node discovery, sync and validation touch every layer, clean commit history and thorough inline documentation are paramount. Please aim for clear, self-contained PRs so I can review each piece quickly. Deliverables • Node discovery maintains healthy peer tables and drops stale connections • Block / mempool synchronisation • Transaction validation hooks integrated into the existing consensus code, rejecting malformed or double-spend attempts before propagation • Integration tests that spin up multiple local nodes and prove the above three functions work together If you’re comfortable crafting custom P2P layers—perhaps you’ve tinkered with The language, build system and external libraries are already set up in the repo, so you’ll be extending rather than reinventing.