Karadenizli

Public Key

npub15r9hp5eq3a0heantnja4sth3ug277nhse9f3scu937mxfh0mpw8snt7dpl

Profile Code

nprofile1qqs2pjms6vsg7hmu7e4eew6c9mc7y900fmcvj5ccvwzcldnymhashrcpr3mhxue69uhkummnw3ez6vp39eukz6mfdphkumn99e3k7mgpzfmhxue69uhk7enxvd5xz6tw9ec82csd73v48

Publishing to

nostr-01.yakihonne.com

Author Public Key

npub15r9hp5eq3a0heantnja4sth3ug277nhse9f3scu937mxfh0mpw8snt7dpl

Show more details

Last Notes

2026-08-19 18:41:52 UTC

- reply

That would only be possible if they have spy data from their desktop wallet app about who owns what utxo. Maybe they could partner with coinbase and other exchanges to verify owners but that would only work for never sent coins. How do you verify ownership otherwise?
Maybe they could've done serial number - seed entropy matching if they had the data from production and ask people to submit both and match it with the seed of their utxo.

2026-08-19 02:28:22 UTC

- reply

Autistic pushback on the last point.
Even if nvk found the bug before any hacker, what could they have done about it? The hackers could exploit it faster than most users would be at moving their coins. It might have prevented a decent amount but most cold storage coins would still be swiped.
#nevent1q…8m9p

2026-08-06 02:24:40 UTC

I know for a fact that every other hardware and software wallet manufacturer is auditing their own code right now, but what if they do find a similar vulnerability? If they find they have a similar problem, the moment they tell their customers to move their funds, hackers will beat most users to the punch.
CC was fine until the bug got discovered, but even if they had found it themselves before the hacker, they can't get the word out without letting the hackers know. This was set in stone the moment they ever shipped a device with the bug. Even if they noticed it a year later, that would only help devices after that point.