Signed First, Source Later

• The temporary trust swap
• Why the source stayed shut
• AI changed the reporting tempo
• What sovereignty looks like during the embargo
• Distinct from the model patch clock
• What to do before the source opens

§The temporary trust swap

Self-custody Lightning usually sells a clean bargain: run the daemon you can rebuild, verify the build, keep the keys. That bargain paused for two weeks.

On August 28, Core Lightning shipped 26.06.7 as signed binaries and said the matching source would stay closed until September 11. The point release fixes confirmed vulnerabilities reported over the prior three weeks. Older releases are unsupported. If you cannot upgrade yet, restart with --offline — not power-off — so the node can still watch the chain for cheating while it stops taking peer messages.

That is not a press release detail. It is a temporary rewrite of what “verify” means for operators who hold channel funds on their own hardware.

§Why the source stayed shut

A patch names the code it changes. Publishing that diff while most nodes still run the vulnerable build hands a working map to anyone who can read it faster than operators can upgrade. Withholding the source for fourteen days after the binary ships is an old responsible-disclosure move applied to a network where the attack surface is a long-lived process that peers can poke.

The maintainers are explicit about the close: once the source lands, rebuild it and confirm the result matches the binary you have been running. Signature verification is the bridge. Rebuild verification is the landing.

§AI changed the reporting tempo

The reports did not arrive as a single tidy CVE. They arrived as a surge — community researchers, tooling, and AI-assisted review in the mix — over a short stretch of August. Maintainers thanked a long list of reporters and said they will keep embracing AI-assisted review going forward.

That tempo is the operator lesson. Vulnerability discovery no longer waits on a few humans reading C by hand. When report volume rises, the window between “confirmed” and “safe to publish the diff” compresses, and the binary-first / source-later pattern becomes more common, not less. Lightning nodes are not cold wallets. They speak to peers. An unpatched daemon is not a theoretical scoreboard row.

§What sovereignty looks like during the embargo

For those fourteen days, a careful operator still has work that is not theater.

Verify the signatures on the published tarballs. Install 26.06.7 and restart. If you cannot upgrade immediately, take the --offline path rather than inventing a half-shutdown. Track whether you installed from the correct signed artifacts, not from a placeholder tag or an auto-generated archive that does not match the release notice. When the source opens on September 11, do the rebuild check — or accept that you ran on signature trust and document that choice.

None of that is as satisfying as git clone and a clean make. It is still self-custody. Self-custody includes the days when the only honest audit surface is the signature and the release process, not the tree.

§Distinct from the model patch clock

There is a parallel story in AI labs this month: models that find flaws inside closed evals, and a public that waits on patches it cannot yet verify. That story is about discovery inside a score. This one is about operators who already run the production surface.

The interesting object here is not that software has bugs. It is that Bitcoin-adjacent infrastructure now routinely forces a short, named interval where rebuild-from-source is unavailable by design, and the rational move is still to upgrade. Sovereignty did not disappear. It changed shape for two weeks: from “I can recompile this” to “I can verify who signed this, and I will recompile when the embargo lifts.”

§What to do before the source opens

If you run Core Lightning, treat September 11 as a calendar event, not a blog footnote. Be on 26.06.7 before the diff is public. Keep the signed binary you installed so the rebuild comparison is possible. Prefer official signed artifacts over convenience packages until you have confirmed they contain the same bits. And update your mental model: AI-accelerated reporting means more of these windows, not fewer.

The network does not pause for your audit calendar. The operators who stay online through the next surge will be the ones who practiced signature trust without confusing it for a permanent substitute for source.