Continuous public-repository analysis

Open source.
Not open secrets.

We watch what security-critical projects change—then translate the code into clear, independent intelligence anyone can understand.

24Projects watched
17539Commits captured
17132AI analyses
88High-risk findings · 30d
The watch feed

Changes worth understanding

AI analysis is published as generated. Community notes appear after human validation.

17132 analyses
Highest risk·RSS
Informational 15 AI analysisMessage 57 · Thin
EP Elements ProjectCore Lightning BitcoinLightning Network

CI: Add debug and upload artifacts on failure

This commit only improves GitHub Actions CI debugging. It adds extra logging and uploads test artifacts when a CI job fails. There is no change to the Core Lightning software itself, no user-facing behavior change, and no security issue.

4aae26dcby ShahanaFarooqui+46−01 file
No security note in commit
Informational 12 AI analysisMessage 78 · Adequate
BC Bitcoin Corelibsecp256k1 BitcoinCryptographic libraries

tests: add constant time tests

This commit only adds new test code. It extends the project's constant-time test suite to also exercise the silent payments module, ensuring that secret key material is not accidentally leaked through timing side channels during those oper…

Adds constant-time (side-channel) test coverage for the silent payments moduleUses memory-secret marking macros (SECP256K1_CHECKMEM_UNDEFINE/DEFINE) to detect secret-dependent branchesNo functional or cryptographic code changes
936907b0by josibake+78−01 file
No security note in commit
Informational 15 AI analysisMessage 70 · Adequate
BC Bitcoin Corelibsecp256k1 BitcoinCryptographic libraries

tests: add sha256 tag test

This commit only adds a new test that checks whether certain SHA-256 'tagged' hash initialization functions used in silent payments produce the correct internal hash state. It does not change any production code, cryptographic logic, or be…

4f7a578dby josibake+24−01 file
No security note in commit
Informational 15 AI analysisMessage 47 · Thin
BC Bitcoin Corelibsecp256k1 BitcoinCryptographic libraries

ci: enable silentpayments module

This commit only changes the project's continuous integration (CI) configuration. It adds the new 'silentpayments' module to the list of optional modules that are built and tested automatically. There are no changes to the actual cryptogra…

f27a2968by Sebastian Falbesoner+28−162 files
No security note in commit
Informational 15 AI analysisMessage 40 · Thin
BC Bitcoin Corelibsecp256k1 BitcoinCryptographic libraries

docs: update README

This commit only updates the README documentation to mention a new optional feature (Silent Payments, BIP-352) and point to an example file. No code, build scripts, or cryptographic logic was changed. There is no security issue here.

7e4b313cby josibake+2−01 file
No security note in commit
Informational 15 AI analysisMessage 73 · Adequate
BC Bitcoin Corelibsecp256k1 BitcoinCryptographic libraries

silentpayments: skip slow benchmarks for low iters count (<= 2)

This change only adjusts benchmark tests for a new Bitcoin privacy feature (silent payments). It skips some slow benchmark cases when tests are run with very low iteration counts, such as in automated CI runs. It does not change any produc…

4aa16704by Sebastian Falbesoner+12−21 file
No security note in commit
Informational 15 AI analysisMessage 83 · Strong
BC Bitcoin Corelibsecp256k1 BitcoinCryptographic libraries

tests: add BIP-352 test vectors

This commit only adds test data and test infrastructure for the BIP-352 silent payments feature. It does not change any production cryptographic code, so it cannot introduce a runtime security vulnerability on its own.

b608a9d9by josibake+11046−06 files
No security note in commit
Informational 15 AI analysisMessage 62 · Adequate
BC Bitcoin Corelibsecp256k1 BitcoinCryptographic libraries

build: add skeleton for new silentpayments (BIP352) module

This commit is purely a build-system and header-file skeleton for a new Silent Payments (BIP352) module. It adds configuration options, dependency checks, and empty placeholder files, but contains no actual cryptographic code or implementa…

a93e696aby Sebastian Falbesoner+83−08 files
No security note in commit
Informational 15 AI analysisMessage 41 · Thin
BC Bitcoin Corelibsecp256k1 BitcoinCryptographic libraries

silentpayments: sending

This commit adds a new feature to the secp256k1 cryptographic library: the sender-side logic for Bitcoin Silent Payments (BIP352). It lets a wallet create special one-time payment addresses for recipients without revealing which recipient …

New feature implementation for BIP352 Silent Payments sender sideExtensive input validation (ARG_CHECK) and test coverage for malformed keys and bad argumentsSensitive intermediate values (shared secrets, scalars) are explicitly cleared
b30ea3ebby josibake+719−14 files
No security note in commit
Informational 15 AI analysisMessage 68 · Adequate
BC Bitcoin Corelibsecp256k1 BitcoinCryptographic libraries

silentpayments: recipient label support

This commit adds new public API functions to the silentpayments module of libsecp256k1 to support recipient-side labels for BIP352 silent payments. It is a feature addition, not a security fix or vulnerability patch. There is no evidence i…

c83b6783by Sebastian Falbesoner+302−13 files
No security note in commit
Informational 15 AI analysisMessage 70 · Adequate
BC Bitcoin Corelibsecp256k1 BitcoinCryptographic libraries

silentpayments: receiving

This commit adds new code for receiving BIP352 Silent Payments in the libsecp256k1 cryptography library. It introduces functions that let a wallet scan a Bitcoin transaction to find outputs sent to it and compute the secret tweaks needed t…

New feature code, not a security patchExtensive input validation and NULL checks addedSensitive scalars cleared after use (shared_secret, scan_key_scalar, t_k_scalar)
d72a7432by josibake+632−13 files
No security note in commit
01
Why commit watching?

Security should leave a paper trail.

A quiet fix may be responsible caution—or it may leave users unaware that their assets were ever at risk. CommitWatch preserves the evidence, adds context, and tracks whether vendors disclose, acknowledge, and learn.

Why we built this