Rincoin-Sim v1.1.0.1 and the Rincoin Core v1.1 Branch
The first binary release of the Rincoin-Sim v1.1 line and the Rincoin Core v1.1 development branch are now published on the canonical repository.
Not a Core release and not for mainnet use: Rincoin-Sim is a 1/1000-scale functional-test build of Rincoin Core. v1.1.0.1 is a patch release on v1.1.0 and the first in the v1.1 line with binaries attached. The v1.1.0 binaries were withdrawn before publication after three defects were found (version naming, signet chain selection, bundled README); all three are fixed here. Release assets: a Linux x86_64 tarball, the source tarball, and a SHA256SUMS signed with the same key as the tag (ED20 B635 4EE4 526D 01F8 3B53 8B6E 3BF4 5C71 4ECA).
Verified Before Publishing
On a clean checkout: make check with zero failures, the three Rincoin functional tests, and the Customized Halving boundary script -- then the shipped tarball re-checked, and the assets independently re-downloaded and signature-verified on a second machine. Consensus behaviour is unchanged from v1.1.0, so the v1.1.0 evidence bundle remains the evidence for it. There is no reproducible build; the binaries inherit trust from the signature.
Release: https://t.co/0qSHjs7Gds
Evidence: https://t.co/o0Mk9eOvio
Archive: https://t.co/Wna9CsfkGY
Rincoin Core: The v1.1 Branch on the Canonical Repository
Following the release, the v1.1 development branch of Rincoin Core is now on the canonical repository -- until now it lived only in the staging repository. The Customized Halving can now be read, built, and run from the project's own repository. The move was made in coordination with the Founder.
Commit signing on this repository begins at c1020be63, the commit that added the security policy and public key; everything from there to the head of this branch is signed under ED20 B635 4EE4 526D 01F8 3B53 8B6E 3BF4 5C71 4ECA, the earlier commits with the primary key and the later ones with its signing subkey. Older commits predate the policy and are unsigned.
The branch was copied from staging by commit hash, so the objects and their signatures are byte-identical in both, carrying the Customized Halving parameters and fork height (RIP-0002 / RIP-0009), the RIN3 nVersion enforcement -- the hard fork's transaction replay protection -- at both the mempool and block-validation layers, and MWEB and Taproot held at NEVER_ACTIVE on mainnet (RIP-0004 / RIP-0011). Core commits that carry code verified in Sim name the Sim commit they were ported from; Core-only changes have no such counterpart.
Development continues in the staging repository; finished work reaches the canonical one through a pull request and review, as this branch did. It is a development branch, not a release: no tag, no binaries, master unchanged.
Branch: https://t.co/h44SOzQbIO
Staging: https://t.co/olghAFb16g
#Rincoin $RIN #RIN #Development
Rincoin-Sim: Supply Accounting for the 168,000,000 RIN Cap
The 168,000,000 RIN supply cap is now accounted for in code. No consensus change -- GetBlockSubsidy() is untouched, and emission is identical at every height.
What the Tests Pin
GetTotalSubsidy() expresses the whitepaper's schedule integral (v1.6.4, Scenario II) in closed form over the Customized Halving phase boundaries, pinned by unit tests against a brute-force sum -- full sweep, zero mismatches. The cap is derived, not duplicated: 800 RIN per halving interval, asserted on mainnet against MAX_MONEY at startup; off by one satoshi, the daemon aborts with exit 134. The integral reaches the cap exactly at height 234,587,500 -- 446.3232 years at 60-second blocks, matching the paper's t_trans -- with S_fix pinned at 31,027,500 RIN.
Enforcement inside GetBlockSubsidy() is a separate future change and will be proposed as a new RIP before any implementation. Five signed commits, merged to master through a pull request; all five are written to be ported to Rincoin Core.
PR: https://t.co/6G5fWv5Hma
#Rincoin $RIN #RIN #Development
Rincoin-Sim v1.1.0.1 and the Rincoin Core v1.1 Branch
The first binary release of the Rincoin-Sim v1.1 line and the Rincoin Core v1.1 development branch are now published on the canonical repository.
Not a Core release and not for mainnet use: Rincoin-Sim is a 1/1000-scale functional-test build of Rincoin Core. v1.1.0.1 is a patch release on v1.1.0 and the first in the v1.1 line with binaries attached. The v1.1.0 binaries were withdrawn before publication after three defects were found (version naming, signet chain selection, bundled README); all three are fixed here. Release assets: a Linux x86_64 tarball, the source tarball, and a SHA256SUMS signed with the same key as the tag (ED20 B635 4EE4 526D 01F8 3B53 8B6E 3BF4 5C71 4ECA).
Verified Before Publishing
On a clean checkout: make check with zero failures, the three Rincoin functional tests, and the Customized Halving boundary script -- then the shipped tarball re-checked, and the assets independently re-downloaded and signature-verified on a second machine. Consensus behaviour is unchanged from v1.1.0, so the v1.1.0 evidence bundle remains the evidence for it. There is no reproducible build; the binaries inherit trust from the signature.
Release: https://t.co/0qSHjs7Gds
Evidence: https://t.co/o0Mk9eOvio
Archive: https://t.co/Wna9CsfkGY
Rincoin Core: The v1.1 Branch on the Canonical Repository
Following the release, the v1.1 development branch of Rincoin Core is now on the canonical repository -- until now it lived only in the staging repository. The Customized Halving can now be read, built, and run from the project's own repository. The move was made in coordination with the Founder.
Commit signing on this repository begins at c1020be63, the commit that added the security policy and public key; everything from there to the head of this branch is signed under ED20 B635 4EE4 526D 01F8 3B53 8B6E 3BF4 5C71 4ECA, the earlier commits with the primary key and the later ones with its signing subkey. Older commits predate the policy and are unsigned.
The branch was copied from staging by commit hash, so the objects and their signatures are byte-identical in both, carrying the Customized Halving parameters and fork height (RIP-0002 / RIP-0009), the RIN3 nVersion enforcement -- the hard fork's transaction replay protection -- at both the mempool and block-validation layers, and MWEB and Taproot held at NEVER_ACTIVE on mainnet (RIP-0004 / RIP-0011). Core commits that carry code verified in Sim name the Sim commit they were ported from; Core-only changes have no such counterpart.
Development continues in the staging repository; finished work reaches the canonical one through a pull request and review, as this branch did. It is a development branch, not a release: no tag, no binaries, master unchanged.
Branch: https://t.co/h44SOzQbIO
Staging: https://t.co/olghAFb16g
#Rincoin $RIN #RIN #Development