pull down to refresh
Calle´s report. What impacts me the most is his commment on LN.
gained a ton of new insights working in bitcoin red team that i wish i could share without vague posting. but this is what i got anon.
- we’re experiencing a massive collision between decades of human open source slop against 2 weeks of kimi k3 (not good)
- everything is broken, bitcoin is burning
- bitcoin is becoming stronger through this
- bitcoin is the obvious first target but the rest of the world will follow shortly
- sometimes old things need to burn so new things can grow on healthy soil
- humans should never code in c (just stop)
- lightning is complicated and is more broken than the average (sorry)
- verification is free. we used to complain about slop PRs. then about slop security audits. if you can’t handle the information overload, stop complaining and use AI to sort through it.
- those projects that started AI audits months ago are in a completely different position than those who didn’t
- projects need their own AI audit pipeline going into the future
- the burden for a developer to keep software safe and secure is pretty stressful and not for everyone. it has become a lot more stressful now.
- unmaintained projects are most probably broken, don’t rely on them. i’d rather one-shot it myself with a modern AI
- multiple concurrent, diverse human approaches have proven to be the best vulnerability search method
- external red teaming will probably have to continue forever
- we’ve basically completed a basic scan of virtually the entirety of bitcoin open source. the low hanging fruit is done.
- we’ve reported a ton of real critical and high vulnerabilities. project maintainers across the board have validated our findings.
- response speed is very different across projects and shows how healthy each project is. i recommend acting fast these days.
- red team etiquette matters. if you don’t disclose responsibly, boast on twitter about your findings on a particular project, or make indications about the nature of particular findings, you’ve disqualified yourself as a serious security researcher. trust is the most important factor in this game. if you lose it, it’s very hard to win it back.
- did i mention that humans should not code in c?
The question is if normies are prepared for the switch. If I am not mistaken they are talking of a new app and therefore you need to migrate the funds. The thing is that there are other services linked to WoS, or even the user name.
Following BIP-110 live at https://bip110.dinerosinreglas.com/
What will be the future of the Coldcard company?
Are they obliged to keep updating the firmwares, do they have funds to keep all the R&D, are they guilty or did they took part of the btcs, should they continue till a deadline, will people forget the issue and buy the new models by learing how to use dice?
How many layers of Bitcoin do you use so that the received do not know your btc stack?
From cold to hot, from hot to LN? What if is a normal btc tx?
That is one of the motives of my question. So, he used nothing but entropy on a windows (not lynux?) OpenSSL and never got hacked. I don´t know if BIP-39 words existed back then, or passphrases, or other stuff. The UI of the first ¨wallet¨ was as simple as send or recieve, and the access to it was secured by a password or what? I guess his whole PC was the hardware wallet, never mixed with nothing else.
ECash Alpha will start in 1 hour:
https://ecash.com/fast-facts
How does a Hard Fork on Bitcoin works? They say you can claim 1:1 BTC to ECX.