Rogue Network v3.0.0 — FORGE mainnet upgrade

Required upgrade before block 1,100,100. This release prepares the existing OGG/RGN mainnet for the FORGE activation. Historical rules and rewards remain in effect through block 1,100,099. Activation is determined by block height, not a calendar date.

Source commit: 18367e0aea25899af7fe8d608f0a19fa420740a9

Changes at activation

• Scrypt merged-mining proofs anchored to DigiByte, Dogecoin, or both, with the agreed 12-second target. Actual block intervals vary. RGN blocks do not wait for discovery of a native DGB/DOGE block.
• V4 certificate binding and a 2-of-4 approved signing quorum. Ordinary RGN nodes validate RGN proof-of-work and certificates without DGB/DOGE daemons or signer keys. Native-template checks depend on the approved quorum; this release is not signer-free.
• Profile rgn-mainnet-v3: 1,100 RGN initial normal block subsidy, declining toward the 100 RGN tail, within the 10.7 billion RGN lifetime gross issuance cap. Transaction fees retain their inherited handling.
• Normal subsidy allocation: 40% miners, 30% existing staking, 20% P2E and 10% treasury, with deterministic integer rounding. Future Tribe funding ends; existing balances, contracts and claims are preserved.
• Special treasury credits form part of the stated cap: 300 million RGN at block 1,100,110, then 36 credits of 50 million RGN at 1,100,100 + j × 219,150 for j = 1..36; the first is at block 1,319,250. These are canonical state credits rather than a separate payout service.
• Approved native treasury commitments are enforced through the V4 proof/signing path. When a native block is found and accepted, its full subsidy plus fees from included transactions are directed to the approved native treasury destinations, subject to native-chain maturity and reorganisation rules.
• Corrected proof binding, target-derived chainwork handling and explorer reward RPC support.

Install and run a regular node

Download rgn-v3.0.0-linux-amd64.tar.gz and SHA256SUMS from this release. The archive includes the required shared mainnet configuration, current public peers, startup instructions and licenses. Use the included configuration rather than the repository's historical genesis.json by itself.

sha256sum -c SHA256SUMS
tar -xzf rgn-v3.0.0-linux-amd64.tar.gz
cd rgn-v3.0.0-linux-amd64
sha256sum -c PACKAGE-SHA256SUMS
./egem --datadir "$HOME/.rgn" --networkid 70088 --nousb init ./RGN-mainnet-1100100-genesis.json
./start-node.sh "$HOME/.rgn"

These commands initialize a new node. Existing operators must stop their node cleanly, retain a consistent backup and apply the configuration to their existing datadir before restarting with the new binary. Do not run a second process against the same database. Preserve existing node identities, account keys and customized service/port settings. See NODE-SETUP.txt for the existing-node procedure and the read-only verification command.

Linux x86-64 release; dynamically linked glibc 2.34 or newer is required. Ubuntu 22.04 is the reference build/runtime environment. Windows, macOS, ARM64 and musl/Alpine binaries are not included.

The upstream executable name and version banner remain egem / 1.0.3-syrius. Identify this release by its source commit and SHA-256, not the legacy banner. The banner's compiled network default is not the running network: the supplied startup command explicitly selects 70088.

Mining and validation

Running a regular node does not require a native daemon or signing service. Mining operators need compatible FORGE V4 pool/solo software, an RGN node, DGB and/or DOGE native backends, and access to the approved public signing quorum. An ASIC cannot mine through an ordinary node's HTTP RPC alone. Pool software, private signer deployments and a Docker image are not included in this node archive.

Production activation and post-fork block, reward and transaction checks will follow at block 1,100,100.