The latest wave of grants from our General Fund, supporting 21 open source projects across the Bitcoin ecosystem.
opensats.org/blog/21-grants-…
ziggie retweeted
While there's no RCE PoC yet for it, CVE-2026-99288 (NoisyTCP) looks *real* nasty. Similar class of bug as CVE-2026-98432 (the not-MPTCP bug) but their PoC doesn't require MPTCP at all. Patch your servers ASAP.
“TollGate is basically a protocol to add a toll booth to a router, just like the ones on the highway. When you connect to it, it tells you its price, and you pay with ecash.”
opensats.org/blog/developer-…
ziggie retweeted
Today we're announcing pi402!
Pay for AI inference directly with your coding agent. Instant on Lightning. No accounts, API keys, or cards needed.
Inference 🤝 Bitcoin
Learn more: pi402.tech
ziggie retweeted
announcing pi402: an L402+MPP inference stack built on Pi and Aperture 🍰⚡️🤖
lightning.engineering/posts/…
w/ pi402, agents can dynamically purchase inference with Bitcoin, powered by the Lightning Network, enabling instant low cost streaming payments
the stack is fully open source w/ three key components:
pi-402 (github.com/lightninglabs/pi-…):
* a @pidotdev extension that embeds Wavelength (wavelength.lightning.enginee…) via a WASM to handle L402+MPP negotiation
lightmeter (github.com/lightninglabs/lig…):
* a companion daemon to Aperture that handles the per-token (sats/token) metering, model pricing, and native MPP session channel accounting
aperture (github.com/lightninglabs/ape…):
* our L402+MPP reverse proxy that can be put in front of any existing inference endpoint to upgrade it to a Bitcoin metered instance
try out my live endpoint today at: pi402.roasbeef.computer/
here I'm hosting deepseek-v4-1-flash, selling inference at 1 sat per 500 tokens (1k sat per 500k tokens)
Today we're announcing pi402!
Pay for AI inference directly with your coding agent. Instant on Lightning. No accounts, API keys, or cards needed.
Inference 🤝 Bitcoin
Learn more: pi402.tech
ziggie retweeted
lnd v0.21.8+v0.20.8 have been released!
⚡️ github.com/lightningnetwork/…
github.com/lightningnetwork/…
⚡️
this release contains a number of important bug fixes, p2p stability improvements, on-chain sweeping improvements, and more!
as usual we recommend that all users update 🛡️
ziggie retweeted
To every developer who's stood watch over BTC/LN, past and present, inside project teams and out: thank you. You rarely get credit for the attacks you've prevented. LND v0.21.8-beta is the latest tag, so please take a minute to make sure you're running it: github.com/lightningnetwork/…
ziggie retweeted
Locking down LND:
- Don’t enable any non-standard features you won’t use
- Keep routing and app server nodes separate
- Make the app one private: no public or peer-opened channels
- Always upgrade to the latest
- Hot wallet? Only the BTC you need
- Watch force closes like a hawk
⚠️⚠️ All LNbits users should stop their LNbits servers IMMEDIATELY. ⚠️⚠️
Please forward this announcement.
Following a wave of attacks, we have a number of security patches to push. Until then, it's better to err on the side of caution. 🙏
Updates to follow soon.
ziggie retweeted
Easy autoloop in Lightning Loop:
- Set a hot wallet limit for your node
- Go over it and all excess funds go straight out to cold storage
- The most you could lose stays capped at the limit
If you're an exchange or a merchant receiving funds over LN, use this or something like it
ziggie retweeted
Start building with Wavelength:
wavelength.lightning.enginee…
ziggie retweeted
Der Widerstand gegen DAC8 wächst!
Jetzt geht man auch in Österreich juristisch gegen die umstrittene EU-Datensammlung bei Bitcoin-Nutzern vor. 🇦🇹
Mehr dazu bei @bitcoin_at und in diesem Artikel. ⬇️
blocktrainer.de/blog/weitere…
ziggie retweeted
Shout out to the public routing nodes of the Lightning Network. The real ones.
They protect our privacy.
They keep the network resilient.
They put their own money on the line.
We need more of them, especially independent operators. Let's make life easier for them going forward.
ziggie retweeted
Please note that updating after the fact is not enough.
Treat the entire machine as compromised.
📢 Our incident response investigation identified an attack vector targeting instances running versions 2.4.1 (Jul 23, 2026) or older.
We have no credible reports of hot wallet drains for users running the latest 2.4.7 release. We again urge everyone to keep their BTCPay Server updated.
If you were impacted, please send all details and logs to [email protected]
ziggie retweeted
📢 Our incident response investigation identified an attack vector targeting instances running versions 2.4.1 (Jul 23, 2026) or older.
We have no credible reports of hot wallet drains for users running the latest 2.4.7 release. We again urge everyone to keep their BTCPay Server updated.
If you were impacted, please send all details and logs to [email protected]
ziggie retweeted
Not a drill: shut down your BTCPay Server if you have a hot wallet.
Appreciate the reposts 🙏
ziggie retweeted
Update on my part: Our public servers were not attacked (on 2.4.7), it seems reports are on before 2.4.2.
The attacker managed to log in as admin on those instance, we are still trying to figure out how.















