Christian Decker (@Snyke) header
Christian Decker (@Snyke) profile picture

They call me Dr. Bitcoin. -- Bitcoin enthusiast since 2009, and researcher at @Blockstream

Zurich, CH
Joined July 2007
Photo by Christian Decker (@Snyke)Photo by Christian Decker (@Snyke)Photo by Christian Decker (@Snyke)Photo by Christian Decker (@Snyke)Photo by Christian Decker (@Snyke)Photo by Christian Decker (@Snyke)Photo by Christian Decker (@Snyke)Photo by Christian Decker (@Snyke)Photo by Christian Decker (@Snyke)
It looks like the Web-of-trust might have a future after all in these uncertain times 🤗
I can confirm that B731AAC521B013859313F674A26D6D9FE088ED58 is @snyke’s key. I verified it in person and signed it myself.
5
3
58
4,225
Well, seeing that our @Core_LN pre-announcement caused a bit of a kerfuffle, let me talk about the what, why, and when of the upcoming CLN v26.06.7 point release. 🧵 First of all: no need to panic. We are not aware of any vulnerability being actively exploited. 1/6
8
55
9
162
27,573
Should you prefer to wait for the source release, you absolutely can. As an added precaution, especially in the event that LLMs can reverse-engineer fixes from the binaries, we suggest restarting your node with the `--offline` flag. 5/6
1
2
30
1,519
`--offline` stops incoming and outbound connections, isolating your node, while still enforcing correctness on-chain if any peers attempt to cheat. You can then selectively and manually reconnect to trusted peers if you want to continue using LN for payments. 6/6
1
1
1
35
1,079
Christian Decker retweeted
If you run Core Lightning: when the release is published: upgrade with signed binaries, or start your node with `--offline`. Details stay under embargo for two weeks. Previous releases, including 26.04, are unsupported. Full details when the embargo lifts. The 26.09 release is still planned for late September.
Like many open source Bitcoin projects, CLN has received a number of AI-generated CVE reports from multiple sources over the past 10 days. Our small team, together with several invaluable open source contributors, has been working intensively to validate and triage these reports and develop fixes where needed. We’re now working through a broader remediation strategy. The first step is a point release containing many of these fixes, and we will strongly recommend upgrading. We’re aiming to have an initial version of the point release available within the next few days.
13
60
13
124
28,536
Christian Decker retweeted
The past weeks have been quite challenging, with many batches of AI-generated reports to analyze, most of them finding real issues that needed to be fixed ASAP. Many thanks to folks who run those scans, this is extremely helpful!
1
1
24
981
Christian Decker retweeted
CORE LIGHTNING WARNS USERS TO UPGRADE OR TAKE NODES OFFLINE Core Lightning developers are preparing an emergency release after receiving a wave of AI-generated CVE reports over the past 10 days and validating vulnerabilities requiring fixes. The team has escalated its response and will release signed binaries while keeping details of the vulnerabilities under embargo for two weeks. CLN strongly urges EVERYONE to upgrade during that window. If you don’t upgrade, developers recommend taking your node OFFLINE due to the known risks. Previous releases, including 26.04, will no longer be supported.
10
26
9
108
19,553
Christian Decker retweeted
Wondering why each project wants to maximize the abstraction level of the Lightning Network, preventing the user from controlling their node. Of course, running a self-hosted node can be complicated (I don't do it either), but even within the Lightning-as-a-Service paradigm, I want to be able to create channels, customize my invoices, configure payments, etc. Many wallets don't allow this. Many of them have shitty UI/UX. Many of them I haven't seen yet. So, I've built my own open-source Lightning wallet powered by the Greenlight backend.
4
8
1
27
1,627
Radicle is the most #Bitcoin VCS out there. Little known fact: they explicitly credit the Lightning Network specification as Inspiration of their transport and gossip subprotocols ⚡🚀
UPDATE: Bitchat is now mirrored on @Radicle — censorship-resistant, peer-to-peer code hosting: iOS/macOS: rad:z2v9tRJz1oknFAqCSY5W5c76nVvm6 Android: rad:z347HbE1F4c77DVLvsPe2ApoEEw6f Clone it. Seed it. Keep it alive. 👇
3
4
28
3,051
Christian Decker retweeted
Martin is a beast of an engineer. Proud that Brink can support him.
We are excited to announce that Martin Zumsande (@lightlike1) has (re)joined Brink to continue his work on Bitcoin Core including P2P networking, validation, testing, and review!
3
9
97
4,623
Christian Decker retweeted
SOMEBODY HAS TO SAY IT THE BITCOIN DICTATOR
159
159
70
856
143,530
I think the biggest misconception of our time is that being economically successful, being intelligent and having deserved it are all somehow aligned.
4
2
2
33
1,686
Natural stupidity?
What’s coming after Artificial intelligence?
2
2
18
1,867
The "rational market participant" is the economist's equivalent of the "spherical cow" and approximately as realistic...
1
1
11
1,110
I really dislike the apples vs oranges comparisons that new off chain protocol proponents such as Ark and Spark perpetuate: liquidity is only a problem when crossing the boundary of a LN channel. Ark and Spark compare that with intra-instance payments.
5
10
1
41
4,037
Consider this: each instance of ark/spark or LN channel is an island with a fixed set of participants. Amongst the participants of a single instance there is no limit on how the funds can be redistributed and no limit on speed.
4
3
19
1,734
Not saying Ark or Spark aren't great new developments, but please keep the comparisons honest. LN just makes inter- and intra-instance payments evident because it is limited to two participants per channel. But that goes away with multi-party channels.
2
1
1
16
1,052
It's crossing from on instance/channel to another where we need others liquidity, and LN is the only one allowing such cross-instance payments, hence why LN is still being used to connects arks, and then they face the same liquidity issues.
3
2
15
690