EP
← All projectsElements Project

libwally-core

Cross-platform wallet primitives for keys, addresses, transactions, PSBT, and Elements.

BitcoinCryptographic librariesSoftware walletsNormal
Repository coverage

154 commits in the local evidence base

Every captured commit receives deterministic security triage and a separate communication-quality score. Security candidates and broader second-pass signals receive full-patch Ollama analysis.

35security candidates39second-pass queue128AI analyses
42commits · 30 days
43commits · 60 days
99commits · 180 days
138commits · 365 days
Backfill bands
Aug 5 → Feb 622 seen3 candidatesComplete
Feb 6 → Jun 652 seen3 candidatesComplete
Jun 6 → Jul 67 seen0 candidatesComplete
Jul 6 → Aug 514 seen1 candidatesComplete
Commit communication

Does the history explain itself?

Message quality measures whether a commit identifies its scope, purpose, rationale, testing, and supporting references. It does not change the security-severity score.

61/100 average clarity
19Strong · 80–100
63Adequate · 60–79
59Thin · 40–59
13Opaque · 0–39
1security candidate with opaque commit messaging
Read the scoring rubric →
Developer activity

Who is changing the project?

Public Git author strings; identities are not independently verified.

DeveloperCommitsCandidatesAnalyzedHigh riskMessage avg.
Jon Griffiths12427102158
kkdao444075
odudex514069
Erick Cestari1110100
KY-U111075
Ondřej Češka111050
dependabot[bot]808093
pythcoiner301063
Daniel Newton202055
Greg Sanders101068
Leonardo Comandini101060
longhutianjie101072
Analysis record

Published AI watches

Last scanned 47 minutes ago

Low 40 AI analysisMessage 75 · Adequate
EP Elements Projectlibwally-core BitcoinCryptographic librariesSoftware wallets

psbt: allow unknowns (global, input and output) to have empty values.

This commit fixes a bug in how the library reads partially-signed Bitcoin transactions (PSBTs). Previously, if a PSBT contained an unknown extra field with an empty value, the library would store a dangling pointer to a zero-length buffer …

Use of potentially dangling pointer for zero-length bufferMemory-safety bug in PSBT deserializationAddition of regression test for malformed/edge-case PSBT input
10670278by Jon Griffiths+9−23 files
No security note in commit
Informational 15 AI analysisMessage 38 · Opaque
EP Elements Projectlibwally-core BitcoinCryptographic librariesSoftware wallets

Bump version to 1.6.1

This commit only updates version numbers across build files, documentation, and package metadata from 1.6.0 to 1.6.1. There are no code logic changes, no bug fixes, and no security-related modifications.

f7b0a15bby Jon Griffiths+12−129 files
No security note in commit
Informational 15 AI analysisMessage 50 · Thin
EP Elements Projectlibwally-core BitcoinCryptographic librariesSoftware wallets

tx: add add tx_input_is_issuance/tx_is_input_issuance to determine issuance inputs

This commit adds two new helper functions that let callers ask whether a transaction input is an 'issuance' input on the Elements sidechain. It is a straightforward feature addition: it exposes existing internal data through a new API, mir…

91689c1cby Jon Griffiths+42−58 files
No security note in commit
Low 44 AI analysisMessage 73 · Adequate
EP Elements Projectlibwally-core BitcoinCryptographic librariesSoftware wallets

psbt: Copy the PSET genesis blockhash

This commit fixes a bug where cloning or combining a special Bitcoin transaction format (PSET) dropped the 'genesis blockhash' field. Without that field, valid signatures could not be created for certain transactions using Elements taproot…

Missing field copy in PSET clone/combine pathAffects Elements taproot signature hash computationCould produce an unsignable or invalidly-signed PSET
4b64af46by kkdao+3−01 file
No security note in commit
Moderate 60 AI analysisMessage 68 · Adequate
EP Elements Projectlibwally-core BitcoinCryptographic librariesSoftware wallets

psbt: Refuse upgrading a v0 PSBT with no tx

This commit fixes a crash bug in libwally-core, a Bitcoin/Elements cryptography library. When a user tried to upgrade an older-style PSBT (Partially Signed Bitcoin Transaction) to version 2, the code would follow a pointer to transaction d…

NULL pointer dereference in transaction-version upgrade pathMissing input validation on internal object state before pointer dereferenceConsistency fix aligning with existing psbt_build_tx() and v0 error handling
e76b2304by kkdao+10−02 files
No security note in commit
Low 49 AI analysisMessage 50 · Thin
EP Elements Projectlibwally-core BitcoinCryptographic librariesSoftware wallets

mem: use wally_memcpy for more secret/potentially secret data

This commit replaces ordinary memory-copy operations with a special secure-copy function (wally_memcpy) in a handful of places that handle private keys, BIP32 extended keys, and descriptor template secrets. The goal is to reduce the chance…

secret-data handling (private keys, BIP32 extended keys, SLIP77 blinding key)use of hardened memory-copy primitive (wally_memcpy)defensive hardening against compiler optimization of sensitive copies
473b9161by Jon Griffiths+8−83 files
No security note in commit
Informational 19 AI analysisMessage 65 · Adequate
EP Elements Projectlibwally-core BitcoinCryptographic librariesSoftware wallets

tx: add tx_input_is_pegin/tx_is_input_pegin to determine pegin inputs

This commit is a routine API cleanup: it adds two new functions with clearer names for checking whether a transaction input is a 'pegin' (a special type of cross-chain input used in Elements-based blockchains), and marks the old function n…

1576afb5by Dmytro Hladkykh+48−1610 files
No security note in commit
Low 45 AI analysisMessage 73 · Adequate
EP Elements Projectlibwally-core BitcoinCryptographic librariesSoftware wallets

psbt: Refuse v2 global tx under loose parsing

This change fixes a memory leak in the library's handling of a specific kind of invalid Bitcoin transaction file (PSBT v2 with an unexpected global transaction). Previously, parsing such a file under loose parsing could allocate memory for…

Memory leak on parsing malformed PSBT v2 with global txInvalid PSBT v2 accepted under loose parsing flagPointer overwrite after allocation in psbt_set_global_tx / v2 path
10f41d80by kkdao+17−13 files
No security note in commit
Informational 15 AI analysisMessage 85 · Strong
EP Elements Projectlibwally-core BitcoinCryptographic librariesSoftware wallets

Add 1.6.0 upgrade advice to CHANGES.md

This commit only updates the project's changelog text (CHANGES.md) to match the published 1.6.0 release notes. It adds a sentence telling users that the release contains important bug and security fixes and that they should update. No code…

7f8f89e8by kkdao+3−01 file
Vendor flagged security relevance
Moderate 60 AI analysisMessage 78 · Adequate
EP Elements Projectlibwally-core BitcoinCryptographic librariesSoftware wallets

psbt: fix finalizing large P2SH and bare multisig inputs

This commit fixes two bugs in how the library finalizes old-style multi-signature Bitcoin transactions. First, large multisig setups (like 5-of-5 or 4-of-7) were silently left unfinished because the buffer used was too small. Second, for b…

Buffer size mismatch causing silent failure to finalize large multisig inputsIncorrect scriptSig construction for bare multisig producing invalid spendsHeap allocation introduced to replace undersized stack buffer
cf8eb142by odudex+136−82 files
No security note in commit
Informational 22 AI analysisMessage 73 · Adequate
EP Elements Projectlibwally-core BitcoinCryptographic librariesSoftware wallets

tx: allow getting the weight and vsize of partial transactions

This commit fixes a bug where two helper functions for calculating transaction size/weight would incorrectly reject transactions that were still being built (for example, when a wallet is estimating fees before all inputs and outputs are a…

Behavior change in argument validation pathRelaxation of a previously added strict checkNo memory safety, cryptographic, or authorization changes visible
01d53ac9by odudex+44−22 files
No security note in commit
Informational 15 AI analysisMessage 38 · Opaque
EP Elements Projectlibwally-core BitcoinCryptographic librariesSoftware wallets

Bump version to 1.6.0

This commit is a routine version bump from 1.5.6 to 1.6.0. It only changes version numbers in build files, documentation, and package metadata. There are no code changes that affect security.

530eb957by Jon Griffiths+14−149 files
No security note in commit
Low 35 AI analysisMessage 73 · Adequate
EP Elements Projectlibwally-core BitcoinCryptographic librariesSoftware wallets

tx: prevent pre-bip144 serialization on elements, share arg checks

This commit tightens and unifies how transaction serialization arguments are checked in libwally-core. It prevents a caller from accidentally producing ambiguous pre-BIP144 transaction formats on Elements-based networks, and makes the leng…

Inconsistent argument validation between length and serialization functionsBehavior change for Elements: pre-BIP144 flag is now ignored rather than honoredDefensive unification of transaction serialization checks
063c195dby Jon Griffiths+33−221 file
No security note in commit
Low 47 AI analysisMessage 50 · Thin
EP Elements Projectlibwally-core BitcoinCryptographic librariesSoftware wallets

psbt: disallow hybrid pubkeys

This commit tightens public-key validation inside PSBT (Partially Signed Bitcoin Transaction) handling by rejecting 'hybrid' public keys. Hybrid keys are an old, non-standard encoding that sits between compressed and uncompressed formats. …

Rejects non-standard hybrid public-key encoding in transaction-related dataNarrows public-key acceptance to only compressed/uncompressed standard encodingsApplies consistent strict validation across keypath, signature, and blinding pubkey paths
06fba283by Jon Griffiths+4−42 files
No security note in commit
Informational 23 AI analysisMessage 83 · Strong
EP Elements Projectlibwally-core BitcoinCryptographic librariesSoftware wallets

expose ec_public_key_strict_verify to verify non-hybrid pubkeys

This commit adds a new public function that lets callers check whether a Bitcoin-style public key is valid and is not an old, rarely-used 'hybrid' key format. It does not change existing behavior; it only exposes a new, stricter verificati…

New strict public-key validation API rejecting hybrid (0x06/0x07 prefixed uncompressed) public keysHybrid keys are still accepted by the pre-existing wally_ec_public_key_verify; only the new strict call rejects themNo buffer overflow, memory corruption, or cryptographic flaw visible in the diff
e9ff9b8eby Jon Griffiths+39−09 files
No security note in commit
Informational 15 AI analysisMessage 50 · Thin
EP Elements Projectlibwally-core BitcoinCryptographic librariesSoftware wallets

bip39: document that mnemonic/passphrase arguments require ascii/utf8 nfkd

This commit only updates documentation comments in a header file. It adds a note that BIP39 mnemonic and passphrase arguments must be ASCII or UTF-8 NFKD encoded. No code behavior changed, no bug was fixed, and no security vulnerability wa…

abbe03ceby Jon Griffiths+6−61 file
No security note in commit
Moderate 51 AI analysisMessage 50 · Thin
EP Elements Projectlibwally-core BitcoinCryptographic librariesSoftware wallets

bip39: fail if the callers requested language is not found

This commit fixes a behavior in the BIP39 (mnemonic seed phrase) code where, if a caller asked for a language that wasn't supported, the library would quietly give them the English wordlist instead of reporting an error. The patch makes th…

Silent fallback to default language could cause language/cross-check mismatchesBehavioral change from permissive fallback to explicit failurePotential downstream impact if callers previously passed invalid language strings and relied on English fallback
9f912adaby Jon Griffiths+8−41 file
No security note in commit
Informational 14 AI analysisMessage 93 · Strong
EP Elements Projectlibwally-core BitcoinCryptographic librariesSoftware wallets

build(deps-dev): bump fast-uri from 3.1.7 to 3.1.9 in /src/wasm_package

This is an automated Dependabot update that bumps a JavaScript development dependency called fast-uri from version 3.1.7 to 3.1.9 inside the WebAssembly packaging directory. The change only updates a package-lock.json file. There is no dir…

Dependency bump of a URI-parsing library, which is a component class commonly associated with input-validation vulnerabilitiesNo explicit security claim, CVE, or advisory reference in the commit or supplied materialsNo source code changes beyond lockfile metadata
9bfb5c78by dependabot[bot]+6−61 file
No security note in commit
Moderate 64 AI analysisMessage 95 · Strong
EP Elements Projectlibwally-core BitcoinCryptographic librariesSoftware wallets

sign: verify schnorr sigs after creation

This commit adds a safety check when creating Schnorr digital signatures in libwally-core. After a signature is generated, the code now immediately verifies it using the corresponding public key. If the signature fails verification, it is …

Schnorr signature verification immediately after signingOutput buffer cleared when signature generation or verification failsPrivate-key leakage risk explicitly mentioned in commit message
4e3d596fby Jon Griffiths+8−11 file
Vendor flagged security relevance
Low 44 AI analysisMessage 38 · Opaque
EP Elements Projectlibwally-core BitcoinCryptographic librariesSoftware wallets

bip38: fail if aes fails

This commit fixes a programming oversight in the BIP38 encrypted-key code. Previously, the AES encryption/decryption helper functions ignored any error returned by the underlying AES routine. If AES failed for some reason, the code would c…

Unchecked return value from cryptographic primitive (wally_aes) fixedAES failure during BIP38 encryption/decryption could previously produce or accept malformed key materialError propagation added to both encryption and decryption paths
7a723188by Jon Griffiths+26−141 file
No security note in commit
Repository ledger

Explore captured commits

Expand any commit for its author, full message, clarity score, changed files, triage signals, analysis, and source link.

Lower-priorityupdate CHANGES.md for release 1.5.4by Jon Griffiths · cea4227f · Jun 16, 2026 · 1 fileMessage 45 · ThinInformational 15Details
Commit message · Jon Griffiths

update CHANGES.md for release 1.5.4

45/100 · ThinMessage clarity
✓ Descriptive subject✓ Names a concrete action or component! No meaningful explanatory body
Why it was queued
documentation-only discount
AI analysis · Informational 15/100

This commit only updates the project's changelog file (CHANGES.md) to document what is included in the upcoming 1.5.4 release. No actual source code, build scripts, or configuration files were changed. It is a documentation-only release-notes update.

Lower-priorityci: update ci imageby Jon Griffiths · a212c0d3 · Jun 16, 2026 · 1 fileMessage 40 · ThinInformational 15Details
Commit message · Jon Griffiths

ci: update ci image

40/100 · ThinMessage clarity
✓ Subject identifies a change✓ Uses a recognizable type or scope! No meaningful explanatory body
AI analysis · Informational 15/100

This commit simply swaps the Docker image used by the project's automated CI (continuous integration) pipeline to a newer version. There is no change to the actual library code, no user-facing behavior change, and no security-relevant signal visible in the diff.

Lower-prioritydocker: update trixie base imageby Jon Griffiths · 112c0ff3 · Jun 16, 2026 · 1 fileMessage 45 · ThinInformational 15Details
Commit message · Jon Griffiths

docker: update trixie base image

45/100 · ThinMessage clarity
✓ Descriptive subject✓ Names a concrete action or component! No meaningful explanatory body
AI analysis · Informational 15/100

This commit simply updates the pinned SHA256 digest of the Debian 'trixie' base Docker image used for building and testing. It is a routine dependency refresh with no code changes and no security-relevant content described by the project.

Lower-priorityelements: align unblinding with the elements implby Jon Griffiths · d8153d1c · Jun 16, 2026 · 1 fileMessage 45 · ThinModerate 59Details
Commit message · Jon Griffiths

elements: align unblinding with the elements impl

45/100 · ThinMessage clarity
✓ Descriptive subject✓ Names a concrete action or component! No meaningful explanatory body
AI analysis · Moderate 59/100

This commit tightens the unblinding process for confidential asset transactions in the Elements/Liquid sidechain. Previously, the code blindly trusted the decrypted message and did not verify that the extracted asset ID and blinding factor actually match the original cryptographic commitments. The patch adds verification steps: after decryption it re-derives the asset generator and value commitment and compares them to the inputs. If they do not match, it clears the sensitive outputs and returns an error. This prevents a class of attacks where a malicious or malformed blinded output could make the wallet accept an incorrect asset ID or amount.

Lower-priorityjava: only set source level to 17 if supported by javacby Jon Griffiths · 71fd4c4c · May 28, 2026 · 1 fileMessage 50 · ThinInformational 18Details
Commit message · Jon Griffiths

java: only set source level to 17 if supported by javac

50/100 · ThinMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component! No meaningful explanatory body
AI analysis · Informational 18/100

This commit changes the Java build configuration so that it falls back to Java 8 source compatibility when the compiler does not support Java 17, instead of unconditionally requiring Java 17. It is a build-system compatibility fix, not a security patch.

Lower-priorityjs: update github build to ubuntu 24.04by Jon Griffiths · 4976dc48 · May 28, 2026 · 1 fileMessage 45 · ThinInformational 15Details
Commit message · Jon Griffiths

js: update github build to ubuntu 24.04

45/100 · ThinMessage clarity
✓ Descriptive subject✓ Names a concrete action or component! No meaningful explanatory body
Why it was queued
documentation-only discount
AI analysis · Informational 15/100

This commit simply updates the GitHub Actions workflow that builds the JavaScript/WebAssembly package. It changes the build runner from Ubuntu 22.04 to Ubuntu 24.04 and switches the dependency installation script from one named for Debian 'bullseye' to one named for 'trixie'. There is no code change affecting users, no security fix, and no vulnerability introduced.

Lower-prioritybase64: fix -Wunterminated-string-initialization warningsby Jon Griffiths · cb95fe3f · May 28, 2026 · 1 fileMessage 50 · ThinInformational 15Details
Commit message · Jon Griffiths

base64: fix -Wunterminated-string-initialization warnings

50/100 · ThinMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component! No meaningful explanatory body
AI analysis · Informational 15/100

This commit changes how two fixed lookup tables are written in the source code for the base64 encoding/decoding module. The old form used long string literals made of many hex escape characters; the new form lists individual characters/bytes inside braces. The commit message says the purpose is to silence a compiler warning about unterminated string initialization. The data values in the tables are identical before and after, so this is a code-style/maintenance change, not a security fix.

Lower-prioritybuild: add python 3.14 support, disable 3.15 while in betaby Jon Griffiths · 11c7da3e · May 28, 2026 · 1 fileMessage 62 · AdequateInformational 15Details
Commit message · Jon Griffiths

build: add python 3.14 support, disable 3.15 while in beta

62/100 · AdequateMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Uses a recognizable type or scope! No meaningful explanatory body
Why it was queued
documentation-only discount
AI analysis · Informational 15/100

This commit is a routine build configuration update. It changes one line in the project's wheel-building workflow so that Python 3.14 wheels are now built and Python 3.15 wheels are skipped while Python 3.15 is still in beta. There is no security relevance in the change itself.

Lower-prioritybuild: remove abandoned msvc-dev-cmd from window wheel buildby Jon Griffiths · 53452d74 · May 28, 2026 · 1 fileMessage 62 · AdequateInformational 15Details
Commit message · Jon Griffiths

build: remove abandoned msvc-dev-cmd from window wheel build

62/100 · AdequateMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Uses a recognizable type or scope! No meaningful explanatory body
Why it was queued
documentation-only discount
AI analysis · Informational 15/100

This commit swaps one way of setting up Microsoft's C++ compiler on Windows in the project's automated wheel-building workflow. It replaces a third-party GitHub Action (msvc-dev-cmd) with a direct call to a Microsoft-provided batch file on the runner. There is no code change that affects the library's behavior, its cryptography, or how it handles user input.

Lower-priorityjava: update source and target version to 17by Jon Griffiths · 53d900a9 · May 28, 2026 · 1 fileMessage 60 · AdequateInformational 16Details
Commit message · Jon Griffiths

java: update source and target version to 17

Fixes the obsolete version warning when building.

60/100 · AdequateMessage clarity
✓ Descriptive subject✓ Names a concrete action or component✓ Provides an explanatory body
AI analysis · Informational 16/100

This commit simply changes the Java compiler target version from 1.8 to 17 in the build configuration. It is a routine build hygiene change to silence an obsolete-version warning and does not alter any program logic, cryptographic code, or security behavior.

Lower-priorityjava: disable loadLibrary warning running testsby Jon Griffiths · 82275dd4 · May 28, 2026 · 1 fileMessage 70 · AdequateInformational 15Details
Commit message · Jon Griffiths

java: disable loadLibrary warning running tests

Note this means that java v20+ is now required for testing.

70/100 · AdequateMessage clarity
✓ Descriptive subject✓ Names a concrete action or component✓ Provides an explanatory body✓ Mentions testing or verification
AI analysis · Informational 15/100

This is a small build/test configuration change for Java tests. It adds a Java command-line option that suppresses a warning when native (non-Java) libraries are loaded during testing. The change only affects how tests are run and requires Java 20 or newer. There is no indication it fixes or introduces a security vulnerability.

Lower-prioritybuild: build wheel and sdist separatelyby Jon Griffiths · 05bfee5d · May 28, 2026 · 1 fileMessage 90 · StrongInformational 12Details
Commit message · Jon Griffiths

build: build wheel and sdist separately

Something in the secp aux macros breaks when building the sdist and
wheel at the same time. Build them separately to work around this.

Note that we only want the sdist artifact; the wheel is just used for
smoke testing before producing the sdist.

90/100 · StrongMessage clarity
✓ Descriptive subject✓ Names a concrete action or component✓ Uses a recognizable type or scope✓ Provides detailed explanatory context✓ Mentions testing or verification
AI analysis · Informational 12/100

This commit changes the project's automated build script so that Python wheel and source distribution packages are built in two separate steps instead of one combined step. The commit message says this is a workaround because something in the secp256k1 auxiliary macros breaks when both are built together. The wheel is only used for a quick smoke test; the final artifact they keep is the source distribution. There is no indication this is a security fix.

Lower-priorityci: factor out common test config, rebuild wallycore docker imageby Jon Griffiths · d601cbd5 · May 28, 2026 · 1 fileMessage 72 · AdequateInformational 15Details
Commit message · Jon Griffiths

ci: factor out common test config, rebuild wallycore docker image

72/100 · AdequateMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Uses a recognizable type or scope✓ Mentions testing or verification! No meaningful explanatory body
AI analysis · Informational 15/100

This commit only reorganizes the project's GitLab CI configuration file. It creates a shared template for test jobs and updates the Docker image used for testing to a newer version. There are no changes to the actual library code, cryptographic logic, or any files that end users install.

AI review queuedcmake: add missing definesby Jon Griffiths · be278177 · May 27, 2026 · 2 filesMessage 35 · OpaqueLow 32Details
Commit message · Jon Griffiths

cmake: add missing defines

35/100 · OpaqueMessage clarity
✓ Descriptive subject! No meaningful explanatory body
Why it was queued
second-pass: opaque commit message
AI analysis · Low 32/100

This commit fixes the CMake build system so it correctly detects several platform features and headers that the library's C code relies on. Before this fix, the CMake build could silently produce a misconfigured library that uses less secure fallback code paths (for example, missing secure memory-zeroing functions or unaligned-access handling). The commit does not change the core cryptographic code itself; it only changes how the build system discovers what the current platform supports.

Lower-prioritytests: use the (now) already-installed gcovr binaryby Jon Griffiths · c153347c · May 27, 2026 · 1 fileMessage 60 · AdequateInformational 15Details
Commit message · Jon Griffiths

tests: use the (now) already-installed gcovr binary

60/100 · AdequateMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Mentions testing or verification! No meaningful explanatory body
AI analysis · Informational 15/100

This is a tiny CI (continuous integration) maintenance change. It removes a redundant pip install command for a code-coverage tool called gcovr, because that tool is now pre-installed in the test environment. There is no change to the actual library code, cryptography, or anything users interact with.

Lower-prioritybuild: run swig python tests lastby Jon Griffiths · a2804b36 · May 27, 2026 · 1 fileMessage 100 · StrongInformational 15Details
Commit message · Jon Griffiths

build: run swig python tests last

Since the swig python tests were updated to build the python wheel using
setup.py, 'make check' has issues due to the wheel build reconfiguring
the source tree when being built while the other tests are running.

Change this to run all other tests before the swig python tests; This
fixes 'make check' including for parallel builds.

100/100 · StrongMessage clarity
✓ Descriptive subject✓ Names a concrete action or component✓ Uses a recognizable type or scope✓ Provides detailed explanatory context✓ Explains rationale or failure mode✓ Mentions testing or verification
AI analysis · Informational 15/100

This commit is a build-system fix that changes the order in which automated tests run during 'make check'. It moves the Python wheel-building tests to run last, because building the Python wheel while other tests are running in parallel was causing test failures. There is no security-relevant code change here.

Lower-priorityci: update scan-build, asan and valgrind for trixieby Jon Griffiths · 5adb8acc · May 27, 2026 · 1 fileMessage 87 · StrongInformational 15Details
Commit message · Jon Griffiths

ci: update scan-build, asan and valgrind for trixie

Run valgrind tests on the test binaries not the libtool wrapper scripts.

87/100 · StrongMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Uses a recognizable type or scope✓ Provides an explanatory body✓ Mentions testing or verification
AI analysis · Informational 15/100

This commit is a routine update to the project's automated testing configuration for newer Debian 'trixie' tooling versions. It changes CI paths from older GCC 10/Clang 11 tool versions to newer GCC 14/Clang 19 versions, and adjusts the Valgrind test step to run directly on compiled test binaries instead of libtool wrapper scripts. There is no change to the actual library source code, no bug fix, and no security patch.

Lower-prioritybuild: re-apply: don't require linking to work for manylinux buildsby Jon Griffiths · 5d9149b1 · May 27, 2026 · 1 fileMessage 62 · AdequateInformational 15Details
Commit message · Jon Griffiths

build: re-apply: don't require linking to work for manylinux builds

62/100 · AdequateMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Uses a recognizable type or scope! No meaningful explanatory body
AI analysis · Informational 15/100

This commit changes the build configuration so that when building Python packages for 'manylinux' (a standard for portable Linux Python wheels), a failed link check against libpython is ignored. This is a build-system workaround, not a code change, and it does not alter cryptographic behavior, memory handling, or runtime security.

Lower-prioritybuild: require python 3.9 or later. use new optionality and python checkby Jon Griffiths · f512c79c · May 27, 2026 · 1 fileMessage 77 · AdequateInformational 16Details
Commit message · Jon Griffiths

build: require python 3.9 or later. use new optionality and python check

Optionality means we don't need our previous hack from commit
d6b1fe21d070134bad11ffd6f091927201dfa856.

77/100 · AdequateMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Uses a recognizable type or scope✓ Provides an explanatory body
AI analysis · Informational 16/100

This commit updates the build system to require Python 3.9 or newer instead of Python 2.7 or newer. It also changes how the build detects whether Python development files are available, using a cleaner built-in option rather than a previous workaround. There is no direct security fix here; it is a build-maintenance change that removes outdated Python 2 support.

Lower-prioritybuild: update ax_python_devel.m4 to latest upstream revisionby Jon Griffiths · 3d6529b0 · May 27, 2026 · 1 fileMessage 62 · AdequateInformational 15Details
Commit message · Jon Griffiths

build: update ax_python_devel.m4 to latest upstream revision

62/100 · AdequateMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Uses a recognizable type or scope! No meaningful explanatory body
AI analysis · Informational 15/100

This commit updates a single build-system helper file used during software compilation. It does not change any wallet, cryptography, or transaction-handling code. There is no indication this change fixes or introduces a security vulnerability.

Lower-priorityci: update ci refs to run on trixieby Jon Griffiths · 4fbdb23e · May 27, 2026 · 1 fileMessage 57 · ThinInformational 15Details
Commit message · Jon Griffiths

ci: update ci refs to run on trixie

57/100 · ThinMessage clarity
✓ Descriptive subject✓ Names a concrete action or component✓ Uses a recognizable type or scope! No meaningful explanatory body
AI analysis · Informational 15/100

This commit only updates the continuous integration (CI) configuration to use newer Docker images for testing. It changes the name and version hash of the test container from an old GreenAddress image to a newer Blockstream one based on Debian 'trixie'. There are no changes to the actual library code that users run, so this does not introduce or fix a security vulnerability in the software itself.

Lower-prioritydocker: add a multi-arch docker build stage to the ciby Jon Griffiths · 84a444f8 · May 27, 2026 · 1 fileMessage 73 · AdequateInformational 15Details
Commit message · Jon Griffiths

docker: add a multi-arch docker build stage to the ci

This builds amd64 and arm64 images for the same commit ref.

Note the location of the docker image has changed from "greenaddress/"
to "blockstream/".

73/100 · AdequateMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Provides detailed explanatory context
AI analysis · Informational 15/100

This commit adds a new CI/CD pipeline stage that builds Docker images for two processor architectures (amd64 and arm64) and pushes them to Docker Hub under the 'blockstream/' organization. It is purely an infrastructure/automation change and does not modify any library code, cryptographic logic, or user-facing behavior.

Lower-prioritydocker: add a trixie docker image, update node and emsdkby Jon Griffiths · e982b2d6 · May 27, 2026 · 4 filesMessage 73 · AdequateInformational 15Details
Commit message · Jon Griffiths

docker: add a trixie docker image, update node and emsdk

Node v20 is EOL; move to v24. The latest emsdk is now available on both
amd64 and arm64, so update that too.

update-java-alternatives is unneeded (and broken) on trixie, so don't
run it. Fix JAVA_HOME to work on amd64 and arm64.

73/100 · AdequateMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Provides detailed explanatory context
AI analysis · Informational 15/100

This commit updates the project's Docker build images. It adds support for Debian Trixie, upgrades the included Node.js version from 20 to 24, updates the Emscripten SDK used for JavaScript builds, and fixes Java environment settings for both Intel/AMD and ARM processors. There are no changes to the library's actual cryptographic or wallet code.

Security candidatesecp: update to latest zkp-masterby Jon Griffiths · b23895f1 · May 25, 2026 · 1 fileMessage 45 · ThinInformational 0Details
Commit message · Jon Griffiths

secp: update to latest zkp-master

45/100 · ThinMessage clarity
✓ Descriptive subject✓ Names a concrete action or component! No meaningful explanatory body
Why it was queued
cryptography-sensitive path
AI analysis · Informational 0/100

This commit is described as updating a bundled cryptographic library (secp256k1) to a newer version, but the actual code changes are not available for review. Without the diff, we cannot determine whether the update fixes security bugs, introduces new ones, or is purely routine maintenance.

AI review queuedbuild: remove distutils dependencyby Jon Griffiths · dbaa9393 · May 25, 2026 · 1 fileMessage 47 · ThinInformational 19Details
Commit message · Jon Griffiths

build: remove distutils dependency

47/100 · ThinMessage clarity
✓ Descriptive subject✓ Uses a recognizable type or scope! No meaningful explanatory body
Why it was queued
second-pass: broader security terminology
AI analysis · Informational 19/100

This is a tiny build-maintenance change: it replaces the deprecated Python `distutils.sysconfig` module with the newer `sysconfig` module in the package setup script. There is no security vulnerability visible in the diff, no change to cryptographic code, and no disclosed incident. It is a routine compatibility cleanup.