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 43 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.

Security candidatepsbt: return an error if fetching input_amount when not presentby Jon Griffiths · fa3a5859 · Aug 9, 2026 · 8 filesMessage 73 · AdequateLow 40Details
Commit message · Jon Griffiths

psbt: return an error if fetching input_amount when not present

Add has_input_amount to allow callers to determine field presence in the
same way as output_amount.

Also remove non-existent input_value accessors from the SWIG Java
wrapper.

Note this is an ABI change.

73/100 · AdequateMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Provides detailed explanatory context
Why it was queued
signing boundarysigning or wallet path
AI analysis · Low 40/100

This commit changes a library function so that it now returns an error when a PSBT/PSET input amount is missing, instead of silently returning zero. It also adds a new 'has_input_amount' check so callers can ask whether the value exists before reading it. The change is an intentional fix to prevent callers from accidentally treating a missing amount as zero. It also cleans up some old, non-existent function names in the Java wrapper.

Security candidatepsbt: return an error if fetching output_amount when not presentby Jon Griffiths · 07871406 · Aug 9, 2026 · 2 filesMessage 50 · ThinLow 34Details
Commit message · Jon Griffiths

psbt: return an error if fetching output_amount when not present

Note this is an ABI change.

50/100 · ThinMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component! No meaningful explanatory body
Why it was queued
signing boundarysigning or wallet path
AI analysis · Low 34/100

This commit changes a library function so that it returns an error when asked for an output amount that is not actually present, instead of silently returning zero. This prevents callers from accidentally treating a missing amount as a real zero-value output, which could lead to incorrect transaction handling in Bitcoin/Elements PSBT workflows.

Security candidatepsbt: reject trailing data when parsing if WALLY_PSBT_PARSE_FLAG_COMPLETE is usedby KY-U · 3bf543cd · Aug 6, 2026 · 5 filesMessage 75 · AdequateModerate 51Details
Commit message · KY-U

psbt: reject trailing data when parsing if WALLY_PSBT_PARSE_FLAG_COMPLETE is used

Set the flag unconditionally for base64 inputs.

Add PSBT v0 and v2 regression test cases with a trailing byte.

75/100 · AdequateMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Provides an explanatory body✓ Mentions testing or verification
Why it was queued
signing boundaryfuzzing or regression evidencesigning or wallet path
AI analysis · Moderate 51/100

This commit tightens how the library reads PSBT (Partially Signed Bitcoin Transaction) data. It adds a new parsing flag that requires the parser to consume the entire input, and turns that flag on automatically when reading base64-encoded PSBTs. Previously, extra bytes tacked onto the end of a PSBT could be silently ignored. The change is defensive: it helps prevent malformed or intentionally padded PSBTs from being accepted as valid.

AI review queuedbuild(deps-dev): bump fast-uri from 3.1.4 to 3.1.5 in /src/wasm_packageby dependabot[bot] · d3f6adf0 · Aug 5, 2026 · 1 fileMessage 93 · StrongInformational 15Details
Commit message · dependabot[bot]

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

Bumps [fast-uri](https://github.com/fastify/fast-uri) from 3.1.4 to 3.1.5.
- [Release notes](https://github.com/fastify/fast-uri/releases)
- [Commits](https://github.com/fastify/fast-uri/compare/v3.1.4...v3.1.5)

---
updated-dependencies:
- dependency-name: fast-uri
dependency-version: 3.1.5
dependency-type: indirect
...

Signed-off-by: dependabot[bot] <support@github.com>

93/100 · StrongMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Uses a recognizable type or scope✓ Provides detailed explanatory context✓ Links an issue, advisory, or supporting reference
Why it was queued
automated dependency-update discountsecond-pass: broader security terminology
AI analysis · Informational 15/100

This is an automated dependency update by Dependabot that bumps the JavaScript package fast-uri from version 3.1.4 to 3.1.5 inside the WebAssembly packaging directory. The change only updates version numbers and package hashes in package-lock.json. There is no indication in the commit itself that this fixes a security issue, and no security references were provided.

Lower-priorityjava: use len fn to allocate wrapper buffer for aes encrypt/decryptby Jon Griffiths · c68f6683 · Aug 3, 2026 · 1 fileMessage 65 · AdequateTriage 0Details
Commit message · Jon Griffiths

java: use len fn to allocate wrapper buffer for aes encrypt/decrypt

Reported-by: Efstratios Kaplanellis (@5tratan) of Almamater Technologies

65/100 · AdequateMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Provides an explanatory body
Security candidateaes: add missing length check for multi-chunk encrypt/decrypt, with testsby Jon Griffiths · e9fed8a4 · Aug 3, 2026 · 2 filesMessage 75 · AdequateLow 47Details
Commit message · Jon Griffiths

aes: add missing length check for multi-chunk encrypt/decrypt, with tests

Reported-by: Efstratios Kaplanellis (@5tratan) of Almamater Technologies

75/100 · AdequateMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Provides an explanatory body✓ Mentions testing or verification
Why it was queued
cryptography-sensitive path
AI analysis · Low 47/100

This commit fixes a missing safety check in libwally-core's AES encryption/decryption function. Previously, callers could pass an output buffer smaller than the input data, which could lead to writing past the end of the buffer (a buffer overflow). The patch now rejects such calls and adds tests for many invalid input combinations. The issue was reported by an outside security researcher.

Security candidatejava: fix output type for psbt_get_output_amountby Jon Griffiths · aed82410 · Aug 3, 2026 · 1 fileMessage 60 · AdequateLow 36Details
Commit message · Jon Griffiths

java: fix output type for psbt_get_output_amount

Reported-by: Efstratios Kaplanellis (@5tratan) of Almamater Technologies

60/100 · AdequateMessage clarity
✓ Descriptive subject✓ Names a concrete action or component✓ Provides an explanatory body
Why it was queued
signing boundary
AI analysis · Low 36/100

This commit fixes a Java language binding bug where a function that reads a Bitcoin transaction output amount was incorrectly declared to return a 'size' type (a memory/length value) instead of an unsigned 64-bit integer. Output amounts in Bitcoin are 64-bit integers, so the wrong return type could cause the returned value to be truncated, misinterpreted, or trigger type-conversion errors in Java applications using libwally-core. The fix is a one-line change in the SWIG interface file used to generate Java wrappers.

Security candidatecrypto: add ec_public_key_compress to produce a compressed pubkeyby Jon Griffiths · 03351cc9 · Jul 31, 2026 · 10 filesMessage 73 · AdequateInformational 15Details
Commit message · Jon Griffiths

crypto: add ec_public_key_compress to produce a compressed pubkey

Allow both compress and decompress to work (as a no-op) on already
compressed/decompressed pubkeys.

Co-authored-by: odudex <odudex@proton.me>

73/100 · AdequateMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Provides detailed explanatory context
Why it was queued
cryptography-sensitive pathsigning or wallet path
AI analysis · Informational 15/100

This commit adds a new public-key compression function to a cryptographic library and updates the existing decompression function so both can accept already-compressed or already-uncompressed keys as input. It also adds tests and language bindings. There is no security vulnerability here; it is a normal feature addition with defensive input validation.

AI review queuedtests: add tests for parsing invalid der sigsby Jon Griffiths · 824e8a33 · Jul 31, 2026 · 1 fileMessage 55 · ThinInformational 12Details
Commit message · Jon Griffiths

tests: add tests for parsing invalid der sigs

55/100 · ThinMessage clarity
✓ Descriptive subject✓ Names a concrete action or component✓ Mentions testing or verification! No meaningful explanatory body
Why it was queued
signing or wallet pathsecond-pass: security-sensitive path
AI analysis · Informational 12/100

This commit only adds new test cases to check that the library correctly rejects malformed cryptographic signatures. It does not change any production code, so by itself it cannot introduce or fix a security vulnerability. It may be related to earlier work that hardened signature parsing, but the diff only contains tests.

Security candidatesign: disallow overlong der encodings and zero r or s valuesby Jon Griffiths · e7894ee6 · Jul 31, 2026 · 1 fileMessage 85 · StrongModerate 62Details
Commit message · Jon Griffiths

sign: disallow overlong der encodings and zero r or s values

libsecp will happily parse and return such signatures without error,
however they can never be valid (in the overlong case, because libsecp
internally sets R to zero). Reject them up-front when parsing rather
than failing when attempting to use them later.

85/100 · StrongMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Provides detailed explanatory context✓ Explains rationale or failure mode
Why it was queued
signing boundarysigning or wallet path
AI analysis · Moderate 62/100

This commit tightens signature validation in a cryptographic library. It now rejects malformed DER-encoded signatures that are longer than allowed, or where one of the signature numbers (R or S) is zero. Previously, the underlying secp256k1 library would accept these invalid forms silently, which could lead to later failures or unexpected behavior when the signatures are used in Bitcoin/Elements transactions.

Security candidatedescriptor: add derive_bip32_key to derive a given descriptor keyby Jon Griffiths · 00d26754 · Jul 26, 2026 · 11 filesMessage 73 · AdequateLow 33Details
Commit message · Jon Griffiths

descriptor: add derive_bip32_key to derive a given descriptor key

Make key fetching consistent by handling blinding keys in the key
lookup.

Mark slip77 node flags correctly so their key features are returned
correctly.

73/100 · AdequateMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Provides detailed explanatory context
Why it was queued
secret or key material
AI analysis · Low 33/100

This commit adds a new public API to libwally-core that lets users derive BIP32 keys directly from a parsed Bitcoin/Elements descriptor. It also fixes two consistency bugs in how descriptor keys are looked up: it now correctly routes requests for the special 'blinding key' index, and it correctly marks SLIP77 blinding key nodes so callers can tell what kind of key they are getting. There is no direct evidence in the commit that these changes fix an exploitable vulnerability; they appear to be correctness and API-completeness improvements.

AI review queuedbuild(deps-dev): bump fast-uri from 3.1.2 to 3.1.4 in /src/wasm_packageby dependabot[bot] · c25fc5fd · Jul 25, 2026 · 1 fileMessage 93 · StrongInformational 13Details
Commit message · dependabot[bot]

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

Bumps [fast-uri](https://github.com/fastify/fast-uri) from 3.1.2 to 3.1.4.
- [Release notes](https://github.com/fastify/fast-uri/releases)
- [Commits](https://github.com/fastify/fast-uri/compare/v3.1.2...v3.1.4)

---
updated-dependencies:
- dependency-name: fast-uri
dependency-version: 3.1.4
dependency-type: indirect
...

Signed-off-by: dependabot[bot] <support@github.com>

93/100 · StrongMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Uses a recognizable type or scope✓ Provides detailed explanatory context✓ Links an issue, advisory, or supporting reference
Why it was queued
automated dependency-update discountsecond-pass: broader security terminology
AI analysis · Informational 13/100

This is an automated update by Dependabot that bumps the JavaScript helper library fast-uri from version 3.1.2 to 3.1.4 inside the WebAssembly packaging directory. It only changes a package-lock.json file and is marked as a development dependency, meaning it is not part of the core cryptographic library shipped to users. There is no direct evidence in the commit that this fixes a security problem in libwally-core itself, but dependency updates can sometimes address bugs or vulnerabilities in the helper library.

Lower-prioritydescriptor: add taproot (tapscript) descriptor supportby pythcoiner · 0d983134 · Jul 17, 2026 · 17 filesMessage 83 · StrongTriage 0Details
Commit message · pythcoiner

descriptor: add taproot (tapscript) descriptor support

Adds tr() descriptors with script paths: the WALLY_LEAF_VERSION_TAPSCRIPT
constant, multi_a/sortedmulti_a tapscript fragments, taptree parsing with
BIP-341 merkle-root/leaf hashing, tr() address derivation including the
key-path tweak, and the taproot tree/leaf/control-block/key-enumeration
accessor APIs. Includes the C and Python descriptor test suites.

Co-authored-by: odudex <odudex@proton.me>
Co-authored-by: Jon Griffiths <jon_p_griffiths@yahoo.com>

83/100 · StrongMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Provides detailed explanatory context✓ Mentions testing or verification
AI review queuedBump version to 1.5.6by Jon Griffiths · 0c41f38f · Jul 11, 2026 · 9 filesMessage 38 · OpaqueInformational 15Details
Commit message · Jon Griffiths

Bump version to 1.5.6

38/100 · OpaqueMessage clarity
✓ Subject identifies a change✓ Names a concrete action or component! No meaningful explanatory body
Why it was queued
second-pass: opaque commit message
AI analysis · Informational 15/100

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

Lower-priorityupdate CHANGES.md for release 1.5.6by Jon Griffiths · 9947fc4e · Jul 11, 2026 · 1 fileMessage 45 · ThinInformational 15Details
Commit message · Jon Griffiths

update CHANGES.md for release 1.5.6

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.6 release. It does not change any source code, build scripts, tests, or documentation that affects how the software runs. The changelog entries describe fixes that were already made in earlier commits, including a security-relevant fix about preventing memory leaks via extended CPU registers on x86. Because this commit itself only edits the changelog, it introduces no new security risk and requires no action.

Lower-prioritydescriptor: reject nested expressions with unconsumed trailing inputby odudex · f23a1c97 · Jul 11, 2026 · 2 filesMessage 73 · AdequateModerate 53Details
Commit message · odudex

descriptor: reject nested expressions with unconsumed trailing input

A nested expression was delimited only by its enclosing brackets and
commas, so trailing characters after it were silently ignored, e.g.
wsh(pk(KEY)xyz) parsed as wsh(pk(KEY)).

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

This commit fixes a parsing bug in libwally-core's Bitcoin descriptor handling. Previously, if extra characters appeared after a valid nested expression inside parentheses, the parser silently ignored them. For example, 'wsh(pk(KEY)xyz)' was accepted as if it were just 'wsh(pk(KEY))'. This could let malformed or attacker-crafted descriptors be misinterpreted, potentially causing two users or programs to disagree about what a wallet script actually is. The fix makes the parser reject such trailing garbage.

Lower-prioritydescriptor: require type B for the top level miniscript in sh()/wsh()by odudex · 6f656241 · Jul 11, 2026 · 2 filesMessage 50 · ThinModerate 59Details
Commit message · odudex

descriptor: require type B for the top level miniscript in sh()/wsh()

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

This commit tightens validation for Bitcoin descriptors that wrap a miniscript inside sh() (pay-to-script-hash) or wsh() (pay-to-witness-script-hash). Previously, the library accepted any miniscript fragment as the top-level child, even fragments that are not valid standalone scripts (for example, a fragment that only pushes a public key or verifies a signature but leaves a value on the stack). The change now rejects those malformed descriptors before they can be used to create addresses or transactions. The risk is that an attacker or buggy wallet could trick a user into accepting a descriptor whose script does not behave as expected, potentially making funds unspendable or enabling unexpected spending conditions.

AI review queuedBump version to 1.5.5by Jon Griffiths · 78499f00 · Jul 9, 2026 · 9 filesMessage 38 · OpaqueInformational 15Details
Commit message · Jon Griffiths

Bump version to 1.5.5

38/100 · OpaqueMessage clarity
✓ Subject identifies a change✓ Names a concrete action or component! No meaningful explanatory body
Why it was queued
second-pass: opaque commit message
AI analysis · Informational 15/100

This commit is a routine version bump from 1.5.4 to 1.5.5 across build files, documentation, and package metadata. It changes only version strings and the build version constant; no code logic is modified.

Lower-priorityupdate CHANGES.md for release 1.5.5by Jon Griffiths · d0ac03ba · Jul 9, 2026 · 1 fileMessage 45 · ThinLow 44Details
Commit message · Jon Griffiths

update CHANGES.md for release 1.5.5

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 · Low 44/100

This commit is just a changelog update for libwally-core version 1.5.5. It mentions that the release 'de-optimizes some memcpy calls on x86 to prevent leaks via extended registers.' That wording suggests a security-sensitive fix, but the actual code change is not shown in this commit—only the release note is. So we can flag the topic as potentially security-relevant, but we cannot verify the fix from this commit alone.

Lower-priorityci: re-enable clear testsby Jon Griffiths · 1009497b · Jul 9, 2026 · 1 fileMessage 67 · AdequateInformational 15Details
Commit message · Jon Griffiths

ci: re-enable clear tests

67/100 · AdequateMessage clarity
✓ 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 changes the project's continuous integration (CI) configuration. It re-enables a set of tests called 'clear tests' that were previously disabled in automated build pipelines, and adds a compiler warning suppression for an amalgamation compile test. There is no change to the actual library code that users run, so this commit does not introduce or fix a security vulnerability in the software itself.

Security candidateinternal: avoid potential info leaks via sse/avx registersby Jon Griffiths · 91b3b6d6 · Jul 9, 2026 · 10 filesMessage 73 · AdequateModerate 68Details
Commit message · Jon Griffiths

internal: avoid potential info leaks via sse/avx registers

In particular when built as a shared library, calls through the PLT
spill these registers onto the stack.

Thanks to @pythcoiner <pythcoiner@proton.me> for identifying the
leak cause and suggesting a fix.

73/100 · AdequateMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Provides detailed explanatory context
Why it was queued
cryptography-sensitive path
AI analysis · Moderate 68/100

This commit fixes a potential information leak in a cryptocurrency wallet library. When the library is built as a shared library on x86/x86_64 systems, optimized memory-copy functions can leave secret data (private keys, seed phrases, chain codes) inside special CPU registers (SSE/AVX). If the program then makes a call through the dynamic linker before those registers are reused, the CPU spills the register contents onto the stack, where they may remain uncleared. The patch replaces many ordinary memory copies with a simple, unoptimized byte-by-byte copy function for sensitive data, preventing the data from being left in those registers. The commit message explicitly calls this an 'info leak' and thanks an external contributor for finding the cause and suggesting the fix.

Lower-prioritytests: add more test_clear testsby pythcoiner · 9d05ca17 · Jul 9, 2026 · 1 fileMessage 55 · ThinInformational 12Details
Commit message · pythcoiner

tests: add more test_clear tests

55/100 · ThinMessage clarity
✓ Descriptive subject✓ Names a concrete action or component✓ Mentions testing or verification! No meaningful explanatory body
AI analysis · Informational 12/100

This commit only adds new test cases to an existing test file. It does not change any production code, fix a bug, or alter behavior. The tests check whether sensitive secret bytes are cleared from the call stack after using certain cryptographic functions, which is a defensive security practice, but the commit itself is purely a testing improvement.

Lower-priorityinternal: mark internal functions as hidden visibility when possibleby Jon Griffiths · 2d36c91d · Jul 9, 2026 · 5 filesMessage 73 · AdequateLow 47Details
Commit message · Jon Griffiths

internal: mark internal functions as hidden visibility when possible

Even when building with -fvisibility=hidden, some internal functions
(those that aren't static and thus provably limited to a single
compilation unit) are not marked hidden. As a result, calls to them from
within the library are routed through the PLT. This can result in
register data containing secrets/partial secrets being spilled to the
stack.

Mark such internal functions as hidden so internal calls to them avoid
the PLT call mechanism.

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

This change is a hardening patch for a cryptocurrency wallet library. It tells the compiler to keep certain internal helper functions private to the library, so calls to them stay inside the library instead of going through an external lookup table (the PLT). The commit message says the old route could cause CPU register values containing secret key material to be temporarily saved to the stack, where they might be more easily exposed in a crash dump or memory leak. The patch reduces that risk but does not by itself fix a specific, independently reported vulnerability.

Lower-prioritydescriptor: avoid iterating multisig nodes twiceby Jon Griffiths · 017d76eb · Jul 6, 2026 · 1 fileMessage 68 · AdequateInformational 12Details
Commit message · Jon Griffiths

descriptor: avoid iterating multisig nodes twice

node_get_child_count() iterates all keys which we then immediately do
again below. Count the children as we iterate checking the keys instead.

Co-authored-by: odudex <odudex@proton.me>

68/100 · AdequateMessage clarity
✓ Descriptive subject✓ Names a concrete action or component✓ Provides detailed explanatory context
AI analysis · Informational 12/100

This is a small code cleanup in how a Bitcoin descriptor function counts child nodes. It removes a redundant loop and counts children while already checking them. There is no visible security bug being fixed—just an efficiency and clarity improvement.

AI review queuedBump version to 1.5.4by Jon Griffiths · c5591834 · Jun 16, 2026 · 9 filesMessage 38 · OpaqueInformational 15Details
Commit message · Jon Griffiths

Bump version to 1.5.4

38/100 · OpaqueMessage clarity
✓ Subject identifies a change✓ Names a concrete action or component! No meaningful explanatory body
Why it was queued
second-pass: opaque commit message
AI analysis · Informational 15/100

This commit is a routine version bump from 1.5.3 to 1.5.4 across build files, documentation, and package metadata. It changes only version strings and constants; no code logic is modified. There is no security-relevant content in the diff.