Hey everyone,
I’ve been developing a fully original blockchain from scratch — Miqrochain — a SHA-256 Proof-of-Work network with 8-minute blocks, 26.28 M total supply, 50 MIQ initial reward, and no premine / no ICO.
Everything (consensus, networking, wallet, RPC, miner) is written from zero in C++ — not a fork of Bitcoin Core or any other chain.
At the moment, the main node runs perfectly and mines valid blocks, but newly joined nodes fail to fully synchronize with it.
They connect, handshake, and sometimes exchange headers, but they don’t download or accept blocks correctly from the initial node.
All consensus validation, PoW, and serialization routines are solid — the problem seems to be in P2P or block transfer logic (likely headers-first, inv/getdata, or block acceptance flow).
I’m looking for another experienced blockchain or C++ network dev to help review the sync logic and identify why new peers don’t sync to the main node’s chain.
The project is well-structured and actively maintained (builds cleanly on Windows & Linux via CMake/MSVC/GCC).
Tech context:
SHA-256 PoW, epoch retarget difficulty adjustment
8-minute blocks
Interactive miner with Base58 address prompt
Fully custom block, tx, and serialization system
RPC interface (HTTP JSON, cookie-auth)
P2P protocol based on version/verack/inv/getdata/headers
Currently debugging: multi-node synchronization
I can provide the current source (C++17), a working binary, and logs from both the initial node and secondary node attempts.
All I need is another sharp pair of eyes to find where the sync stalls or fails.
If you’ve ever debugged Bitcoin Core, Litecoin, or custom PoW chain networking, your input will be extremely valuable.
Happy to credit you publicly or even collaborate long-term if you’re interested in shaping a fair-launch project from the ground up.
Github Repo:
https://github.com/takumichronen/miqrochainThanks in advance to anyone who can help diagnose this — I’ve put a lot into this codebase and would love to get the multi-node sync working cleanly so we can move forward to GUI and for others to join successfully.
— Takumi Chronen
Lead Dev, Miqrochain
> History repeats in 8-minute blocks.
