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.

Security candidatepsbt: allow unknowns (global, input and output) to have empty values.by Jon Griffiths · 10670278 · Nov 17, 2026 · 3 filesMessage 75 · AdequateLow 40Details
Commit message · Jon Griffiths

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

Thanks to @bitcoisas for reporting and providing the test case.

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 boundarysigning or wallet path
AI analysis · Low 40/100

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 instead of a proper empty value. This could lead to crashes or memory corruption when the PSBT is later processed. The fix ensures empty unknown values are stored as NULL. A test case with an empty unknown output field was added.

Security candidatepsbt: Copy the PSET genesis blockhashby kkdao · 4b64af46 · Nov 11, 2026 · 1 fileMessage 73 · AdequateLow 44Details
Commit message · kkdao

psbt: Copy the PSET genesis blockhash

wally_psbt_clone_alloc() and wally_psbt_combine() copied every global
PSET field except the genesis blockhash, so a cloned PSET serialized
without it and its taproot inputs could no longer be signed, as the
Elements taproot signature hash requires the genesis blockhash.

Copy it when the destination has none. A clone always takes it from
the source, and a combine keeps an existing value.

73/100 · AdequateMessage clarity
✓ Descriptive subject✓ Names a concrete action or component✓ Provides detailed explanatory context✓ Names security-relevant behavior explicitly
Why it was queued
signing boundarysigning or wallet path
AI analysis · Low 44/100

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 features. It is a correctness/data-loss bug rather than a direct theft-of-funds vulnerability, but it could cause signing failures or interoperability problems.

Security candidatepsbt: Refuse upgrading a v0 PSBT with no txby kkdao · e76b2304 · Nov 11, 2026 · 2 filesMessage 68 · AdequateModerate 60Details
Commit message · kkdao

psbt: Refuse upgrading a v0 PSBT with no tx

wally_psbt_set_version() upgrading a v0 PSBT to v2 read the version,
locktime, inputs and outputs from psbt->tx without checking it exists.
A v0 PSBT with no global tx is valid: wally_psbt_init_alloc() makes
one, and loose parsing accepts one, so set_version() on either
dereferenced NULL.

Refuse the upgrade with WALLY_EINVAL, as psbt_build_tx() and the other
v0 paths already do when there is no tx.

68/100 · AdequateMessage clarity
✓ Descriptive subject✓ Names a concrete action or component✓ Provides detailed explanatory context
Why it was queued
signing boundarysigning or wallet path
AI analysis · Moderate 60/100

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 data without first checking that the data existed. If the PSBT had no transaction attached, that pointer was NULL, causing the program to crash (NULL pointer dereference). The fix simply refuses the upgrade with an error when no transaction is present, matching how other parts of the code already handle the same situation.

Security candidatepsbt: Refuse v2 global tx under loose parsingby kkdao · 10f41d80 · Nov 8, 2026 · 3 filesMessage 73 · AdequateLow 45Details
Commit message · kkdao

psbt: Refuse v2 global tx under loose parsing

wally_psbt_from_bytes() with WALLY_PSBT_PARSE_FLAG_LOOSE accepted a v2
PSBT carrying PSBT_GLOBAL_UNSIGNED_TX if the tx key came before the
version key. psbt_set_global_tx() allocated the input and output arrays
for the tx, then the v2 path overwrote those pointers with new arrays,
leaking the old ones.

Refuse such a PSBT instead of freeing the arrays. A v2 PSBT with a tx
fails psbt_is_valid(), so it could not even be serialized, and the
reverse key order is already refused by psbt_set_global_tx(). The
signature-only PSBTs that loose parsing exists for never have a tx in
v2.

73/100 · AdequateMessage clarity
✓ Descriptive subject✓ Names a concrete action or component✓ Provides detailed explanatory context✓ Names security-relevant behavior explicitly
Why it was queued
signing boundarysigning or wallet path
AI analysis · Low 45/100

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 inputs/outputs, then overwrite those pointers, leaking the memory. The patch now rejects these invalid files outright. It does not appear to be a security-critical remote code execution or theft bug, but it is a correctness and denial-of-service hardening fix.

Security candidateAdd 1.6.0 upgrade advice to CHANGES.mdby kkdao · 7f8f89e8 · Nov 5, 2026 · 1 fileMessage 85 · StrongInformational 15Details
Commit message · kkdao

Add 1.6.0 upgrade advice to CHANGES.md

The published 1.6.0 release notes open by advising users to update as
soon as possible because the release carries important bug and
security fixes. CHANGES.md left that sentence out, so anyone reading
the changelog in the source tree or a packaged tarball misses it.

Copy the sentence into CHANGES.md so both match.

85/100 · StrongMessage clarity
✓ Descriptive subject✓ Names a concrete action or component✓ Provides detailed explanatory context✓ Explains rationale or failure mode✓ Names security-relevant behavior explicitly
Why it was queued
explicit security languagedocumentation-only discount
AI analysis · Informational 15/100

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, build scripts, or cryptographic logic were changed.

Security candidatepsbt: fix finalizing large P2SH and bare multisig inputsby odudex · cf8eb142 · Nov 4, 2026 · 2 filesMessage 78 · AdequateModerate 60Details
Commit message · odudex

psbt: fix finalizing large P2SH and bare multisig inputs

Legacy multisig scriptSigs were built in a WALLY_SCRIPTSIG_MAX_LEN
(520 byte) buffer, which is the limit for a single push, not for a
scriptSig. P2SH inputs needing more (e.g. 5-of-5, 4-of-7, 1-of-13)
were silently left unfinalized. Allocate the buffer instead.

Bare multisig scriptSigs also pushed the multisig script after the
signatures, which CHECKMULTISIG then took as a signature, making the
spend invalid. Only push the script for P2SH.

78/100 · AdequateMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Provides detailed explanatory context✓ Names security-relevant behavior explicitly
Why it was queued
signing boundarysigning or wallet path
AI analysis · Moderate 60/100

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 bare multisig transactions, the final script incorrectly included the whole redeem script as if it were another signature, making the spend invalid. The patch allocates a correctly sized buffer and only appends the redeem script for P2SH inputs.

Security candidatepsbt: disallow hybrid pubkeysby Jon Griffiths · 06fba283 · Oct 31, 2026 · 2 filesMessage 50 · ThinLow 47Details
Commit message · Jon Griffiths

psbt: disallow hybrid pubkeys

Modern txs should not be using hybrid pubkeys, so reject them outright.

50/100 · ThinMessage clarity
✓ Descriptive subject✓ Provides an explanatory body
Why it was queued
signing boundarysigning or wallet path
AI analysis · Low 47/100

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. The change swaps a lenient verifier for a strict one in four places where PSBT data is parsed, so malformed or non-standard keys are now refused rather than accepted.

Security candidateexpose ec_public_key_strict_verify to verify non-hybrid pubkeysby Jon Griffiths · e9ff9b8e · Oct 31, 2026 · 9 filesMessage 83 · StrongInformational 23Details
Commit message · Jon Griffiths

expose ec_public_key_strict_verify to verify non-hybrid pubkeys

In modern contexts we want to exclude hybrid keys (0x6/0x7 prefixed
uncompressed public keys). Expose this call to detect them.

83/100 · StrongMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Provides detailed explanatory context✓ Mentions testing or verification
Why it was queued
cryptography-sensitive pathsigning or wallet path
AI analysis · Informational 23/100

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 verification option. The change itself is defensive and not a vulnerability fix, though it may help downstream code reject hybrid keys that some modern protocols consider invalid.

Security candidatebip39: document that mnemonic/passphrase arguments require ascii/utf8 nfkdby Jon Griffiths · abbe03ce · Oct 30, 2026 · 1 fileMessage 50 · ThinInformational 15Details
Commit message · Jon Griffiths

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

50/100 · ThinMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component! No meaningful explanatory body
Why it was queued
secret or key materialaccess controlcryptography-sensitive path
AI analysis · Informational 15/100

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 was addressed.

Security candidatebip39: fail if the callers requested language is not foundby Jon Griffiths · 9f912ada · Oct 30, 2026 · 1 fileMessage 50 · ThinModerate 51Details
Commit message · Jon Griffiths

bip39: fail if the callers requested language is not found

Don't silently fall back to English.

50/100 · ThinMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component! No meaningful explanatory body
Why it was queued
secret or key materialcryptography-sensitive path
AI analysis · Moderate 51/100

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 the function return an error when the requested language is missing, and only default to English when no language is explicitly requested. This prevents silent mismatches between what the caller expects and what they get.

Security candidatesign: verify schnorr sigs after creationby Jon Griffiths · 4e3d596f · Oct 29, 2026 · 1 fileMessage 95 · StrongModerate 64Details
Commit message · Jon Griffiths

sign: verify schnorr sigs after creation

Unlike ECDSA, a corrupted schnorr sig may leak information about the
private key. Check the sig after creation to prevent this from ever
happening.

95/100 · StrongMessage clarity
✓ Descriptive subject✓ Names a concrete action or component✓ Provides detailed explanatory context✓ Explains rationale or failure mode✓ Mentions testing or verification✓ Names security-relevant behavior explicitly
Why it was queued
secret or key materialsigning or wallet path
AI analysis · Moderate 64/100

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 erased and not returned to the caller. This prevents a rare but real risk: a corrupted or faulty Schnorr signature could leak information about the private key.

Security candidatebip32: disallow paths with a leading m but without a following slashby Jon Griffiths · 7985c7c8 · Oct 28, 2026 · 2 filesMessage 50 · ThinLow 40Details
Commit message · Jon Griffiths

bip32: disallow paths with a leading m but without a following slash

50/100 · ThinMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component! No meaningful explanatory body
Why it was queued
secret or key materialcryptography-sensitive path
AI analysis · Low 40/100

This commit tightens how the library parses BIP32 key derivation paths. Previously, a string like 'm0' or 'm*' was accepted as if the 'm' were silently ignored, which could let an attacker trick a wallet into deriving keys from a different path than the user intended. The fix now rejects any path that starts with 'm' or 'M' but is not followed by a slash.

Security candidatedocs: update psbt docs to describe sighash behaviourby Jon Griffiths · 20386811 · Oct 27, 2026 · 1 fileMessage 62 · AdequateInformational 18Details
Commit message · Jon Griffiths

docs: update psbt docs to describe sighash behaviour

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
signing boundarysigning or wallet path
AI analysis · Informational 18/100

This commit only updates documentation comments in a header file. It adds notes explaining that PSBT signing functions use the sighash value already stored for each input, falling back to a default if none is set, and that callers should verify the sighash is acceptable before signing. No code behavior was changed.

Security candidatebip32: disallow repeated child numbers in multi-paths per BIP-389by Jon Griffiths · a9f766cd · Oct 27, 2026 · 2 filesMessage 50 · ThinLow 48Details
Commit message · Jon Griffiths

bip32: disallow repeated child numbers in multi-paths per BIP-389

Correct number of items limit to 255.

50/100 · ThinMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component! No meaningful explanatory body
Why it was queued
secret or key materialcryptography-sensitive path
AI analysis · Low 48/100

This commit tightens validation of Bitcoin descriptor multi-path expressions like <0;1;2>. Previously, the library accepted repeated child numbers (e.g., <0;0>) and allowed up to 255 entries by using >= instead of >. The change enforces BIP-389 by rejecting duplicate path components and correcting the limit to 255 distinct items. This is a standards-compliance and safety fix: duplicate paths could silently produce identical derived keys across branches, which may break wallet assumptions, enable fingerprinting, or cause downstream logic to treat different descriptor branches as the same.

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.

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.

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.

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.

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.

Security candidatedescriptor: support elements confidential wallet policiesby Jon Griffiths · 6bbe9eeb · May 6, 2026 · 1 fileMessage 78 · AdequateLow 27Details
Commit message · Jon Griffiths

descriptor: support elements confidential wallet policies

These are the same as existing wallet policies except that the blinding
key placeholder must be '@B`, which must be given first in the policy
key map when parsing.

This allows the blinding scheme and key to be presented separately from
the rest of the policy which will then be identical (modulo el-prefixes)
between elements and bitcoin for the same wallet structure.

This also allows the distinction between blinding keys and policy keys
to remain intact. Blinding keys are qualitatively different from
derivation keys; they may for example be a real pubkey, raw entropy,
and/or/in addition to an algorithm that operates on the result of the
policy for given derivation indices (in the case of deterministic
blinding). For these reasons blinding keys remain outside standard key
iteration in a parsed descriptor.

78/100 · AdequateMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Provides detailed explanatory context✓ Names security-relevant behavior explicitly
Why it was queued
entropy or randomness
AI analysis · Low 27/100

This commit adds support in libwally-core for a new Elements/Liquid confidential-wallet policy format. It lets wallet policies include a special '@B' blinding key placeholder, kept separate from ordinary derivation keys. The change is a feature addition with embedded validation rules; it does not appear to fix a known vulnerability, but it does touch sensitive descriptor-parsing code that handles cryptographic keys. There is no vendor statement that this is a security fix, and no independent researcher is credited.