Rincoin-Sim Test Evidences

Build and test evidence for Rincoin-Sim v1.1.0, a 1/1000-scale functional-test build of Rincoin Core. Fifteen files plus a signed digest list, recording the state of the source tree the release was built from. Verified tree: e9be3b12e6ff462e00350e10459dd2e0adb87141Released as: tag v1.1.0 of Aevust/rincoin-sim Start with MANIFEST.md. It lists what each file records, how the suite was run, how the result was judged, and what this bundle does not establish. Contents MANIFEST.md — the bundle's own description and verification instructions build-e9be3b12e-20260804-154252.log — the build; the header records a clean working tree (dirty: 0 file(s)), exit=0, 612 s, g++ 13.3.0 on Ubuntu 24.04 suite-full.log — full functional suite: 112 passed, 55 failed, 42 skipped, runtime 1168 s suite-2026-08-01-130520.log — the pre-release baseline the run above is compared against feature_taproot_wallet_guard.log, feature_rin3_enforcement.log, p2p_rin3_services.log, rpc_fundrawtransaction.log — four individual test runs feature_abortnode.log — ten standalone runs of the one test whose status differs from the baseline sim-ch.log, sim-ch-rin3.log, sim-ch-attack.log, sim-mweb.log — the four simulation scripts shipped in scripts/, run against the same commit. They cover ground the functional suite does not: reorgs up to 5461 blocks that erase the entire Customized Halving history and remine it, and an MWEB peg-in and peg-out with a reorg across the peg-out block signatures.txt — commit signatures for the twelve commits up to and including the verified tree tree-sha256.txt — SHA-256 of the thirteen functional test files as committed SHA256SUMS, SHA256SUMS.asc — digest list over the fifteen other files, and a detached armored signature over it Verifying this bundle gpg --verify SHA256SUMS.asc SHA256SUMS sha256sum -c SHA256SUMS The signature is made with the key that signed the commits: subkey C5BEF8A9FA06C16F of primary fingerprint ED20 B635 4EE4 526D 01F8 3B53 8B6E 3BF4 5C71 4ECA. No distribution channel has to be trusted — the fingerprint above identifies the key, and it is computed over the primary key packet alone, so it is the same whichever channel serves it. Fetch by fingerprint and check what arrived: gpg --keyserver hkps://keys.openpgp.org \ --recv-keys ED20B6354EE4526D01F83B538B6E3BF45C714ECA gpg --fingerprint ED20B6354EE4526D01F83B538B6E3BF45C714ECA The test files can be checked against a clone: git clone https://github.com/Aevust/rincoin-sim.git cd rincoin-sim && git checkout e9be3b12e sha256sum -c /path/to/tree-sha256.txt Scope The scripts themselves are not in this bundle; they are in the tagged source under scripts/, and running them there is how these logs were produced. Two of the four end with their own assertion counts (35 and 28, none failed); the other two print measured values next to the expected ones. They were run by hand rather than under the test runner, so unlike the suite logs there is no runner-side record of what was skipped. Passing jobs are compared as sets rather than counts. One job changed status against the baseline — feature_abortnode.py — and it is recorded as a documented exception rather than absorbed into a total; MANIFEST.md names the mechanism. The baseline log predates the convention of heading each log with its commit, so the exact tree it ran against cannot be identified from this bundle; MANIFEST.md sets out what the two logs do and do not establish between them. License The logs are machine output from a build of Rincoin-Sim, which is MIT licensed. MANIFEST.md is released under CC0.