Bitcoin developer meetup serving the Research Triangle NC ⚡[email protected] #nostr npub18z4n70qxqv40xef4je7fd0zya462gmkhvf2eax695f6sfgrk9yvq55lrpv

Raleigh/Durham/Chapel Hill, NC
Joined November 2021
Triangle BitDevs retweeted
In August the Core Lightning maintainers told node operators to upgrade or run --offline. There was nothing to upgrade to for another two days, and when v26.06.7 arrived it was binaries only, with the source held back a further two weeks so attackers could not reverse-engineer the fixes. We (me + AI models) used that window. Ten AI models, one public source tree, the same five sentences of prompt, under $100 between them. Every report was hashed into the Bitcoin blockchain with OpenTimestamps as it was finished, nine days before upstream published the source, so none of it can be backdated. Reading source, the models found four of the nine defects the release fixed. Running "strings" on the public download found five more, and one of those is theft that pays for itself: as a forwarding node you refund the sender upstream, and the peer then claims the outgoing HTLC on-chain with the preimage it held the whole time. You pay twice and collect nothing. It was findable because the patched binary carries upstream's own new log line, FUNDS LOSS, which names the function, and the vulnerable code sat in the public v26.06.6 tree throughout. Three models at three price points landed on it within minutes of the download. The embargo hides the patch, but not the mechanism. Write-up: juraj.bednar.io/en/blog-en/2… Full case-study, reports and timestamps: github.com/jooray/CLN-incide…
6
14
3
78
7,194
Triangle BitDevs retweeted
Maybe it's just me but I never see an AI doomer who changes his own oil. I wonder why that is...
1
1
14
Triangle BitDevs retweeted
Replying to @lopp
north carolinians don’t play. make sure you look up the castle laws in NC before you trespass in that state!
1
5
698
rbitcoin now has a logo and a website. Why? I have no idea. Maybe people will find it useful and randomly send me bitcoin to keep building it. rbitcoin.org
🤖 Made with AI
8
6
47
2,410
Today, Bitcoin Policy Institute and a broad coalition from across the digital-asset ecosystem are publishing an open letter calling on the world’s leading AI labs to provide qualified open-source defenders with trusted access to frontier AI models. The past several weeks have made the need for this abundantly clear. The people defending digital-asset infrastructure and open-source software need access to the latest AI capabilities to perform comprehensive security reviews and stay ahead of increasingly sophisticated adversaries. The coalition includes open-source development organizations, major custodians, treasury companies, payment services, security firms, capital allocators, and others whose businesses and customers depend on the integrity of open-source infrastructure and libraries. Open-source defenders often occupy the least privileged position in the AI security landscape. They have limited access to the strongest internal cyber models and are frequently blocked by guardrails when using publicly available frontier systems for legitimate security research. As a result, they often resort to less capable open-weight alternatives. We are urging frontier AI labs to establish a clear, trusted pathway for qualified open-source and digital asset defenders to access their strongest capabilities, with sufficient compute and secure environments to conduct meaningful security reviews. Frontier AI could become one of the most powerful defensive technologies ever developed, but only if defenders get fair access to those systems. It’s time to give defenders the tools they deserve. Read the open letter, add your organization, or sign as an individual on our website at btcpolicy.org/ailetter
87
382
76
1,279
553,952
Triangle BitDevs retweeted
~90% of ASICs run one vendor's closed-source firmware. Almost nobody has audited it. We at @256FOUNDATION do. Introducing the 256 Red Team 🧵 — the 256 Foundation's firmware security program. On hardware we own, in an isolated lab, under coordinated disclosure.
19
77
16
313
65,010
Triangle BitDevs retweeted
We’re listening to the community and updating things as fast as we can. We’ve added more methods to create entropy offline with our new Help Center guide: help.blockstream.com/generat… All tables can now be printed with white backgrounds, black text, and borders.
btw @BlockstreamJade your dice generated recovery phrase instructions are totally impractical. nobody has 16 sided dice. only D&D players have 8 sided dice. it would be far more useful to use the ubiquitous d6 for physically generated entropy. help.blockstream.com/blockst…
18
17
2
162
14,209
Triangle BitDevs retweeted
We never officially covered BIP-110 because it has always been a waste of time and attention. A social DOS attack. Join us Wednesday for Socratic Seminar 55. This marks the 13th seminar with a covenants topic header and the 32nd with a covenants agenda item. RSVP 👇
2
1
7
234
Triangle BitDevs retweeted
Your attention is a valuable resource. Some people try to change your mind on a topic. But the easier method is to convince you to re-arrange your attention without changing your mind on any topic. Just get you to hyper-focus on one, and de-emphasize another.
89
128
22
1,711
150,046
Triangle BitDevs retweeted
There is a critical vulnerability being actively exploited on BTCPay Server, which can result in the loss of funds. Please update your BTCPayServer to 2.4.2 by going to Admin Dashboard -> Server -> Maintenance -> Update & verify the 2.4.2 version string in the footer. If you are unable to update right away, turn off your BTCPay Server to prevent unauthorized access until you can update.
216
1,354
519
2,550
1,617,661
Triangle BitDevs retweeted
I know everyone is busy right now, but I need you to take a few minutes and write me a letter of support for .bitcoin
97
225
44
705
135,878
Triangle BitDevs retweeted
Don't fw anybody you can't trust.
1
34
Triangle BitDevs retweeted
Roll the dice, anon.
1
35
Triangle BitDevs retweeted
Lightning swaps in Electrum initially used a Boltz-based backend. This was replaced by an Electrum backend in version 4.5.0 (January 2024). Since version 4.6.0 (July 2025), the swap market is decentralized, and zeroconf swaps have been removed from Electrum.
Update: Boltz will stay disabled until further notice. Our API remains available to process refunds cooperatively. In any case, unilateral refunds will work, as they do not depend on our infrastructure. Our support team stays reachable. To be clear: this is not a response to a single incident. Over the past months we have seen a steady rise in automated, AI-assisted probing of our infrastructure, and we have dealt with several exploits. Each was contained, but the pattern is clear: attackers now iterate faster than a team our size can find and patch. In the past few days alone we saw a drastic acceleration, and we do not believe this asymmetry will reverse. After reviewing the results of our own recent security scans, we cannot responsibly re-enable Boltz swaps, especially as we are being actively targeted by what appear to be multiple resourceful groups while we race to deploy fixes. What we are seeing is a major paradigm shift for Bitcoin services operating on an open source stack, and it needs careful analysis. Do not expect swap services to resume shortly. To be explicit: no user funds were ever at risk. Boltz is non-custodial by design. And as a fully bootstrapped company, the losses were ours alone. We don't know yet how things will continue from here, but we'll keep you posted as soon as we have had the time to catch our breath and make a decision 🙏
6
32
9
244
17,975
Triangle BitDevs retweeted
Replying to @Leishman @River
Only the paranoid survive.
1
5
47
1,844
Triangle BitDevs retweeted
Replying to @DocumentingBTC
> if insufficient manual entropy is provided, it fills the remainder from the system random number generation cold card has accepted low entropy dice input for years. people lost multiple bitcoin due to an insane and insanely stupid default behavior. blue wallet does it right.
1
1
1
121
Blue Wallet has a feature allowing users to add your own entropy using dice rolls or coin flips to create a Bitcoin private key, and if insufficient manual entropy is provided, it fills the remainder from the system random number generation.
23
51
2
310
41,367
Helpful video explaining how to create a simple 12 word bitcoin wallet seed using Seedsigner and dice. Its filmed in real time so you can see the entire process and how long it takes
31
95
4
515
62,652
Triangle BitDevs retweeted
I have spent over $10,000 scanning 100+ bitcoin ecosystem related libraries looking for vulnerabilities with Kimi K3 running as quarterback. Myself and a small "Red Team" have found multiple serious vulnerabilities impacting the ecosystem. They vary in scope severity, but this is a call to action. For any critical tier vulnerability that was identified if I was able to immediately demonstrate a POC (proof of concept), I have already responsibly disclosed to the maintainers. HERE IS HOW YOU CAN HELP ME IF YOU ARE NOT TECHNICAL: - please share with me any repository that is on github that I can scan, we want to cast a wide net. It takes a few moments for you to link github accounts, we'll take it from there - if that project does not have a SECURITY.md make an issue asking the dev to list one IF YOU ARE TECHNICAL: - If you are a maintainer or contributor to a project, I may have already scanned your repo, hit me up I'll share the results, if not I'll add your project to the list. - If I can trust you to do larger review to start looking through this stuff to give me more eyes let me know. AI Has forever changed software development. Tomorrow marks 1 week of Kimi k3 being live in open weights. We are going to accelerate.
289
429
62
2,518
226,903