Given things like the ledger hardware attack[1] I think the time indexed risk of using a centralized exchange is probably lower than doing self-custody.
I understand that many people do self-custody for philosophical reasons, but I think trying to disguise this as a security decision ("If your crypto was stolen in this, it wasn't your crypto.") is arguable at best.
[1] https://www.ft.com/content/70f69253-6017-4259-95c9-48bf0e088...
Does this mean you recommend not using one? Because that goes against all the common best practice recommendations from when I did a couple of years working in Web3 stuff a few years back.
> I think it's naive to suggest that self-custody is just a novelty with no value.
That's not what I suggested.
I suggested that it is less secure over time than centralized exchanges, even with the things you listed.
Records are largely a novelty. And predate streaming services.
I'm fairly sure originals are almost universally novelties compared to things that came after.
There apparently is no such thing as “your crypto” with how many security problems there are.
The Bitcoin mining network is somewhere around 1000 EH/s, while the (AI assisted research ahead) 34.5 million H100-equivalent GPUs globally would yield about 0.435 EH/s. They'd represent less than 0.05% of the Bitcoin network.
Then I forgot my pass phrase and have never been able to recover any of it. I don’t even know how many btc were mined/lost.
Before anyone asks, no, there aren’t any usable exploits / vulns found for the encryption methods used. And from what I can tell the coins in question have still sat frozen for going in a decade and a half now. I suspect many other hackers did the same thing…
Edit: I thought he was talking about 2012 but yeah in 2010 CPU mining was still a thing
Possibly Trezor (35 points, 16 days ago, 3 comments) https://news.ycombinator.com/item?id=50078423
> Coldcard’s software is built on MicroPython, and Coinkite supplies its own hardware-RNG wrapper for the device’s STM32 chip. To avoid conflicts, Coinkite deliberately disabled MicroPython’s built-in RNG path by setting a configuration flag, MICROPY_HW_ENABLE_RNG, to zero. The problem: the underlying library checked only whether that flag was defined, not whether it was enabled (set to a non-zero value). Because a flag set to zero is still “defined,” the build silently compiled against the wrong code, and seed generation fell back to a deterministic software pseudo-random number generator called Yasmarang
Tbh the biggest problem is platforms deciding you’re buying drugs because you purchase and transfer out (thanks Venmo)
A paper wallet works as well
A hardware wallet is just a tradeoff between convenience and an extra security risk
Let's say I use an open source wallet, generate the keys, send there a few Bitcoin and then I print the wallet
Now the Bitcoin is on a paper wallet, where's the vulnerability here? (except a crazy ex burning it down, but that's besides the point haha)
An old laptop with the wifi card taken out is more transparent and auditable. It just runs the ordinary open source code
But I just keep all my funds in a hot wallet, no multisig. And if I get hacked I lose it all. I think the answer is just have good security and dont get hacked. The risk of losing cryptocurrency will encourage security advances across the whole ecosystem. I think I will set up multisig eventually
> I think the answer is just have good security and dont get hacked.
So you proposed a way to be more secure, only to discard it yourself in favor of “just having good security”?
In fact, updates are only a risk. You physically remove anything that can allow updates to happen + anything that allows wireless networking.
I agree my approach is not great, I dont own a lot
If your paper wallet, generated offline, used a bad RNG, it is just as vulnerable.
That sounds like your housekeeper's key...
You can store crypto with zero risk of electronic access just using offline wallet generation and an offline wallet. It's not even hard.
This falls under "extraordinary precautions" that few people do and is an enormous error prone hassle.
You could put it in USD and you'd be financing the bombings of schoolgirls in Iran in a pointless and no-end-in-sight war... not saying either is better, but one of them is optional for US citizens, while the other isn't. And the optional one also lets you avoid third-party custodians like Binance.