diggity retweeted
New episode!
@Slappy_Jones_2 and I discuss:
- Fruitcake and how he didn't know about the negative stereotype
- Ledger rug
- Why generic hardware running Bitcoin Core mitigates the Coldcard and Ledger rugs
Link in the reply.
diggity retweeted
How the hack works, who should panic and how to get safe.
teapawt.org/i/spaces/1OGwbnykoQDKB
diggity retweeted
Brian's comment here isn't genuine adversarial security concern, but a contrived adversarial narrative.
Security design is not about imagining a hypothetical scenario and then mitigating it. There is no exploit without a cost. There is no mitigation without a cost.
You have to start with analysis of the actual path to the exploit and what it would cost, vs what it would cost to mitigate.
Every air gapped Bitcoin signer must have a data transfer channel to a network connected node.
This transfer channel is the easiest and cheapest path for key exfil and malware payloads.
Exploiting the radio chip in the signer would require a sophisticated malware payload on the amnesic signer.
What's the best way to get the malware payload that exploits the radio chip onto the amnesic signer? Over the transfer channel.
If you own the transfer channel why bother why with your contrived radio exploit? Exfil back over the transfer channel, you already own it.
The only other path for delivering malware to the signer (or anywhere in the yeti-2.0 stack for that matter) is for the user to download the malware.
They won't do this if they follow the instructions because the devices are purpose dedicated for linux and Bitcoin Core only, and they are instructed to only download select scrutinized software via command line and then check the hash files for integrity before proceeding.
Yeti mitigates the risk of there being existing malware in the supply chain of the software stack because it doesn't use a dozen different Bitcoin applications and libraries.
It's just guix attested Bitcoin Core.
So good luck with your radio exploit.
diggity retweeted
Bitcoin core uses a dozen things like radioactive decay and you are rolling dice? 🤣
Thermal/Johnson & shot: Brownian electron motion (kT) + discrete charge Poisson stats in silicon.
Crystal: quartz piezo freq shifts from thermal expansion, voltage, vibration stress, aging.
HDD: continuous platter positions + air turbulence + variable seek friction/inertia.
Human: ion-channel thermal noise + chaotic neural/muscle signaling.
Elec: thermal fluctuations + EM interference on paths.
Cache/etc: activity heat/voltage alters transistor thresholds/mobility via solid-state physics.
diggity retweeted
Good morning. It's important to learn how to generate good entropy to secure your Bitcoin. This is how you do it.
Entropylabs.online
diggity retweeted
Here's why this reply is wrong:
Firstly, yes, this is not a threat model, because this is from a context file. The threat model is a different file, it's called THREAT_MODEL, maybe we will need to come up with a clearer name for people like brian.
Secondly, this is not a lie. In the context of the threat model and the projects procedure, operational losses are mitigated with a very thorough start-to-finish process.
These are few and far between in Bitcoin, people like brian love to make vague recommendations that result in operational losses. Use dice, buy a cold card, use multivendor multisig, whatever. What kills people are the millions of little details they didn't think about in between A and B.
A fully opinionated start to finish guide like yeti mitigates this kind of operational risk because those decisions are made for you. You're not going to do something dumb and clever that gets you wrecked.
The threat model is very clear that yeti is designed to mitigate operational failures due to users choosing a stupid path and remote theft of keys due to malware in the software stack.
But Brian won't give you this full picture because he's not an honest person.
Replying to @heavilyarmedc
This is not a threat model, this is you prompting the model to lie. Clown.
diggity retweeted
What if Bitcoin self-custody got worse by adding more “security”?
Maybe the next breakthrough is subtraction.
Generic hardware. Minimal Linux. Bitcoin Core.
Everything else has to earn its place.
diggity retweeted
If you think that the Coldcard bug brought about some grand watershed moment across the entirety of the Bitcoin world, you are the target for the next bug.
Many of the existing malicious actors will simply pivot.
The evidence is all of the stupid reactions that don't make anyone's Bitcoin more secure.
According to Reason magazine's 2022 documentary, Honk Honk HODL raised over $1M in bitcoin for the Canadian truckers. About two-thirds reached them via paper wallets. JW Weatherman stepped in when organizers had no distribution plan, crowdsourcing ideas and helping split 14.6 BTC into 100 wallets for direct handover by NobodyCaribou.
diggity retweeted
Someone asked me in DMs why i care so much about Bitcoin self custody attack surface and why put so much time into publishing a guide. Heres my response:
Two fold:
1. To help bitcoin succeed. Bitcoin requires a critical mass of educated users that can hold base layer bitcoin safely and independently without getting rugged by psy ops and vendors and influencers (trusted 3rd parties eventually equivocates to getting rugged by nation states a la 6102)
2. To help actual people protect themselves from having their savings stolen by opportunistic wolves and snakes
















