Skip to content

Releases: rgmchain/rgm

RGM Core v2.0.1

Choose a tag to compare

@rgmcore rgmcore released this 10 Aug 14:36

Maintenance and hardening release. Not a hard fork — v2.0.0 and v2.0.1 nodes are protocol-compatible.

Changes

  • PQ key hardening — the ML-DSA-44 private key is now held in secure_allocator (mlock'd, non-swappable memory) and wiped with memory_cleanse on clear (replacing an optimizer-removable std::fill).
  • First independent seed node217.25.238.104 added to fixed seeds (activates when networking opens at block 25,000).
  • Test suite — consensus tests for the golden-block subsidy / total supply, the emergency difficulty rule (block 364), and an ML-DSA-44 sign/verify round-trip.
  • PQ sighash justification — documented the empty scriptCode + fixed SIGHASH_ALL in the post-quantum path (key bound via HASH160(program)).

Network status

Mining pools and open node/RPC networking activate at block 25,000; until then the early phase runs on the solo miner for a fair start. Post-quantum (rgm1z…) addresses activate at block 50,000.

Verify

Check the archives against SHA256SUMS.txt:
sha256sum -c SHA256SUMS.txt


(RU) Релиз усиления безопасности, не хардфорк (узлы v2.0.0/v2.0.1 совместимы). Усиление PQ-ключа (secure_allocator + memory_cleanse), первый независимый seed 217.25.238.104 (активен с блока 25 000), тесты (эмиссия/supply, аварийное правило @364, ML-DSA-44 подпись/проверка), обоснование PQ-sighash. Пулы и открытая сеть — с блока 25 000, PQ-адреса — с 50 000.

RGM Core v2.0.0

Choose a tag to compare

@rgmcore rgmcore released this 29 Jul 19:36

RGM Core v2.0.0 — Emergency difficulty fix + checkpoint

First post-launch update. After launch, a large miner spiked the difficulty and then left, and the network stalled at block 363 ("stuck at peak difficulty"). This release fixes the root cause.

What changed

  • Emergency difficulty rule: if no block is found for 3 hours, the next block is allowed at minimum difficulty, so a departing large miner can no longer freeze the chain. Activates at block 364.
  • Checkpoint at block 363, plus nMinimumChainWork and defaultAssumeValid.

This is a coordinated hardfork at block 364. Nothing was rolled back — every coin mined so far stays with its miner.

Network access right now (please read)

During this early phase, external peer connections (P2P) are intentionally limited: the network currently runs on the core nodes, and outside nodes will be opened up at block 25000. Until then:

  • Mining is available now via solo mining through the public endpoint.
  • The light wallet (RGMWallet) works now.
  • A full node or rgm-qt you run yourself will not sync to the network until external P2P is opened at block 25000. Updating now is fine and recommended, but external nodes connect from block 25000 on.

Who this update is for

  • Full node operators and rgm-qt users: update to this version so you are ready when external nodes are opened at block 25000. Required to follow the network past block 364.
  • Ordinary miners (RGMMiner.exe): no update needed — the solo miner does not embed consensus rules.

Downloads

  • rgm-2.0.0-linux-x64.tar.gz — Linux x64 (rgmd, rgm-cli, rgm-tx, rgm-qt)
  • rgm-2.0.0-win64.zip — Windows x64 (.exe)

SHA256

  • rgm-2.0.0-linux-x64.tar.gz: d56a5761eda6eac0ef91263c4a101695d887569e6f9db051e1376fafc5c96ea5
  • rgm-2.0.0-win64.zip: 9977ab86c5083af903705a8b4a249abbb20bdc8cc300c6f1bd864b91a6e157d4

RGM Core v1.0.0

Choose a tag to compare

@rgmcore rgmcore released this 19 Jul 19:12

First release of RGM Core — post-quantum cryptocurrency node (ML-DSA-44 / NIST FIPS 204).
Mainnet activation schedule: pool mining from block 25,000 · SegWit + PQ addresses from block 50,000 · AuxPoW merge-mining from block 500,000.
SHA-256:

22bf6ef69d398a716f8c0ef415abac0cdb2116c052498794d47b79e3b7df7d0f  rgm-1.0.0-linux-x64.tar.gz
ea8f1480a8fe837c0edebe122f4552722a585781cc40d4943c526f6305d516b0  rgm-1.0.0-win64.zip