Lincs Bitcoin (@LincsBitcoin) header
Lincs Bitcoin (@LincsBitcoin) profile picture

Meetups on the 3rd Monday of each month. Bitcoin-only.

Lincolnshire, UK
Joined July 2023
Photo by Lincs Bitcoin (@LincsBitcoin)Photo by Lincs Bitcoin (@LincsBitcoin)Photo by Lincs Bitcoin (@LincsBitcoin)Photo by Lincs Bitcoin (@LincsBitcoin)Photo by Lincs Bitcoin (@LincsBitcoin)Photo by Lincs Bitcoin (@LincsBitcoin)Photo by Lincs Bitcoin (@LincsBitcoin)Photo by Lincs Bitcoin (@LincsBitcoin)
Lincs Bitcoin retweeted
🚨 We're releasing an emergency update to address nginx CVE-2026-123007, CVE-2026-123634, CVE-2026-123633, CVE-2026-121810, CVE-2026-113425. We recommend updating your BTCPay Server as soon as possible.
13
143
28
281
40,285
🚨 TONIGHT'S MEETUP IS CANCELLED 🚨
🚨 NEW MEETUP ALERT 🚨 The next Lincs Bitcoin meetup is taking place on: 📆 Mon 16th November ⌚ 19:30-21:30 📍 The Treaty of Commerce, Lincoln
1
84
🚨 REMINDER - TOMORROW 🚨
🚨 NEW MEETUP ALERT 🚨 The next Lincs Bitcoin meetup is taking place on: 📆 Mon 16th November ⌚ 19:30-21:30 📍 The Treaty of Commerce, Lincoln
20
🚨 REMINDER - A WEEK TODAY 🚨
🚨 NEW MEETUP ALERT 🚨 The next Lincs Bitcoin meetup is taking place on: 📆 Mon 16th November ⌚ 19:30-21:30 📍 The Treaty of Commerce, Lincoln
23
Lincs Bitcoin retweeted
⚠️⚠️ 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.
45
412
99
633
136,622
Lincs Bitcoin retweeted
A truly unprecedented attack upon cold storage at scale. nitter.gq/InsiderGeo/status/2117…
UPDATE: The European refrigeration cyberattack has now reached Italy and Romania, bringing the total to at least 10 countries affected across Europe. In Italy, several Coop stores in Sicily were hit, including at least three in Catania and one in Palermo. In Romania, at least six stores have reportedly been affected. Some affected businesses have yet to publicly disclose the incidents, meaning the actual number of countries and locations impacted could be even higher. The full scale of this cyberattack remains unknown. Countries affected so far: 🇸🇪 Sweden 🇧🇪 Belgium 🇱🇺 Luxembourg 🇪🇪 Estonia 🇮🇪 Ireland 🇳🇱 Netherlands 🇫🇮 Finland 🇩🇰 Denmark 🇮🇹 Italy 🇷🇴 Romania
62
55
5
1,293
42,894
Lincs Bitcoin 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]
35
106
65
263
57,409
"The estimated total impact sits at around $6.3B" 🤯
Binance's initial investigation suggests that the security incident may involve a compromised DevOps engineer’s laptop, which allowed an attacker to gain access to a service container and submit unauthorized withdrawal transactions. We have found no evidence of any wallet private key leak. We will share a detailed technical post-mortem once the investigation is complete and the facts are fully verified. The estimated total impact sits at around $6.3B. We have worked with blockchain partners to freeze affected assets, with ~$3 billion frozen on-chain so far. Binance will cover all losses from the SAFU fund and the company’s funds. User funds are safe. We will also publish an updated Proof of Reserves once the remediation is complete. As an immediate precaution, Binance has: - temporarily suspended deposits and withdrawals while security checks are completed; - revoked the affected address authorisation; - engaged law enforcement and blockchain intelligence partners to trace and recover funds. Our teams are working around the clock to resolve this issue safely and thoroughly. We are working closely with our law enforcement partners to confirm the identity of these criminals and bring them to justice. Please rely only on official Binance channels for updates. Please feel free to contact Binance Customer Support if you have any further questions. binance.com/en/support/annou…
25
Lincs Bitcoin retweeted
🚨 We're releasing BTPay Server 2.4.7 an emergency update fixing one critical and several medium-severity security vulnerabilities brought to our attention through @Anthropic's frontier OSS scanner. We recommend that you update your BTCPay Server as soon as possible.
13
110
16
224
29,789
Sparrow v2.5.6 has been released, removing the eMudhra root certificates and upgrading the bundled Tor to meet the client protocols now required by the Tor network. It also brings extensive screen reader and keyboard accessibility improvements. Changelog: github.com/sparrowwallet/spa… Download: sparrowwallet.com/download
Sparrow v2.5.0 released with: Silent Payments (SP) wallets SP-capable Frigate public server @2140_dev bitview.space fee rates source sparrowwallet.com/download
24
166
11
848
32,794
This is so good 🤣
David Attenborough: Bitcoiners in the wild 🦍🟠₿ In this film, we follow one of the most fascinating and least understood species on planet Earth… the Bitcoiner If you enjoyed this, a like and repost. Follow for more Bitcoin comedy 🧡
1
39
Lincs Bitcoin retweeted
Happy Friday everyone! time for some free sats ⚡️ Drop your lightning address in the comments and we will send you some sats! 🧡 Ends 1pm BST
1,050
175
6
457
13,192
Lincs Bitcoin retweeted
Introducing Bitwater: the water heater element that mines Bitcoin. It screws into the electric tank you already have. Physically decentralized mining that runs no matter what 🧵 Heat water. Mine Bitcoin. Same tank.
564
925
500
7,881
1,457,640
🚨 NEW MEETUP ALERT 🚨 The next Lincs Bitcoin meetup is taking place on: 📆 Mon 16th November ⌚ 19:30-21:30 📍 The Treaty of Commerce, Lincoln
1
1
156
🚨 REMINDER - TOMORROW 🚨
🚨 NEW MEETUP ALERT 🚨 The next Lincs Bitcoin meetup is taking place on: 📆 Mon 19th October ⌚ 19:30-21:30 📍 The Treaty of Commerce, Lincoln
26
Don’t trust. Read the BIPs. Because nobody does. They’re written by developers, for developers. So I built BIP Explorer: all 213 Bitcoin Improvement Proposals in plain English, plus a map of how each one led to the next. bipexplorer.com
43
97
23
496
21,120
🚨 REMINDER - A WEEK TODAY 🚨
🚨 NEW MEETUP ALERT 🚨 The next Lincs Bitcoin meetup is taking place on: 📆 Mon 19th October ⌚ 19:30-21:30 📍 The Treaty of Commerce, Lincoln
19
Lincs Bitcoin retweeted
A few words given the recent exploits on hardware signing devices: • The Ledger supply chain attack represents one of the most sophisticated attacks thus far on the wallet ecosystem. In many ways it’s a lot more sophisticated than the Coldcard RNG exploit, because that one was software only. This one took a cross-border company buyout, tampering with the devices (implanting an eSIM, an LTE module and a CPU) and manufacturing the implants at scale. • These sorts of attacks have been predicted by early Bitcoiners, but in Bitcoin they remained theoretical or crude until this year. It shows that the level of sophistication of attacks has risen quickly, and what was previously “good enough” advice on wallets and self-custody is no longer sufficient. • When we started Nunchuk a few years ago, our premise was that multisig, and multi-vendor multisig, needs to become the standard for self-custody in the future. But even we didn’t expect how fast it would materialize. This is likely due to 2 factors: Bitcoin getting more mainstream, and the rise of AI-assisted attacks. This is a Sputnik moment for Bitcoin self-custody. The defenses need to level up. • Passphrases wouldn’t have helped in the Ledger case, since you are required to enter the passphrase into the device for it to sign any transactions. A compromised device that phones home the seed phrase can also easily phone home the passphrase the moment you enter it. • Similarly, generating the private key somewhere else (even by rolling dice) and subsequently importing it onto a tampered device wouldn’t save you here. The device can phone home the seed phrase the moment it’s imported. • Anti-tampering techniques might help, such as transparent casing or bricking the device if it’s tampered with. Or forever displaying a message once the seal is broken. Or using on-device encryption between the internal hardware components. But a dedicated and resourceful enough attacker can still find ways to get around these layers. Tampering and anti-tampering have long been a cat-and-mouse game. In 2008, card readers doctored right off a Chinese production line sent card data and PINs over mobile networks to Pakistan. The Ledger attack is the same playbook, 18 years later. The bigger the target, the more attackers spend on overcoming the defenses. • You should order directly from the vendors as much as possible, using a PO box for privacy. • Any setup that relies on a single hardware/software stack or a single vendor should be considered at risk. • Building your own hardware signers from generic parts is a good option for technical users. • Multi-vendor multisig should become the standard. Each signer should have a completely independent hardware/software stack from the other signers. The point is that there shouldn’t be any single-point-of-failure anywhere in your setup. • Many advanced protocols rely on timelocks and the recovery path being a simple singlesig. The recent attacks and exploits should highlight how dangerous this could be. Timelocks simply delay a risk. If a seed is compromised and there’s a timelock involved, the attacker just needs to wait out the timelock. (For Miniscript wallets, there’s the wallet descriptor too, but presumably it also gets sent to the device at some point.) Vault-like protocols face a similar problem: any withdrawal or recovery path that relies on a single key is a potential single point of failure. • For our on-chain timelock-assisted wallets, in a few weeks we are adding the option to customize the recovery path to be an M-of-N, so that, if you want, spending would require multiple keys at all points during the wallet’s lifetime.
Replying to @moo9000
Left to right: e-SIM, CPU with firmware able to recognize Ledger's font as shown on screen and capture words as they appear on screen, and a LTE module that can connect once the seed has been fully captured.
35
85
18
434
106,621