-
Notifications
You must be signed in to change notification settings - Fork 3
Comparing changes
Open a pull request
base repository: Rin-coin/rincoin
base: master
head repository: takologi/rincoin
compare: driftwood/cleanup-ci
Commits on Feb 5, 2026
-
- Created standalone test-dns-seeds tool to verify DNS seeder functionality - Uses same DNS resolution code as Rincoin Core (LookupHost) - Reads seed hostnames from chainparams configuration - Supports service bit filtering (x<servicebits>.<hostname>) - Provides detailed output and statistics - Includes build script and comprehensive documentation - Useful for testing and monitoring DNS seeders
Configuration menu - View commit details
-
Copy full SHA for 2d8aac6 - Browse repository at this point
Copy the full SHA 2d8aac6View commit details -
Integrate test-dns-seeds utility into build system
- Changed all command-line arguments to use double dash (--) format - Added test-dns-seeds to src/Makefile.am as noinst_PROGRAMS - Linked against proper Bitcoin Core libraries (SERVER, COMMON, CONSENSUS, UTIL, CRYPTO, SECP256K1, MW, etc.) - Added required G_TRANSLATION_FUN global definition with extern const - Updated standalone Makefile.test-dns-seeds with additional dependencies - Tool successfully builds via both autotools and standalone Makefile - Tested with seed.rincoin.net: successfully queries and returns peer addresses The utility mimics Core's DNS resolution logic using LookupHost() and can: - Query mainnet, testnet, or regtest DNS seeds - Test specific seeds or all configured seeds - Filter by service bits - Control timeout and max IPs returned - Provide verbose output with statistics
Configuration menu - View commit details
-
Copy full SHA for 9660d08 - Browse repository at this point
Copy the full SHA 9660d08View commit details
Commits on May 9, 2026
-
release: add ARM64 Linux targets, platform switches, checksum-in-arch…
…ive, CI workflow - build_release.sh: refactor with build_linux_binaries() helper; add Linux aarch64 (Ubuntu 20/24) targets using aarch64-linux-gnu toolchain; add --no-linux-x86, --no-aarch64, --no-windows platform switches; embed SHA256SUMS.txt inside each binary archive before packing; rename Docker images to rincoin-builder:linux-{arch}-{ubuntu_label} - .github/workflows/release-build.yml: new CI workflow triggered on v* tag push and workflow_dispatch; uploads artifacts and creates GitHub release - doc/build-rincoin-release.md: document ARM64 targets, platform switches, two-level checksum model, updated output layout and timingsConfiguration menu - View commit details
-
Copy full SHA for bb30d14 - Browse repository at this point
Copy the full SHA bb30d14View commit details -
ci: fix workflow triggers — add branch push trigger for aarch64-suppo…
…rt, handle --local build mode
Configuration menu - View commit details
-
Copy full SHA for 198503f - Browse repository at this point
Copy the full SHA 198503fView commit details
Commits on May 17, 2026
-
release: prepare v1.1.0 community maintenance release
Add a preview network combining testnet-like parameters with an accelerated activation schedule and regtest halving interval for rehearsing future protocol transitions. Introduce the RinHash activations table with JSON source data, code generation, and generated consensus-header verification. Add a scheduled min_peer_protocol_version floor for activation 0 (mainnet 840000, testnet 4200, regtest 600, preview 600), bump PROTOCOL_VERSION from 70017 to 70018, expose effective RinHash parameters through RPC, add the preview chain for activation rehearsal, exempt MWEB HogEx transactions from the empty-vin consensus check, and document the release. This release does not change the consensus rules currently in force on mainnet. It introduces infrastructure for future community-reviewed protocol transitions. The peer-protocol floor affects network reachability at and after the per-network activation height, not historical block validity.
Configuration menu - View commit details
-
Copy full SHA for 0f2d7d8 - Browse repository at this point
Copy the full SHA 0f2d7d8View commit details -
ci: fix Docker install conflict on ubuntu-24.04 runners
GitHub Actions ubuntu-24.04 runners already have Docker Engine installed via containerd.io. Installing docker.io on top of it fails with a package conflict. Drop docker.io from the apt install list and rename the step to 'Verify Docker' to make the intent clear.
Configuration menu - View commit details
-
Copy full SHA for 3cc9add - Browse repository at this point
Copy the full SHA 3cc9addView commit details -
ci: add macOS build jobs for x86_64 and arm64 (Approach A)
Add a build-macos job to the release workflow that builds native macOS binaries on GitHub Actions hosted runners: - macos-13 (Intel x86_64) → rincoin-{VERSION}-x86_64-apple-darwin.tar.gz - macos-14 (Apple Silicon arm64) → rincoin-{VERSION}-arm64-apple-darwin.tar.gz Each matrix leg: - Installs Homebrew deps (boost, libevent, qt@5, qrencode, fmt, etc.) - Installs Berkeley DB 4.8 from source via contrib/install_db4.sh (which already handles macOS via its clang patch and shasum fallback) - Configures with --with-gui=qt5 to include rincoin-qt - Runs make deploy to produce a Rincoin-Qt-{VERSION}-{arch}.dmg - Packages all binaries + SHA256SUMS.txt into a .tar.gz Artifacts are uploaded per-arch and, on tag pushes, published directly to the GitHub Release alongside the existing Linux/Windows assets. Also adds apple-support to the branch trigger list so CI runs on pushes to this branch during development.Configuration menu - View commit details
-
Copy full SHA for fe10fb9 - Browse repository at this point
Copy the full SHA fe10fb9View commit details -
ci(macos): fix BerkeleyDB 4.8 mutex detection on Apple Silicon
BDB 4.8 predates arm64/Apple Silicon. Its configure script cannot auto-detect a mutex implementation on that platform, resulting in: configure: error: Unable to find a mutex implementation Pass --with-mutex=POSIX/pthreads as an extra flag to install_db4.sh (which forwards it via "$@" to BDB's own configure). POSIX pthreads are available on both x86_64 and arm64 macOS, so this is safe for both matrix legs.
Configuration menu - View commit details
-
Copy full SHA for fe3760b - Browse repository at this point
Copy the full SHA fe3760bView commit details
Commits on May 24, 2026
-
Configuration menu - View commit details
-
Copy full SHA for 5986793 - Browse repository at this point
Copy the full SHA 5986793View commit details -
Configuration menu - View commit details
-
Copy full SHA for 50272de - Browse repository at this point
Copy the full SHA 50272deView commit details -
Configuration menu - View commit details
-
Copy full SHA for 9f786e4 - Browse repository at this point
Copy the full SHA 9f786e4View commit details -
Configuration menu - View commit details
-
Copy full SHA for 04b883a - Browse repository at this point
Copy the full SHA 04b883aView commit details -
Configuration menu - View commit details
-
Copy full SHA for 8c85b3e - Browse repository at this point
Copy the full SHA 8c85b3eView commit details -
ci(macos): fix Boost library detection with Homebrew
Homebrew ships Boost with the -mt (multithreaded) suffix in library names (libboost_system-mt.a etc.). The AX_BOOST_* autoconf macros look for the non-suffixed name and fail with: checking whether the Boost::System library is available... yes configure: error: Could not find a version of the Boost::System library! The AX_BOOST_* macros check BOOST_INCLUDEDIR and BOOST_LIBRARYDIR environment variables directly. Exporting those to the Homebrew boost prefix lets the macros resolve the correct library path on both x86_64 (macos-13) and arm64 (macos-14) runners.
Configuration menu - View commit details
-
Copy full SHA for fe23212 - Browse repository at this point
Copy the full SHA fe23212View commit details -
ci(macos): fix Boost detection on Homebrew ARM64 (ax_boost_base.m4 pa…
…th gap) The BOOST_LIBRARYDIR env var set in the previous attempt has no effect: this version of ax_boost_base.m4 only checks BOOST_LIBRARYDIR when the --with-boost configure option is also given; otherwise it scans a hard-coded list of prefixes (/usr /usr/local /opt /opt/local) that does not include /opt/homebrew — the Homebrew prefix on Apple Silicon. Fix: resolve the Homebrew boost prefix at build time and pass it directly as configure arguments: --with-boost=$(brew --prefix boost) --with-boost-libdir=$(brew --prefix boost)/lib The configure-argument path (--with-boost-libdir) always wins because ax_boost_base.m4 writes it to BOOST_LDFLAGS last, after all other detection attempts, so it is immune to whatever the auto-detection logic decides.
Configuration menu - View commit details
-
Copy full SHA for 6ab79a2 - Browse repository at this point
Copy the full SHA 6ab79a2View commit details -
build: handle header-only Boost::System and Boost::Filesystem in m4 m…
…acros boost::system became header-only in Boost 1.69; boost::filesystem followed in Boost 1.74. Modern Homebrew (and other distros) no longer ship standalone library files for these components. The ax_boost_{system,filesystem}.m4 macros (serial 20) detect the library by glob-listing the lib directory. When no libboost_system* / libboost_filesystem* files exist the loop body never runs, ax_lib stays empty, and the macro unconditionally aborts with: configure: error: Could not find a version of the Boost::System library! Fix: when ax_lib is empty after both search loops, treat the library as header-only (set the LIB variable to the empty string and mark the check as succeeded). The 'could not link' guard below still fires if files were found but the linker rejected them.Configuration menu - View commit details
-
Copy full SHA for 012a31d - Browse repository at this point
Copy the full SHA 012a31dView commit details -
build: guard posix_fadvise block with __linux__ not _WIN32
posix_fadvise() is Linux-specific; macOS does not provide it. The original #ifndef _WIN32 guard still compiled it on macOS. Change the guard to #ifdef __linux__ so the fadvise optimisation only activates on Linux targets where it is supported.
Configuration menu - View commit details
-
Copy full SHA for c00fd0e - Browse repository at this point
Copy the full SHA c00fd0eView commit details -
build: handle 7-arg UPNP_GetValidIGD added in miniupnpc API v18
miniupnpc 2.2.5 (MINIUPNPC_API_VERSION 18) added two extra parameters to UPNP_GetValidIGD(): char * wanaddr, int wanaddrlen Calling the old 5-argument form against this header produces: net.cpp: error: no matching function for call to UPNP_GetValidIGD Add a compile-time guard (same approach used by Bitcoin Core) that passes the extra wanaddr buffer when building against API >= 18 and falls back to the legacy 5-argument call for older libraries.
Configuration menu - View commit details
-
Copy full SHA for b64acf9 - Browse repository at this point
Copy the full SHA b64acf9View commit details -
build: fix deprecated boost::filesystem::copy_option on Boost >= 1.74
Boost 1.74 renamed the copy_file option enum: copy_option::overwrite_if_exists -> copy_options::overwrite_existing The old name was removed entirely in later versions, causing: bdb.cpp: error: no member named "copy_option" in namespace "boost::filesystem"Configuration menu - View commit details
-
Copy full SHA for 74ffe5a - Browse repository at this point
Copy the full SHA 74ffe5aView commit details -
build: version-guard boost::filesystem copy_option rename for Boost <…
… 1.74 Ubuntu 20.04 ships Boost 1.71 which only has: copy_option::overwrite_if_exists Boost 1.74 introduced the replacement: copy_options::overwrite_existing and later releases (Homebrew 1.87+) removed the old name entirely. Use BOOST_VERSION >= 107400 to select the correct form at compile time so the same source builds on both old Docker images (Ubuntu 20.04/Boost 1.71) and modern Homebrew (Boost 1.87+).
Configuration menu - View commit details
-
Copy full SHA for 8248888 - Browse repository at this point
Copy the full SHA 8248888View commit details
Commits on May 25, 2026
-
build: fix removed Boost.Filesystem API; drop unavailable macos-13 ru…
…nner walletutil.cpp: replace deprecated recursive_directory_iterator methods removed in Boost 1.74+: level() -> depth() no_push() -> disable_recursion_pending() Both new names exist since Boost 1.57 (pre-dating the project minimum of 1.58), so no BOOST_VERSION guard is needed — it is the OLD names that were removed, not the new ones. workflow: comment out the macos-13 (x86_64) matrix entry. GitHub no longer provides macos-13 runners; the job queue waits indefinitely. The entry is left in comments so it can be restored if Intel runner support returns.
Configuration menu - View commit details
-
Copy full SHA for 81f5f08 - Browse repository at this point
Copy the full SHA 81f5f08View commit details -
ci: fix macOS archive nesting; add tmate SSH debug on failure
BSD ar (macOS) cannot merge .a archives — it embeds them as file members rather than extracting object files. The automake LIBADD rule for libbitcoin_crypto_base.a folds libargon2.a into it, which triggers: ld: archive member 'libargon2.a' not a mach-o file in '.../src/crypto/libbitcoin_crypto_base.a' Fix: in the Build step, create an ar wrapper script that delegates to Apple's /usr/bin/libtool -static whenever any input is a .a file. libtool -static extracts and re-archives object files correctly. Also add a tmate SSH-into-runner step (on failure) for interactive debugging of future CI issues.
Configuration menu - View commit details
-
Copy full SHA for 4aea194 - Browse repository at this point
Copy the full SHA 4aea194View commit details -
Configuration menu - View commit details
-
Copy full SHA for 9fc4d8e - Browse repository at this point
Copy the full SHA 9fc4d8eView commit details -
Configuration menu - View commit details
-
Copy full SHA for 658c4e7 - Browse repository at this point
Copy the full SHA 658c4e7View commit details -
macdeploy: fix Litecoin-Qt → Rincoin-Qt throughout deploy scripts
macdeployqtplus, custom_dsstore.py, fancy.plist and detached-sig-create.sh still referenced 'Litecoin-Qt' from the upstream Litecoin fork. This caused 'make deploy' to: • look for dist/Litecoin-Qt.app (wrong copy destination) • look for Contents/MacOS/Litecoin-Qt inside the bundle • position the wrong app icon in the DMG window Replace all four occurrences with 'Rincoin-Qt' to match the actual app bundle name (Rincoin-Qt.app) and binary (Rincoin-Qt.app/Contents/MacOS/Rincoin-Qt).
Configuration menu - View commit details
-
Copy full SHA for a9762d0 - Browse repository at this point
Copy the full SHA a9762d0View commit details -
ci: upgrade GitHub Actions to Node.js 24 compatible versions
actions/checkout@v4 and actions/upload-artifact@v4 use node20, which is deprecated and will be forcibly removed from GitHub Actions runners on September 16, 2026 (forced to node24 from June 2, 2026). actions/checkout@v4 -> @v6 (node24) actions/upload-artifact@v4 -> @v7 (node24) softprops/action-gh-release@v2 -> @V3 (node24) mxschmitt/action-tmate@v3 also uses node20 but the upstream project has not yet released a node24 build; it is a debug-only step so no action is taken for now.
Configuration menu - View commit details
-
Copy full SHA for 511230d - Browse repository at this point
Copy the full SHA 511230dView commit details -
macdeploy: skip missing Qt translation files instead of aborting
macdeployqtplus exited fatally (sys.exit(1)) if any locale in the -add-qt-tr list had no corresponding .qm file in the Qt translations directory. Homebrew Qt@5 on macOS ARM64 does not ship qt_pt.qm (among potentially other locales), causing 'make deploy' to fail with: Error: Could not find Qt translation file "qt_pt.qm" Replace the fatal check with a non-fatal filter: build add_qt_tr by iterating the requested list, appending files that exist and printing a Warning for those that do not. Missing locales are silently omitted from the bundle; present ones are still included.
Configuration menu - View commit details
-
Copy full SHA for 5150d7d - Browse repository at this point
Copy the full SHA 5150d7dView commit details
Commits on May 31, 2026
-
chainparams: initialize vbparams height fields to 0
In CRegTestParams::UpdateActivationParametersFromArgs(), nStartHeight and nTimeoutHeight were declared without an initializer. When -vbparams is invoked with the 3-argument BIP9-compatible form (deployment:start:end), both height fields are skipped by the size() > 3 and size() > 4 guards; with the 4-argument form, nTimeoutHeight is skipped. The indeterminate stack values then flow into UpdateVersionBitsParameters() and corrupt the regtest deployment record, producing non-deterministic versionbits state and intermittent unit / functional test failures (e.g. versionbits_computeblockversion). The behaviour is reachable only on regtest, so mainnet / testnet consensus is unaffected. Initialize both height fields to 0, which matches the implicit contract that omitted optional command-line fields default to 0 and aligns with Bitcoin Core's practice of giving optional -vbparams fields an explicit default (see ReadRegTestArgs()). Reported and analyzed by Aevust: litecoin-project#1095 Reference fix on rincoin-sim: Aevust/rincoin-sim@247dd40 Co-authored-by: Aevust <aevust@users.noreply.github.com>
Configuration menu - View commit details
-
Copy full SHA for b0d626e - Browse repository at this point
Copy the full SHA b0d626eView commit details -
Configuration menu - View commit details
-
Copy full SHA for feba67e - Browse repository at this point
Copy the full SHA feba67eView commit details
Commits on Jul 24, 2026
-
Merge apple-support into dev/driftwood
# Conflicts: # .github/workflows/release-build.yml
Configuration menu - View commit details
-
Copy full SHA for 6daca58 - Browse repository at this point
Copy the full SHA 6daca58View commit details -
Configuration menu - View commit details
-
Copy full SHA for ed1e1f2 - Browse repository at this point
Copy the full SHA ed1e1f2View commit details
Commits on Jul 25, 2026
-
Configuration menu - View commit details
-
Copy full SHA for 458aee6 - Browse repository at this point
Copy the full SHA 458aee6View commit details -
Configuration menu - View commit details
-
Copy full SHA for 714210f - Browse repository at this point
Copy the full SHA 714210fView commit details -
Configuration menu - View commit details
-
Copy full SHA for 45125a3 - Browse repository at this point
Copy the full SHA 45125a3View commit details -
consensus: revert JSON-driven RinHash param table to hardcoded params
Remove the generated rinhash consensus table (json, schema, generator, generated header) and its Makefile codegen rules. Hardcode the Argon2d params (t=2, m=64, lanes=1, salt=RinCoinSalt) directly in RinHash and drop the height-aware overlay resolution; params never varied by height, so PoW output is unchanged. Replace the min_peer_protocol_version overlay with plain Consensus::Params constants (floor 70018 at the same per-network heights) and update net_processing. Remove the getrinhashparams RPC and the getblockchaininfo rinhash object. Retarget the rinhash unit tests and the peer-floor functional test to the constants. Also update the DNS seeder and fixed seed nodes (Community Forge).
Configuration menu - View commit details
-
Copy full SHA for 03a2b32 - Browse repository at this point
Copy the full SHA 03a2b32View commit details -
ci: add GitHub Actions workflow with unit+functional and ASan/UBSan legs
Runs the existing container-based ci/ harness on GitHub Actions. Two matrix legs: a plain unit+functional gate (new fork-appropriate env, no upstream previous-releases downloads) and an ASan/UBSan/integer sanitizer leg. Triggers on push to master and the driftwood integration branches, on pull_request, and on demand.
Configuration menu - View commit details
-
Copy full SHA for 81827d2 - Browse repository at this point
Copy the full SHA 81827d2View commit details -
ci: install libfmt-dev in native CI envs
configure requires libfmt (MWEB links -lfmt; libmw StringUtil uses fmt::format). Neither the new plain env nor the upstream asan env installed it, so configure failed with 'libfmt missing'. Keep ubuntu:20.04 (fmt 6.1.2): libmw uses runtime format strings, which compile on fmt 6/7 but break on fmt 8 (jammy).
Configuration menu - View commit details
-
Copy full SHA for 02bcf10 - Browse repository at this point
Copy the full SHA 02bcf10View commit details -
build: properly wire partially_downloaded_block fuzz target
The FUZZ_TARGETS list carried a malformed entry (test/fuzz/partially_downloaded_block.cpp with an extension) and no per-target _SOURCES/flags block. automake therefore treated it as a program with a default .c source, so 'make distdir' failed with 'No rule to make target test/fuzz/partially_downloaded_block.c'. Use the bare target name and add the standard CPPFLAGS/CXXFLAGS/LDADD/LDFLAGS/SOURCES block like every other fuzz target.
Configuration menu - View commit details
-
Copy full SHA for 05c5761 - Browse repository at this point
Copy the full SHA 05c5761View commit details -
build: drop dangling bench_aggsig target (missing source breaks distdir)
The vendored secp256k1-zkp aggsig module referenced src/bench_aggsig.c, which was never included in the vendored copy. 'make distdir' therefore failed with 'No rule to make target src/bench_aggsig.c'. Remove the bench_aggsig program; a repo-wide scan confirms this was the only remaining missing source reference.
Configuration menu - View commit details
-
Copy full SHA for 60439c0 - Browse repository at this point
Copy the full SHA 60439c0View commit details -
ci: mark work tree as git safe.directory inside the container
make distdir runs 'git archive' to embed clientversion/build info. In the CI container the bind-mounted work tree is owned by the host user while commands run as root, so git (with the backported CVE-2022-24765 ownership check, present even in Ubuntu 20.04's git) aborted with 'detected dubious ownership'. Configure the repo path as a safe.directory for the container root before the build steps.
Configuration menu - View commit details
-
Copy full SHA for aabe209 - Browse repository at this point
Copy the full SHA aabe209View commit details -
ci: use rincoin distdir name in out-of-tree build/test steps
After the litecoin->rincoin package rename, 'make distdir' produces rincoin-\System.Management.Automation.Internal.Host.InternalHost, but the harness still cd'd into litecoin-\System.Management.Automation.Internal.Host.InternalHost for the out-of-tree configure/build, failing with 'No such file or directory'. Update P_CI_DIR and the sequential unit-test glob to rincoin-*; the unit-test binary itself remains test_litecoin.
Configuration menu - View commit details
-
Copy full SHA for 7c37b6e - Browse repository at this point
Copy the full SHA 7c37b6eView commit details -
build: ship argon2 headers in dist (fixes out-of-tree build)
src/crypto/argon2/Makefile.am listed only the .c sources, so 'make distdir' did not copy core.h/encoding.h/etc. into the tarball and the out-of-tree CI build failed with 'core.h: No such file or directory'. Declare the required headers via noinst_HEADERS so they are distributed.
Configuration menu - View commit details
-
Copy full SHA for be2d86c - Browse repository at this point
Copy the full SHA be2d86cView commit details -
ci: build the real tree out-of-tree instead of from make distdir
The distribution tarball produced by 'make distdir' is incomplete: several vendored components (argon2, libmw and its bundled caches/ghc/mio deps) do not declare all of their headers for 'make dist', so building from the dist copy fails (e.g. 'mw/models/crypto/Hash.h: No such file or directory'). Drop the distdir copy and its second configure; build the checked-out tree directly in BASE_BUILD_DIR (VPATH), where every header is present. Fixing 'make dist' completeness is tracked separately from CI.
Configuration menu - View commit details
-
Copy full SHA for 5bdbd11 - Browse repository at this point
Copy the full SHA 5bdbd11View commit details -
secp256k1-zkp: enable extrakeys module in config headers
The vendored secp256k1-zkp uses hardcoded libsecp256k1-config.h headers (included via HAVE_CONFIG_H) that enabled the schnorrsig module but not extrakeys. schnorrsig depends on secp256k1_xonly_pubkey_load, and Taproot support in pubkey.cpp uses secp256k1_xonly_pubkey_parse/_tweak_add_check, all defined by the extrakeys module. Linking rincoind failed with undefined references to those symbols. Define ENABLE_MODULE_EXTRAKEYS so the module's main_impl.h is compiled in.
Configuration menu - View commit details
-
Copy full SHA for 2eb05ba - Browse repository at this point
Copy the full SHA 2eb05baView commit details -
ci: build in-tree to match the release build
The libmw test framework uses a non-VPATH-relative include (-Ilibmw/test/framework/include), so an out-of-tree build could not find test_framework/TxBuilder.h. Combined with the earlier make-dist incompleteness, both classes are avoided by building in-tree (srcdir == builddir), which is exactly how release binaries are produced. P_CI_DIR already defaults to the repo root, so this only drops the separate build dir.
Configuration menu - View commit details
-
Copy full SHA for afb93d9 - Browse repository at this point
Copy the full SHA afb93d9View commit details -
test: fix chain-name field type in rinhash peer-floor test
CBaseChainParams::MAIN/TESTNET/REGTEST/PREVIEW are std::string, not const char*. The Case struct used const char*, which failed to compile under clang. Use std::string (also what SelectParams expects).
Configuration menu - View commit details
-
Copy full SHA for 2c1dd3d - Browse repository at this point
Copy the full SHA 2c1dd3dView commit details -
ci: build headless and upload test-results artifact
The core unit test suite (test_litecoin) passes. The Qt GUI tests (test_rincoin-qt) fail on stale fork data inherited at fork time: URITests uses the litecoin: URI scheme and L-prefixed addresses, RPCNestedTests hardcodes a Litecoin regtest block hash, and WalletTests compares chain-dependent values. These are unrelated to the core/consensus code and cannot be corrected without Rincoin-specific GUI test vectors, so build --without-gui; Qt compilation remains covered by the release build. Updating the Qt test vectors is tracked as a separate follow-up. Also collect the unit-test protocol (test-suite.log/.trs/test_litecoin.log), functional test logs, sanitizer output and config.log into a downloadable 'test-results-<leg>' artifact so results do not have to be hunted in the console log.
Configuration menu - View commit details
-
Copy full SHA for b2b2cc5 - Browse repository at this point
Copy the full SHA b2b2cc5View commit details -
test: complete internal IPv6 prefix update in net and netbase v2 tests
The earlier litecoin-to-rincoin prefix change missed the ADDRv2 serialize and unserialize vectors and the netbase numeric-lookup case, so the core unit tests failed once GUI tests were disabled. Update those vectors to the rincoin-derived prefix. The unserialize ToString is unchanged because the 10-byte payload is unchanged.
Configuration menu - View commit details
-
Copy full SHA for cdedb18 - Browse repository at this point
Copy the full SHA cdedb18View commit details -
docs: add Rincoin parameters reference and consolidate release history
Add doc/rincoin-parameters.md documenting the verifiable Rincoin network/consensus values used by the tests (genesis hashes, ports, magic, address prefixes, internal IPv6 prefix, RinHash params, peer floor) with how to re-derive each from the chain or a formula. Rewrite doc/release-notes-rincoin.md as a consolidated release history covering v1.0.0 through the current development line. Point test/README.md at the parameters doc and update its Litecoin binary references to Rincoin.
Configuration menu - View commit details
-
Copy full SHA for 6a57fbe - Browse repository at this point
Copy the full SHA 6a57fbeView commit details -
test: suppress unsigned-integer-overflow in RinHash crypto for UBSan
The ASan/UBSan leg uses -fsanitize=integer, which reports the intentional mod-2^32 wrapping arithmetic in BLAKE3, Argon2 and SHA3 as unsigned integer overflow, halting the run. This is well-defined behaviour and is handled upstream the same way (see the existing crypto/sha256.cpp etc. entries). Add unsigned-integer-overflow suppressions for crypto/blake3, crypto/argon2 and crypto/sha3.
Configuration menu - View commit details
-
Copy full SHA for a9f2e59 - Browse repository at this point
Copy the full SHA a9f2e59View commit details
Large diffs are not rendered by default.