[ANN] RGMChain (RGM) — Dogecoin fork w/ native post-quantum (ML-DSA-44) addresse

[RGM-Core]

Small honest update — and a genuine ask for feedback.

First, paulmbcufc: I hear you, and that one's fair. The pool's vardiff cap was set far too low and it cost you a real early window. No excuses — that was my bug, and I'm sorry you lost the morning to it.

I want to be straight about what RGM actually is: a one-person project. No team, no funding, no marketing budget — it's just me maintaining the node software, the pool, the explorer and the wallet. That means I move slower than I'd like and I've shipped mistakes (the vardiff cap being the worst so far). I'd genuinely rather hear hard technical criticism now than pretend everything is polished.

Where things stand today:
- Network is live and steady, past the early difficulty stall. Emission is fully verifiable on-chain (genesis → block 1, no gap, no premine): https://mainnet.rgmchain.net
- Difficulty: LWMA window 45 + DigiShield on 60s blocks.
- Pool vardiff bug is fixed (cap raised), so large scrypt ASICs report correctly now.
- More independent nodes are online, so the network no longer depends on a single machine.

So here's my ask to the people here who've actually run chains, pools, or serious scrypt hardware: if you were doing this solo, what would you prioritise, fix, or drop?
- Is the LWMA(45)+DigiShield choice sane for a small scrypt chain, or would you tune it differently?
- Pool side — anything you'd change in how a young chain should handle big ASICs joining/leaving?
- The post-quantum angle (ML-DSA-44, opt-in at block 50k) — useful, or a distraction from just being a solid scrypt coin?

I'm not looking for hype or price talk here — there's no exchange yet, and today I care more about getting the tech right than about listings. I'm looking for the technical blind spots I'm too close to the project to see. Push back freely; I'd rather fix it than defend it.

Website: https://rgmchain.net | GitHub: https://github.com/rgmchain/rgm
X: https://x.com/RGM_Core | Telegram: https://t.me/RGM_Core | Discord: https://discord.gg/dFUDKZVMF

[RGM-Core]

Quick follow-up: the difficulty-recovery fix I mentioned is now live.

I've tagged and shipped v2.0.2 and rolled it out across all nodes. What's in it:

- Emergency difficulty recovery: if the network stalls for 3 hours (e.g. a big ASIC leaves right after spiking difficulty), the chain can now self-recover a min-difficulty block via getblocktemplate instead of sitting frozen. This is the fix for the freeze behaviour I described earlier — it's a miner/template-side change, not a consensus rule change, so it's compatible with existing nodes.
- One more independent seed node, on separate hosting in a different location, baked into the client so new wallets/nodes bootstrap more reliably. Fewer single points of failure for the network coming up.
- Version bump 2.0.1 -> 2.0.2.

It's a maintenance release, not a hardfork — updating is recommended but not urgent, and un-updated nodes stay compatible.

Release + checksums: https://github.com/rgmchain/rgm/releases/tag/v2.0.2
Verify with: sha256sum -c SHA256SUMS.txt

Still very much interested in the difficulty-tuning feedback from earlier — this fix addresses the freeze failure mode, but the LWMA(45) response to big hashrate swings is the part I'd still like harder eyes on.

[RGM-Core]

We have crossed the line. Block 50,000 is behind us.

Hello everyone. As the sole developer behind RGM, I am writing to share that our network has officially passed the 50,000 block milestone.

For those who have been following the project since our fair, zero-premine launch, this block height marks a fundamental shift: native Post-Quantum (PQ) addresses are now fully active on the mainnet. We have implemented ML-DSA-44 (the Module-Lattice-Based Digital Signature Algorithm standardized by NIST as FIPS 204, formerly CRYSTALS-Dilithium) using the liboqs 0.15.0 library.

My goal was never to just create another fork. I wanted to take the proven, fair Scrypt consensus and seamlessly integrate a layer of cryptographic security designed to withstand future quantum threats, without disrupting the mining layer.

Don't trust, verify. I invite you to test it.
I don't expect anyone to simply take my word for it. The code is 100% open, and I strongly encourage independent developers, cryptographers, and miners to test this functionality themselves.

🎁 Free coins for testing
I understand that not everyone currently holds RGM, and mining them just to run a quick test takes time. To remove this barrier, I have set aside a personal reserve of coins specifically for community testing.

If you want to try generating a PQ address and sending a transaction, but don't have any coins:
👉 Simply reply to this thread with your classic RGM address (starting with 'R...'), or send me a Direct Message (DM) here on Bitcointalk, or on Twitter/X, Reddit, or Discord.
I will gladly send you a small amount—more than enough to cover several test transactions and network fees. No strings attached. My only goal is to ensure as many people as possible can personally evaluate this technology.

🔬 How to test it yourself (Step-by-step):

1. Get the latest release:
Download the latest version from the repository: https://github.com/rgmchain/rgm/releases/latest

2. Generate a Post-Quantum Address:
Run the daemon and use the console (`rgm-cli` or the debug console in the GUI wallet). Run:

Code:

getnewaddress "test_pq_wallet" "pq"

This will output a new bech32 address starting with rgm1z...

3. Send a small test transaction:
From the classic address (starting with 'R...') where you received the test coins, send a small amount (e.g., 0.1 RGM) to your new PQ address:

Code:

sendtoaddress "rgm1z[your_new_address]" 0.1

4. Verify on the Block Explorer:
Take the resulting TXID and look it up here: https://mainnet.rgmchain.net
In the transaction details, you will see that the transaction was successfully processed using the post-quantum witness v2 scheme.

The source code is open. I am more than happy to answer any technical questions in the comments or via DM. Thank you to everyone who has supported this project.

🔗 GitHub: https://github.com/rgmchain/rgm
🌐 Explorer: https://mainnet.rgmchain.net

[RGM-Core]

You can also use a wallet (RGM PyWallet) - create a new one or open a previously created one and in the field (SegWit), (PQ) click on +