Rincoin Core v1.1.0 (stops at 840k)

Warning

This release deliberately stops at block height 840,000 as a new consensus is expected from this height on.
Install it, and plan to replace it.

Rincoin reaches block 840,000 in roughly three months (November 2026). At that height the network needs a decided set of consensus rules, and the community has not selected them yet — the review is open at consensus-840k.

Rather than guess at rules that have not been agreed, and rather than let unattended nodes drift onto whichever continuation happens to reach them first, this release refuses to go past the question. It validates normally up to block 839,999 and then stops.

See the chapter The 840k boundary below for more info about the height 840,000 termination.

This release is a drop-in replacement for currently running versions

This release changes no consensus rule, no protocol version, and no block, transaction or storage format. Below height 840,000 it validates exactly as the old releases from Rin-coin/rincoin you are running today (v0.21.4, v1.0.1, v1.0.4, or v1.0.5).

• Upgrading: stop the old node, replace the binaries, start it again. No datadir migration, no reindex, no reconfiguration.
• Downgrading back to 1.0.x works the same way, though you lose the warning and the safe stop.
• Your wallet is untouched. No wallet format change, no rescan.
• The block at the boundary is stored but never connected — it is not marked invalid, and the peer that sent it is not banned. The chain a stopped node leaves behind is a valid chain that the successor release picks up and continues, with no reindex.

The only externally visible change is identity: the node now reports itself as /RincoinCommunityCore:1.1.0/ and continues to speak protocol 70017.

Which file to download

You are running	Download
Ubuntu 22.04 / Debian 12, or anything older, x86_64	rincoin-1.1.0-x86_64-linux-gnu.tar.gz
Ubuntu 24.04 / Debian 13 or newer, x86_64	rincoin-1.1.0-x86_64-linux-gnu-ubuntu24.tar.gz
Raspberry Pi / ARM server, older distro	rincoin-1.1.0-aarch64-linux-gnu.tar.gz
Raspberry Pi / ARM server, Ubuntu 24.04+ / Debian 13+	rincoin-1.1.0-aarch64-linux-gnu-ubuntu24.tar.gz
Windows 10/11, 64-bit	rincoin-1.1.0-win64.zip
macOS, Apple Silicon — GUI wallet	Rincoin-Qt-1.1.0-arm64-apple-darwin.dmg
macOS, Apple Silicon — command-line tools	rincoin-1.1.0-arm64-apple-darwin.tar.gz

There is no Intel macOS build in this release: GitHub retired the x86_64 macOS runners. On an Intel Mac, build from source — see doc/build-osx.md.

If you are unsure which Linux build to take, take the plain one (without -ubuntu24). It is built against an older glibc and therefore runs on both old and new distributions; the -ubuntu24 builds require glibc 2.39 or newer and will not start on older systems.

Every archive contains rincoind, rincoin-cli, rincoin-tx, rincoin-wallet and rincoin-qt.

Verifying your download

SHA256SUMS.txt in the assets covers every archive, and SHA256SUMS.txt.asc is a detached GPG signature over it. Download both alongside the archive you took, then:

gpg --recv-keys FEE1ACA52C65FF3EBF31818CB5595E1752BC2A82
gpg --verify SHA256SUMS.txt.asc SHA256SUMS.txt
sha256sum -c SHA256SUMS.txt --ignore-missing

The signature is made by the signing subkey ABB2 DF8B 79E8 A4E7 6139 4732 B3FF 4116 5803 42CB of the key published in SECURITY.md; the v1.1.0 tag is signed with the same key. Verify the fingerprint before trusting the download.

Each archive also carries its own SHA256SUMS.txt covering the binaries inside it.

What else is in this release

• Mainnet checkpoints extended through height 693,782. All 211 entries in the map were verified against a node synced from production chain data before being committed.
• The peer-protocol-version floor is flat at 70017 on every network. The step to 70018 is scheduled before height 840,000.
• Qt test vectors corrected, so the GUI test suite passes.
• Release builds now run every target in parallel: about 30 minutes instead of just over two hours.
• Several performance-based log outputs moved to the bench log category, so they no longer bloat debug.log.

The full history is in doc/release-notes-rincoin.md.

The 840k boundary

What happens at the boundary

When a block at 840,000 arrives, the node does not connect it. It logs the reason, raises a fatal error and shuts down, leaving the chain on the last block below the boundary. Restarting a node that has already reached 839,999 is refused.

From height 796,800 — about 30 days earlier — every node carries a persistent warning that counts down the remaining blocks and names the estimated date. It appears in getblockchaininfo, getnetworkinfo and getmininginfo, on every block in debug.log, and in the GUI as a status-bar strip visible on every tab. A louder repeat, including a non-blocking desktop notification in the GUI, goes out on a cadence that tightens from roughly every 17 hours to every half hour as the height approaches. Nothing about it blocks the wallet or requires a click.

From the moment the next block would be 840,000, getblocktemplate, the generate* RPCs, submitblock and submitheader refuse, so a node running this release can never mine the boundary block itself.

One operational consequence, stated plainly

A stopped node stops serving blocks to its peers. If a large share of the network is running this release when the chain reaches 840,000, capacity is withdrawn at exactly that moment. That is the deliberate trade — a node that stops is safer than a node that silently picks a side — but it is a reason to plan your upgrade rather than rely on the stop.

What happens next

legacy-1.1 is the end of the 1.0/1.1 line. Development continues on the dev branch, and the release that implements the selected height-840,000 rules will come from there. Watch consensus-840k for the decision, and this repository for the release that follows it. Join the Rincoin Community Forge discord to discuss the future consensus change.

Before block 840,000, install a release that implements the selected rules. A node left on this one will stop and stay stopped.