Jan b retweeted
Update your node if you're on non-Linux!
A new medium severity advisory has been posted: bitcoincore.org/en/2026/10/2…
Jan b retweeted
Bitcoin Core is some of the most reviewed code in the world.
We were curious how our frontier AI model would handle it. Last month we ran 16 agents across 5 of the top models for a week to look for issues in Bitcoin Core v32.0rc1
Impressively, they surfaced two minor items - both now disclosed responsibly.
Agentic teams have been a huge unlock so far for our security efficiency. They're also remarkable to watch.
Jan b retweeted
Bitcoin Core v32.1: a deeper look
First, why no 32.0?
It was tagged on October 21 but never fully announced or released. A remotely triggerable TCP crash was reported on October 23 and 32.1 shipped on October 27 (yesterday) with that fix and two others.
I'll dig into the security updates, but this release also represents months of testing, maintenance, and work to make Bitcoin easier to verify and use.
What went into these v32.1 changes and what do Bitcoin users get from them?
Jan b retweeted
After a drawn out 32.x release cycle, we’ve shipped 32.1. v32.0 was tagged, but not fully announced/released, and after this last-minute discovery: bitcoincore.org/en/2026/10/2… we decided to ship v32.1, which fixes this bug, along with others (below) and includes other minor backports.
Bitcoin Core v32.1 was released!
It is available from: bitcoincore.org/en/download/
Release notes: bitcoincore.org/en/releases/…
Jan b retweeted
Bitcoin Core v32.1 was released!
It is available from: bitcoincore.org/en/download/
Release notes: bitcoincore.org/en/releases/…
Jan b retweeted
Bitcoin Core is tweaking its vulnerability disclosure policy.
groups.google.com/g/bitcoind…
Jan b retweeted
Brilliant work from my colleagues on FRT and Theorem on using Claude to scale formal verification methods on real world software
anthropic.com/research/forma…
Jan b retweeted
An update to Bitcoin Core's security policy
via @darosior on the Bitcoin-Dev mailing list
Jan b retweeted
Fun fact: when building Bitcoin Core’s bitcoind on modern systems, the x86_64 build compiles 10 more source files than the arm64 build.
Jan b retweeted
bitcoin 0.1
i rebuilt satoshi's 2009 bitcoin.exe byte for byte!
afaik nobody has been able to perfectly recreate the executable published in 2009 from source, because we didn't know the exact build environment that was used.
using opus 5.5, i reverse-engineered satoshi's build machine from the binary.
it now outputs an exe with the exact same sha256 as the 2009 release!
Jan b retweeted
CLAUDE FOUND THE SEEDS
anthropic.com/research/ecdsa…
Jan b retweeted
Happy to announce that we rebooted the nix-bitcoin project as bitcoinix
Join all the declarative fun here: github.com/bitcoinix/bitcoin…
Jan b retweeted
A new release candidate of Bitcoin Core, v32.0rc4, is available for testing.
This is a new major release, and follows v31.1.
Work-in-progress release notes are here: github.com/bitcoin-core/bitc…
Binaries are available here: bitcoincore.org/bin/bitcoin-…
Jan b retweeted
A new release candidate of Bitcoin Core, v32.0rc3, is available for testing.
This is a new major release, and follows v31.1.
Work-in-progress release notes are here: github.com/bitcoin-core/bitc…
Binaries are available here: bitcoincore.org/bin/bitcoin-…
Jan b retweeted
Ahmet Kurt (@startimeahmet) and Jan B (@_jan__b) joined Optech to discuss Newsletter #424:
News
● Proposal for a post-quantum Lightning Network (1:10)
Selected Q&A from Bitcoin Stack Exchange
● What would be a drawback if sum instead of SHA256 of amounts was used in the taproot signature message? (36:18)
● Post-BIP110 fork is it necessary to resync from block 0? (39:32)
● Can a Bitcoin node build a partial UTXO set from only the most recent blocks and use it to validate new transactions? (42:16)
Releases and release candidates
● Bitcoin Core 32.0rc2 (21:13)
● Core Lightning 26.06.8 (45:36)
● LDK v0.3-rc2 (47:15)
Notable code and documentation changes
● Bitcoin Core #34566 (51:31)
● BIPs #1951 (54:14)
● BIPs #2224 (57:45)
● Core Lightning #9507 (1:02:00)
● Core Lightning #9508 (1:07:35)
● Core Lightning #9509 (1:12:02)
● Core Lightning #9510 (1:16:03)
● Core Lightning #9513 (1:20:01)
● LND #11198 (1:21:47)
● LND #11146 (1:24:15)
● LND #11132 (1:27:20)
Jan b retweeted
‼️ just got a pretty smart github OAuth phishing/ATO attempt on my personal account.
attacker created a repo named after my github username, opened an issue mentioning me with a fake account-access alert, which triggered a real email from [email protected].
“This wasn’t me” → attacker-controlled GitHub Pages → real github.com OAuth consent page for an app called “profile security settings”, asking for public/private repo access + permission to update GitHub Actions workflow files.
no fake github login page. the email is github, the auth page is github. the malicious part is the OAuth app + redirect flow.
the page is just an obfuscated redirector, while the OAuth callback forwards the returned code/state to the same backend: github.com/api6268/code-839c…
also caught two other username-specific phishing issues from the same github account before they disappeared.
some indicators:
issue account: 6119f4f
OAuth app: profile security settings
consent: Authorize request-6286
landing: api6268[.]github[.]io/code-839c74ee/
related landing: api25cd[.]github[.]io/account-13e95c92/
callback: request-6286[.]github[.]io
backend: gitmain[.]serveblog[.]net
route ID: 9e52a992
