←
Project Loupe43 posts
Project Loupe avatar

Project Loupe

@ProjectLoupe

An AI-powered vulnerability scanner for open-source bitcoin projects. Discord: discord.gg/xDZzSPUrTa

◷ Joined May 2026▧ 2 Photos and videos
Stratum V2 avatar
⟳ Project Loupe retweeted
Stratum V2@StratumV2·Nov 5

SV2 Apps add Bitcoin Core v32 support and block submission over IPC, and continue addressing @ProjectLoupe findings across Pool, JDS, JDC and Translator Proxy. Protocol library highlights include hardening of buffer_sv2, codec_sv2 and framing_sv2, message field renames to match the spec, and support for application-supplied jobs in channels_sv2. All changed published crates introduce breaking changes except noise_sv2, so downstream consumers should review the release notes when upgrading. SV2 UI adds experimental Telegram notifications, multiple custom pools, clearer fallback pool status, and improvements to onboarding, logs and recovery. Setup now supports Bitcoin Core v32. Findings from @ProjectLoupe continue to guide security improvements across the stack. Thank you to the Loupe team and everyone helping turn those findings into fixes! This milestone introduces our SV2 interoperability project, a new effort to test protocol compatibility across different SV2 implementations. The goal is to catch interoperability issues early, make it easier for implementers to validate their software against the spec, and help ensure different SV2 implementations work reliably together. Contributions and feedback are welcome!

Post attachment
instagibbs avatar
⟳ Project Loupe retweeted
instagibbs@theinstagibbs·Oct 28

Post attachment
TFTC@TFTC21Oct 28

Mike Schmidt broke down Bitcoin Core v32.1 and surfaced something important: Core updated its disclosure policy specifically because LLM tools are making bugs easier to find. "Core's recently updated policy fast-tracks the disclosure of easily discoverable vulnerabilities. LLM-assisted security scans helped motivate the change." All three vulnerabilities disclosed today were found by Project Loupe, an AI-powered scanner built at Spiral. If defenders can find them with LLMs, attackers can too. Beyond security, v32.1 packs 715 merged PRs from 111 authors. Fee estimation now factors in live mempool conditions. Initial sync is 1.2-3x faster. The libevent dependency is fully replaced with in-house code. Stratum v2 keeps advancing. The infrastructure keeps getting stronger.

Project Loupe avatar
Project Loupe@ProjectLoupe·Oct 29

The technology is moving fast. Responsible disclosure needs to move with it.

Project Loupe has entered the chat Finding the 3 'easily discoverable' vulnerabilities in Bitcoin Core v32.1 Although @ProjectLoupe was actually ahead of the curve, announcing they would be doing LLM scans back in May before the ColdCard and other hacks: "Loupe’s ultimate goal is to find vulnerabilities, report them, and see them eliminated, making bitcoin safer and bitcoin holders more secure." Great vision by @moneyball and team x.com/bitschmidty/status/211…

Project Loupe avatar
Project Loupe@ProjectLoupe·Oct 29

🥾🪳

Great work by @ProjectLoupe and @L0RINC for finding these bugs! While they are vulnerabilities, they are low / medium severity and the Bitcoin protocol is resilient. No loss of funds possible from these issues. A learning from this is that some of these were found earlier than reported within the Red Team, but the initial findings did not identify the full blast radius so they were not immediately passed along to the security list. Thank you to all of the Bitcoin Core developers who work hard building on Bitcoin so it can be the best money ever!

calle avatar
⟳ Project Loupe retweeted
calle@callebtc·Oct 20

project loupe is an absolute treasure for the bitcoin ecosystem! thank you for the reviews, incredibly valuable for the Cashu project.

Project Loupe avatar
Project Loupe@ProjectLoupe·Oct 15

We file our findings privately. Loupe only shows up in public if a maintainer credits us, which many have: ✅ 754 commits, PRs, & release notes across 23 projects reference Loupe ✅ 610 distinct findings cited by issue number ✅ 132 merged PRs name the finding they fixed

Project Loupe avatar
Project Loupe@ProjectLoupe·Oct 8

🕳️ Also from a Loupe report: @theinstagibbs mapped out how a peer sending a same-txid witness variant can stall honest fee-bumping packages, and is closing those holes across two PRs. That work continues. github.com/bitcoin/bitcoin/p…

Project Loupe avatar
Project Loupe@ProjectLoupe·Oct 8

📦 In review: a package evicted right after acceptance landed in the reject filter until the next block, so a higher-fee child couldn't bump it back in. Loupe and the Bitcoin Red Team found it, @theinstagibbs fixed it. github.com/bitcoin/bitcoin/p…

Project Loupe avatar
Project Loupe@ProjectLoupe·Oct 8

🏎️ A data race: the transaction download manager shared a non-thread-safe RNG with message processing, and a block connecting at the wrong moment could use it from two threads at once. Loupe found it and Crypt-iQ fixed it. github.com/bitcoin/bitcoin/p…

Project Loupe avatar
Project Loupe@ProjectLoupe·Oct 8

🚢 On Windows, the RPC listener got lazy and didn't reserve its port exclusively. Another local process could bind to the same port, catch a connection, and capture wallet-controlling RPC credentials. Loupe found it and hodlinator fixed it. github.com/bitcoin/bitcoin/p…

Project Loupe avatar
Project Loupe@ProjectLoupe·Oct 8

🤫 First up, a Silent Payments fix. Currently, a 3rd party could alter a P2PKH scriptSig so the wallet extracted the wrong pubkey while the spend stayed consensus-valid. Not good. Loupe reported it and @theStack fixed it. No SP implementations were harmed. github.com/bitcoin/bitcoin/p…

Project Loupe avatar
Project Loupe@ProjectLoupe·Oct 8

Loupe findings have been landing in Bitcoin Core. During this cycle, five PRs landed: three have been merged, two are under review. Below is a thread on what each one caught and which Core dev implemented which fix.