Nostr notes by matt

Do you think people have to use Bitcoin for it to achieve that?

2026-10-16T13:21:57Z

In reply to nevent1q…ug80
_________________________

Do you think people have to use Bitcoin for it to achieve that?

Where are the optimistic Bitcoiners? Is there anyone left ...

2026-10-16T13:09:01Z

Where are the optimistic Bitcoiners? Is there anyone left actually optimistic about growing human freedom with software?

🤣 #nevent1q…cf8c

2026-10-04T02:03:43Z

🤣

quoting
nevent1q…cf8c
The BIP110/Blake chain finally has a use case: media publishing!

Using BcashJr Wallet, which also lets you easily split your BTC and Blake UTXOs, you can now publish images using the BPUB protocol.

BPUB doesn’t use Ordinals inscription envelopes. It embeds file data into public keys within multisig scripts, then reveals those scripts in transaction witnesses. That lets it publish images despite BIP110’s censorship.

Pick an image (resize and optimize it first), select the BLAKE coins to fund it, review the fees, and publish. Unused funds return to your wallet as change.

Download the latest release of BcashJr Wallet for Windows, macOS, and Linux here:
https://github.com/smolcars/bcashjr-wallet/releases

Read more about BPUB here:
https://github.com/djkazic/bpub

There’s like fifteen companies offering this…

2026-10-02T17:49:04Z

In reply to nevent1q…7tl6
_________________________

There’s like fifteen companies offering this…

Nostr event nevent1qqsgczfl4egkjg55vnlclywpd4n430zda2kllx2w62lnqyumfhqx49qzyq7ju52ss6vlnrc090d70fzmvu7xsllxgg85vmwzjmvshyyd282eg0qg5tu

2026-10-01T13:53:12Z

Government debt is the new shitcoin.

Nice. What hardware + battery + software did you land on?

2026-10-01T01:44:38Z

In reply to nevent1q…4suu
_________________________

Nice. What hardware + battery + software did you land on?

I’ve definitely heard that people make certain assumptions….

2026-09-20T16:00:56Z

In reply to nevent1q…u9gv
_________________________

I’ve definitely heard that people make certain assumptions….

If you’re always sleeping around it’s cause you don’t know ...

2026-09-20T06:44:30Z

In reply to nevent1q…jyvs
_________________________

If you’re always sleeping around it’s cause you don’t know what sex actually is, and are almost certainly just bad at it.

Maybe unpopular opinion? People who sleep around a lot are ...

2026-09-20T06:43:13Z

Maybe unpopular opinion?

People who sleep around a lot are actually just bad at sex. Sex with a long-term partner is infinitely more interesting and fulfilling in nearly every way.

Define “much”

2026-09-18T01:53:14Z

In reply to nevent1q…n5th
_________________________

Define “much”

Ha, maybe that too. But I get the sense everyone has been racing ...

2026-09-15T10:39:05Z

In reply to nevent1q…ps7w
_________________________

Ha, maybe that too. But I get the sense everyone has been racing ahead on days quality roughly in parallel, including synthetic data.

Not to mention that DeepSeek keeps substantially innovating in ...

2026-09-13T12:45:32Z

In reply to nevent1q…p7am
_________________________

Not to mention that DeepSeek keeps substantially innovating in public. Astra is literally built on an old DeepSeek paper!

The claim that Chinese models are “just distilled western ...

2026-09-13T12:44:43Z

In reply to nevent1q…wt32
_________________________

The claim that Chinese models are “just distilled western models” is obvious nonsense. The Chinese models often end up better than the ones they’re supposedly distilled from, and K3 came out when Fable had only been accessible for a very brief period.

The distillation claim seems to basically be a fantasy of the western labs that want to think they’re just that far ahead and Chinese people are all dumb copycats - no different than what tech thought of China 15-20 years ago.

They didn’t even bother to steal all the money, a huge amount ...

2026-09-08T02:10:51Z

In reply to nevent1q…mq8z
_________________________

They didn’t even bother to steal all the money, a huge amount was left vulnerable. Also, specifically to liquid, they have back doors to halt the system so reporting it to them can likely get the issue locked down faster than you can exploit it.

Finally, they kept 15%? That’s not even remotely white hat behavior. They just wanted to use the term “whitehat” to reduce risk of FBI.

Yea that’s the bug, but that’s not the fix. That was an ...

2026-09-07T00:35:58Z

In reply to nevent1q…e7lk
_________________________

Yea that’s the bug, but that’s not the fix. That was an attempted fix but in fact it was incomplete, the exploit, afaiu, exploited the patched code.

Well, yes, an individual tx that was invalid, just not crypto ...

2026-09-06T22:34:45Z

In reply to nevent1q…0hmv
_________________________

Well, yes, an individual tx that was invalid, just not crypto code failing to check it.

Nah, it was not an individual tx that was wrong. Based on a few ...

2026-09-06T22:32:10Z

In reply to nevent1q…9g3g
_________________________

Nah, it was not an individual tx that was wrong. Based on a few people’s LLM’s analysis that looks right it was a higher level consensus failure not the crypto code.

I saw someone saying mempool didn’t accept that block. Unclear ...

2026-09-06T20:47:30Z

In reply to nevent1q…7hsm
_________________________

I saw someone saying mempool didn’t accept that block. Unclear what’s going on I haven’t really dug into things

Nostr event nevent1qqst4h0agw0ffqqt4tc3vjwef4dwnnzmht0065lzz6dgu8wnhpv6yjczyq7ju52ss6vlnrc090d70fzmvu7xsllxgg85vmwzjmvshyyd282egsrw6k3

2026-09-06T20:46:32Z

In reply to nevent1q…59fs
_________________________

https://blockstream.info/liquid/tx/ce4caece413cd9d444ce7ed9f54e5b328b3da5e4af301aff59a3571f76e988f2

No, means “boy this shouldn’t have happened”

2026-09-06T20:39:59Z

In reply to nevent1q…jeqn
_________________________

No, means “boy this shouldn’t have happened”

There was supposed to be a whitelist of withdraw addresses. Maybe ...

2026-09-06T20:39:36Z

In reply to nevent1q…rwny
_________________________

There was supposed to be a whitelist of withdraw addresses. Maybe it was also a break in the range proof but there would have had to be a second bug. Seems more likely there was a software bug in the peg out verification more generally.

I’ve seen that claim, but zero evidence for it.

2026-09-06T20:38:04Z

In reply to nevent1q…rteu
_________________________

I’ve seen that claim, but zero evidence for it.

This is the thing that gets me. That should have been an easy ...

2026-09-06T20:11:28Z

In reply to nevent1q…9fz8
_________________________

This is the thing that gets me. That should have been an easy protection against this kind of hack.

Qwen3.8-Flash-Next is smarter and needs less VRAM anyway ...

2026-09-03T10:38:22Z

In reply to nevent1q…8nt6
_________________________

Qwen3.8-Flash-Next is smarter and needs less VRAM anyway 🤷‍♂️

Oof 3bpw? That’s usually pretty lobotomized.

2026-09-03T10:37:46Z

In reply to nevent1q…pd55
_________________________

Oof 3bpw? That’s usually pretty lobotomized.

Wait until they start hacking banks and laundering it through ...

2026-08-30T14:22:08Z

In reply to nevent1q…am8z
_________________________

Wait until they start hacking banks and laundering it through Bitcoin…

This is far from the first time wireshark has had a critical RCE ...

2026-08-28T00:09:51Z

In reply to nevent1q…mzmu
_________________________

This is far from the first time wireshark has had a critical RCE vulnerability 😭. In fact far from it, they gave them every year or three.

This is your regular reminder not to use Wireshark to read ...

2026-08-28T00:05:16Z

This is your regular reminder not to use Wireshark to read untrusted packets.

Whether they care about Bitcoin or not I’d really expect ...

2026-08-27T01:53:59Z

In reply to nevent1q…zum2
_________________________

Whether they care about Bitcoin or not I’d really expect something from a Pirate Bay founder to understand that what’s illegal in one country may not be in another…

I mean fuck even if it were unlicensed money services if it’s ...

2026-08-25T23:46:54Z

In reply to nevent1q…tfuq
_________________________

I mean fuck even if it were unlicensed money services if it’s not illegal where it’s hosted and it’s not trying to scam people why would you take down a domain?

Damn that’s so disappointing from njalla. #nevent1q…ccew

2026-08-25T23:45:47Z

Damn that’s so disappointing from njalla.

quoting
nevent1q…ccew

So I'm the predator now 😂

My reply:

I am frankly shocked by this suspension.

None of my domains contain any claim of holding a monetary license of any kind. Before taking action, did you actually verify the substance of the report filed against me?

My domains were used exclusively to host the client side of an open-source project:
https://gitworkshop.dev/bitblik.app/relay.ngit.dev/bitblik

This project does not constitute a monetary service or platform by any legal definition — a position I had confirmed with legal counsel prior to this dispute. Furthermore, the domains pointed to VPS infrastructure located entirely outside the European Union.

I would ask you to consider seriously: on what grounds can a report like this be treated as anything other than a bad-faith complaint from competitors operating under European licenses, attempting to suppress open-source peer-to-peer Bitcoin software?

I had understood your organization to stand for freedom of speech and the protection of individuals pursuing financial and technological sovereignty — including open-source development and separation from overreaching regulatory frameworks. This action is deeply at odds with those values.

I am extremely disappointed, and I will not be silent about this. I intend to make this situation widely known in Bitcoin, Nostr, and freedom-tech communities if it is not resolved promptly.

In the meantime, regardless of the outcome, please provide me with the EPP/auth codes for all affected domains so that I may transfer them to another registrar at my earliest convenience.

Thank you.

Probably tomorrow, and also again next week, and definitely for ...

2026-08-22T10:10:22Z

In reply to nevent1q…c7qr
_________________________

Probably tomorrow, and also again next week, and definitely for real about a month and a half from now.

It was a refrain in like 2018 cause the price would always pump ...

2026-08-21T10:57:16Z

In reply to nevent1q…2nad
_________________________

It was a refrain in like 2018 cause the price would always pump during Asia trading hours.

Got on a plane last night and my wife joked “and Asia hasn’t ...

2026-08-21T10:50:38Z

Got on a plane last night and my wife joked “and Asia hasn’t even woken up yet”. Indeed, guess we’re living in 2018 and Asia woke up 😂

Apparently he’s feeling it…

2026-08-12T13:04:56Z

In reply to nevent1q…a0ta
_________________________

Apparently he’s feeling it…

All the more reason for Luke to select a PoW he (or a friend) can ...

2026-08-12T09:59:59Z

In reply to nevent1q…2k0k
_________________________

All the more reason for Luke to select a PoW he (or a friend) can premine?

Problem is it needs a fork to reduce the difficulty. You’d need ...

2026-08-12T09:58:09Z

In reply to nevent1q…fgqz
_________________________

Problem is it needs a fork to reduce the difficulty. You’d need to convince people to follow that…

BDash

2026-08-12T00:58:24Z

In reply to nevent1q…z9u5
_________________________

BDash

Yea it is, it’s “fair” in that anyone with like a single S9 ...

2026-08-11T22:07:14Z

In reply to nevent1q…se7g
_________________________

Yea it is, it’s “fair” in that anyone with like a single S9 can select the outcome. The only reason to do it in such an obviously broken way is if you want to game it.

I mean hard to argue with honestly.

2026-08-11T22:06:23Z

In reply to nevent1q…fg68
_________________________

I mean hard to argue with honestly.

Wait so let me get this straight. Luke’s (obviously) trying to ...

2026-08-11T21:31:50Z

Wait so let me get this straight. Luke’s (obviously) trying to rig the PoW function selection for his coin, probably cause he has ASICs for one option.

So….he’s just trying to create a coin he can premine so he can dump it on the BIP 110 followers? Man that’s low af.

Almost certainly hardware failure, though if you have the ...

2026-08-11T10:54:47Z

In reply to nevent1q…79gk
_________________________

Almost certainly hardware failure, though if you have the specific error I’d be curious to see it.

Weird, I’ve asked everyone and no one seems to be having ...

2026-08-11T00:13:19Z

In reply to nevent1q…l2lx
_________________________

Weird, I’ve asked everyone and no one seems to be having issues.

What quant?

2026-08-10T00:41:59Z

In reply to nevent1q…xq6w
_________________________

What quant?

lol, no. The security model hinges on it being hard to change ...

2026-08-09T21:29:00Z

In reply to nevent1q…emqg
_________________________

lol, no. The security model hinges on it being *hard to change* Bitcoin’s rules. That applies equally to miners as to random nodes.

Hell yea

2026-08-09T16:45:57Z

In reply to nevent1q…z968
_________________________

Hell yea

People got this weird idea after segwit that a “UASF” is this ...

2026-08-09T15:52:55Z

People got this weird idea after segwit that a “UASF” is this magic thing where a bunch of people on social media get together and start making threats and suddenly Bitcoin’s consensus rules will change.

That’s nonsense. I’m sorry if you were told that the thing that activated Segwit was a UASF and nothing else but you were lied to.

For the good sports, yea. I will never forgive the subset of the ...

2026-08-09T01:52:53Z

In reply to nevent1q…23ad
_________________________

For the good sports, yea.

I will never forgive the subset of the BIP 110 community who drove gloria out of bitcoin with their massive harassment campaign, though - she did more for lightning from the core side than anyone since segwit and her leaving bitcoin was a massive loss.

Yea, maybe they thought if they got lucky and reorg’d one block ...

2026-08-08T22:20:57Z

In reply to nevent1q…5la7
_________________________

Yea, maybe they thought if they got lucky and reorg’d one block they’d scare other pools into joining.

Probably but you can’t buy 50% of the network….

2026-08-08T22:08:03Z

In reply to nevent1q…l2aj
_________________________

Probably but you can’t buy 50% of the network….

lol https://bip110.fail

2026-08-08T22:07:43Z

In reply to nevent1q…yerc
_________________________

lol https://bip110.fail

I missed that 110-coin isn’t even banning the subset of data ...

2026-08-08T22:07:29Z

I missed that 110-coin isn’t even banning the subset of data BIP 110 seeks to ban, and probably never will.

bip110.fail

Ha well that turned out to be wrong. Directionally right, but ...

2026-08-08T20:17:27Z

In reply to nevent1q…hdre
_________________________

Ha well that turned out to be wrong. Directionally right, but they got lucky fast.

What’s the node alias/pubkey?

2026-08-08T19:51:32Z

In reply to nevent1q…y9ns
_________________________

What’s the node alias/pubkey?

I’m betting any remaining 110 miners will turn off before they ...

2026-08-08T19:50:25Z

In reply to nevent1q…awh4
_________________________

I’m betting any remaining 110 miners will turn off before they get a block. Boring, but certainly the better outcome for Bitcoin.

I’ve had enough drama this week anyway.

After this week, BIP 110 just needs to go silently into the void.

2026-08-07T20:50:18Z

In reply to nevent1q…38gs
_________________________

After this week, BIP 110 just needs to go silently into the void.

Actual issue on the wrong hardware wallet…they’re just ...

2026-08-05T20:59:44Z

In reply to nevent1q…akkk
_________________________

Actual issue on the wrong hardware wallet…they’re just banking on “you heard about the hardware wallet hack…”

Yet more phishing attempts. ...

2026-08-05T20:35:30Z

Yet more phishing attempts.

It definitely is, but I’ve seen some people reproduce the issue ...

2026-08-05T11:38:43Z

In reply to nevent1q…a9cz
_________________________

It definitely is, but I’ve seen some people reproduce the issue without that and the agent automatically fetched the submodules.

Only if you put each word back in the bag after you pull and ...

2026-08-03T14:37:22Z

In reply to nevent1q…mv62
_________________________

Only if you put each word back in the bag after you pull and shake the bag really, really, really well (probably means the bag needs to be very oversized, if I had to guess).

That’s what suggestions 1,3, and 4 are meant to address.

2026-08-03T14:36:26Z

In reply to nevent1q…nda8
_________________________

That’s what suggestions 1,3, and 4 are meant to address.

I dunno about that. If you have a source that’s just 32 bits ...

2026-08-03T11:26:20Z

In reply to nevent1q…wpv5
_________________________

I dunno about that. If you have a source that’s just 32 bits (eg device ID) it’s not clear to me it’s worth including. Yes, if you screw everything else up it might save you, but in nearly every instance of weak entropy wallets a defining feature was some low entropy 32 bit counter that hid the bug. It seems like it’s worth banning this.

Sure, that’s a reasonable approach. Even just two HWRNGs ...

2026-08-03T11:06:49Z

In reply to nevent1q…g6pk
_________________________

Sure, that’s a reasonable approach. Even just two HWRNGs (they’re cheap!) is better than one.

> I think I'm misunderstanding the mechanics. I said ...

2026-08-03T11:01:36Z

In reply to nevent1q…f8zf
_________________________

> I think I'm misunderstanding the mechanics. I said 'inputs' to mean exactly 'pre-whitening'. But i have no idea exactly how it would work on Linux. Claude told me yesterday that it's deliberately made almost impossible to do, which makes a lot of sense, if true.

Right, the suggestion doesn’t work on the Linux RNG, it was more targeting embedded devices.

> Re: 'at least one validated', yep, that seems to be the right general idea.

Right, this part does work on Linux - use the OS RNG but also use mouse movements or whatever and check that you get enough entropy there. Maybe check for a TPM and pull bits from that, etc. Probably at least one source you can either fetch pre-whitening or you can access a success/fail result because the device checks for you.

#nevent1q…d2vw

2026-08-03T01:28:32Z

In reply to nevent1q…eada
_________________________

quoting nevent1q…d2vw
Not really. Once the weak entropy has been hashed you’re likely to miss issues. A million might give you a collision with only 32 bits of entropy, sure, but 60? Still brute forceable, but you won’t see it with such a test. Might be useful, but not as useful as the manual process I suggested in (4).

Not really. Once the weak entropy has been hashed you’re likely ...

2026-08-03T01:28:07Z

In reply to nevent1q…3xyx
_________________________

Not really. Once the weak entropy has been hashed you’re likely to miss issues. A million might give you a collision with only 32 bits of entropy, sure, but 60? Still brute forceable, but you won’t see it with such a test. Might be useful, but not as useful as the manual process I suggested in (4).

Anyone can do an LLM scan! Before buying your next hardware ...

2026-08-03T01:26:36Z

In reply to nevent1q…l877
_________________________

Anyone can do an LLM scan! Before buying your next hardware wallet, ask a frontier LLM to review their firmware!

Oh that’s definitely been happening. Lots of people have been ...

2026-08-03T00:40:19Z

In reply to nevent1q…k7l8
_________________________

Oh that’s definitely been happening. Lots of people have been *busy* this weekend.

It’s still early, but it’s not at all the case that we cant ...

2026-08-03T00:23:13Z

It’s still early, but it’s not at all the case that we cant learn anything from this and do better. If I were a hardware wallet manufacturer, I think my takeaways/changes I’d make are:

1) insecure fallbacks or hashing in weak entropy should be explicitly verboten. Unless it’s 96 bits or higher, do not include it!

2) Anything generating keys on an embedded device should have at least two random inputs and should check them with even basic randomness tests. This requires pulling lots of extra bits in before they’ve been whitened which isn’t possible on all hardware, but hardware that does whitening usually will do tests for you so make sure you’re checking it!

quoting nevent1q…9vun

That’s definitely not true. If you can run a test on the bits (and can extract a few orders of magnitude more bits than you need) before you use them and before they’re hashed/whitened/etc, you can absolutely test for quality. You then take a few sources that you’ve tested and xor/hash it all together and you’d be fairly confident in your robustness.

Sadly, many HW RNGs do whiten the output before you get it so it may not work everywhere, but some HWRNGs do test their data before they provide it!

3. (Obviously) Everyone should be doing regular LLM reviews of software and firmware.

4. HWWs should have an explicit QA step where each input to the RNG is logged and the result of adding those inputs together to build a seed is done on a separate device with a reimplementation and compared against the device's seed. This should be done for each firmware release.

I doubt almost any HWWs today do 2&4.

> Test before hashed/ whitened: yes. That was my original ...

2026-08-03T00:11:23Z

In reply to nevent1q…l299
_________________________

> Test before hashed/ whitened: yes. That was my original thought. But as others pointed out, that's not the same thing as what the whole process outputs.

Sure, but screwing up XORing three validated chunks together is harder than screwing up one. It wouldn’t have saved this case (which was ultimately a failure of having an insecure fallback in the code at all, which shouldn’t be allowed!), but it should be common practice.

> Also as per your comment with HWW, isn't it super-hard/impossible to check the *input* to dev/urandom's CSPRNG, in practice?

On Linux? Sure, that’s ultimately because it’s post-whitened/hashed which makes it hard to validate. That doesn’t mean it couldn’t be XOR’d with more but probably we should be requiring at least one “validated” input to any RNG for key generation.

The closed-source stuff is more complicated, of course, but I’d ...

2026-08-02T16:18:59Z

In reply to nevent1q…z9tu
_________________________

The closed-source stuff is more complicated, of course, but I’d expect any HWW to have at least two streams of actually random values and going forward I’d expect them to be (if at all possible within reasonable bounds) pulling a few KiB of output from each and doing at least basic statistics tests on them.

All the more reason for defensive coding in RNGs. Sadly this ...

2026-08-02T15:34:43Z

In reply to nevent1q…mz0r
_________________________

All the more reason for defensive coding in RNGs. Sadly this isn’t the norm (does anyone do it?) but hopefully it can become it…

quoting
nevent1q…9vun
That’s definitely not true. If you can run a test on the bits (and can extract a few orders of magnitude more bits than you need) before you use them and before they’re hashed/whitened/etc, you can absolutely test for quality. You then take a few sources that you’ve tested and xor/hash it all together and you’d be fairly confident in your robustness.

Sadly, many HW RNGs do whiten the output before you get it so it may not work everywhere, but some HWRNGs do test their data before they provide it!

That’s definitely not true. If you can run a test on the bits ...

2026-08-02T15:25:55Z

In reply to nevent1q…3aw6
_________________________

That’s definitely not true. If you can run a test on the bits (and can extract a few orders of magnitude more bits than you need) before you use them and before they’re hashed/whitened/etc, you can absolutely test for quality. You then take a few sources that you’ve tested and xor/hash it all together and you’d be fairly confident in your robustness.

Sadly, many HW RNGs do whiten the output before you get it so it may not work everywhere, but some HWRNGs do test their data before they provide it!

Sure, my only point was that it’s possible to take a ...

2026-08-02T10:12:45Z

In reply to nevent1q…x252
_________________________

Sure, my only point was that it’s possible to take a conservative approach to RNG with additional checks in place that could catch bugs. It’s not the case that RNG bugs are only possible to catch in review.

It’s not entirely hopeless. Running hardware RNG output through ...

2026-08-02T00:59:31Z

In reply to nevent1q…5llh
_________________________

It’s not entirely hopeless. Running hardware RNG output through basic entropy tests prior to hashing/use could have saved everyone a lot of headache. I don’t know that people do this today but probably we should all start!

Doesn’t mean any of us should feel good that so many people ...

2026-08-01T22:34:03Z

In reply to nevent1q…n2dq
_________________________

Doesn’t mean any of us should feel good that so many people lost their real money.

I’m gonna be honest, as much as I think bitcoin is important ...

2026-08-01T22:09:01Z

I’m gonna be honest, as much as I think bitcoin is important for freedom in the long term, it really doesn’t feel great working in bitcoin this weekend.

Hell yea.

2026-08-01T10:29:02Z

In reply to nevent1q…gqf8
_________________________

Hell yea.

💯

2026-08-01T00:32:19Z

In reply to nevent1q…5fnz
_________________________

💯

And, again, this was well before anything was public and they ...

2026-07-31T22:31:29Z

In reply to nevent1q…vvgd
_________________________

And, again, this was well before anything was public and they weren’t searching, they were analyzing the code. One of them was even skeptical cause it seemed too broken!

I think you drastically underestimate how much people have ...

2026-07-31T22:30:44Z

In reply to nevent1q…eutc
_________________________

I think you drastically underestimate how much people have scanned things with LLMs! Also they might have tried six months ago but the models are much better today than at the beginning of the year!

I can only go on my experience from yesterday and testing on LDK. ...

2026-07-31T21:54:51Z

In reply to nevent1q…h07j
_________________________

I can only go on my experience from yesterday and testing on LDK. Yesterday I know at least three people who asked three different LLMs to find the coldcard issue before any details were public and all three successfully found the issue. On LDK we’ve been doing code scanning and they have found many issues (most not critical security ones, but real problems with fixing, and some important security fixes as well!)

Well, I’m not sure if a model from a year ago would have found ...

2026-07-31T21:26:59Z

In reply to nevent1q…l5hk
_________________________

Well, I’m not sure if a model from a year ago would have found it, but, yes, absolutely no one asked the question in the past three to six months…. Until this week.

Anyone with a Claude or OpenAI subscription absolutely had no ...

2026-07-31T21:22:00Z

In reply to nevent1q…lmkg
_________________________

Anyone with a Claude or OpenAI subscription absolutely had no problem finding the ColdCard bug a week ago, if they looked.

No, I mean people who reproduced the issue before it was public. ...

2026-07-31T21:21:16Z

In reply to nevent1q…3u8c
_________________________

No, I mean people who reproduced the issue before it was public. The only prompts were things like “there appear to be funds getting drained from coldcards, let’s look at the firmware and find the bug”.

Now, maybe they promoted it with “there’s an issue leading to ...

2026-07-31T21:04:10Z

In reply to nevent1q…atyu
_________________________

Now, maybe they promoted it with “there’s an issue leading to drains!” Rather than “do a review”, but could always start with that.

Of coldcard? I know several people who asked different LLMs ...

2026-07-31T21:02:52Z

In reply to nevent1q…vwh6
_________________________

Of coldcard? I know several people who asked different LLMs yesterday and each immediately found the issue.

LLMs are very two-sided for security. On the one hand, ...

2026-07-31T20:58:17Z

LLMs are very two-sided for security.

On the one hand, long-latent bugs are finally surfacing.

On the other hand, before you choose to use a product, you can get your own code review done for incredibly low cost*!

In the short term it’s incredibly bad, in the long-term it democratizes code review greatly. “Don’t trust, verify” finally becomes an actual possibility for normal people!

* of course LLMs do still make up issues when asked, push any such review to write PoCs to check their analysis!

The selective sweep was a bug/lazy implementation on the part of ...

2026-07-31T17:25:46Z

In reply to nevent1q…g239
_________________________

The selective sweep was a bug/lazy implementation on the part of the attacker’s LLM.

I mean look at coldcard’s blog too…

2026-07-31T16:33:34Z

In reply to nevent1q…vpux
_________________________

I mean look at coldcard’s blog too…

Doing so at this juncture would allow attackers to steal ...

2026-07-31T11:07:41Z

In reply to nevent1q…wgl5
_________________________

Doing so at this juncture would allow attackers to steal additional coins faster.

As long as you did at least 40-50 dice rolls you’re okay. ...

2026-07-31T11:07:04Z

In reply to nevent1q…5qhl
_________________________

As long as you did at least 40-50 dice rolls you’re okay. Consider migrating out of an abundance of caution, but no rush.

Correct. If you have N-of-M multisig and N is greater than the ...

2026-07-31T11:06:02Z

In reply to nevent1q…efky
_________________________

Correct. If you have N-of-M multisig and N is greater than the number of coldcards you’re in no rush.

We know how to generate good randomness, they just had bugs. Best ...

2026-07-31T11:04:48Z

In reply to nevent1q…kl9z
_________________________

We know how to generate good randomness, they just had bugs. Best bet is multisig across different wallets if you’re worried.

Everything true up to the end. Other coldcards also have bugs, ...

2026-07-31T11:03:27Z

In reply to nevent1q…4456
_________________________

Everything true up to the end. Other coldcards also have bugs, not quite as severe but still bad.

I haven’t dug into the specific implementation. My ...

2026-07-31T01:58:23Z

In reply to nevent1q…p6ge
_________________________

I haven’t dug into the specific implementation. My understanding is the dice is combined with the very limited existing entropy (something like 32 bits). Generally if you’re in the 90+ bit range brute force isn’t likely. 64 brute force is still reasonably doable. Obviously variable in between.

If you have an old phone, reset/wipe it, install a good wallet ...

2026-07-31T01:52:48Z

In reply to nevent1q…ud3t
_________________________

If you have an old phone, reset/wipe it, install a good wallet and use that temporarily. If you either don’t know or don’t have confidence in any single wallet product for the amount you’re talking about, your best bet may be an exchange (just be prepared to get hassled for proof of origin of funds…).

6^50 is > 2^128. 50 rolls is basically equivalent to a perfect ...

2026-07-31T01:49:54Z

In reply to nevent1q…acaj
_________________________

6^50 is > 2^128. 50 rolls is basically equivalent to a perfect seed. Fewer of course less so.

Depends on how many. A few rolls? Migrate ASAP. 50 rolls? Don’t ...

2026-07-31T01:48:29Z

In reply to nevent1q…jv7k
_________________________

Depends on how many. A few rolls? Migrate ASAP. 50 rolls? Don’t ever think about it. Somewhere in between? Depends on how many…

Yes, later devices had a similar but slightly different (and ...

2026-07-31T01:47:23Z

In reply to nevent1q…7dj0
_________________________

Yes, later devices had a similar but slightly different (and somewhat less bad, though still loose-your-coins bad) bug.