RGM network update — 28 July 2026Short version: RGM launched on 27 July. Early on, a large miner joined, pushed the difficulty up sharply, and then left. With that hashrate gone, the remaining miners couldn't meet the elevated difficulty, and the network stalled at block 363 — a known failure mode for young Scrypt chains ("stuck at peak difficulty").
We've shipped RGM's first update to fix the root cause:
- An emergency difficulty rule: if no block is found for 3 hours, the next block is allowed at minimum difficulty. A large miner leaving can never freeze the chain again.
- A checkpoint at block 363, locking in all history up to the stall.
This was a coordinated update (a hardfork at block 364). Our nodes are updated and the network is producing blocks again.
In plain terms:- Nothing was rolled back. Every coin mined so far (~18,150 RGM) stays with whoever mined it. We didn't and won't reset balances.
- Outside connections were briefly limited during the upgrade so the fix could roll out cleanly. We'll reopen them together with the updated release.
- Updated binaries and a short write-up will be posted on GitHub in the next couple of days. If you run a node, you'll need that update to follow the network past block 364.
We'd rather be upfront about a rough first day than pretend it didn't happen. RGM is a Dogecoin fork that adds a native post-quantum address type — no premine, 60-second blocks, 50 RGM per block.
We want a broad, fair start, and once the update is out we'd love for more people to run nodes and mine with us.
Website: rgmchain.net |
Telegram: t.me/RGM_Core |
GitHub: github.com/rgmchain/rgm
I need a node to sync wallet. Ready to mine to RPC -but need wallet synced
You are absolutely right, and I appreciate you pointing this out. Your miner couldn't sync because the network was temporarily stuck at block 363.
Here is exactly what happened: shortly after launch, a large miner joined, spiked the difficulty to ~450, and then disconnected. Without that hashrate, the remaining miners (especially CPU miners) couldn't find a block at that elevated difficulty, causing the chain to stall. This is a known failure mode for young Scrypt chains.
The good news is that we have already deployed the fix. The network is producing blocks again. We added an emergency rule: if no block is found for 3 hours, the next block is allowed at minimum difficulty. This guarantees that a large miner leaving can never freeze the chain again. We also placed a checkpoint at block 363 to lock in the history.
For your miner to sync and continue mining, you will need the updated client. We are finalizing the build and will post the updated binaries and a short write-up on GitHub in the next couple of days. Until then, older nodes won't be able to follow the network past block 364.
Rest assured, nothing was rolled back. Every coin mined before the stall (~18,150 RGM) stays with whoever mined it. We'll announce the release here and in our Telegram as soon as it's ready. Thank you for your patience and for testing the network!
Wallet not sync(((
You are absolutely right. Your miner couldn't sync because the network was genuinely stuck at block 363 due to an early difficulty spike.
The good news: we improved the node software and restarted our nodes. The network is now fully operational and producing blocks again.
Here is a live screenshot of our working miner:
https://i.postimg.cc/RFmxKQ75/solo-miner.jpgYour wallet will sync perfectly once we publish the updated binaries on GitHub in the next couple of days. Older clients simply cannot follow the chain past block 364.
Rest assured, no balances were rolled back.
