Replies (24)

And it is all because apparently BTClock is too similar to BLOCKCLOCK. Wtf? Also, they have not disclosed vulnerabilities in the SEs they use in the Mk4 and Q, and have not upgraded to a drop-in replacement that is a newer version without those vulnerabilities.
It is somewhat costly to exploit, but the fix is replacing one part with a drop in replacement. And this attack has existed since ~2005. Not informing users about this in general is pretty irresponsible.
Apparently “BTClock” is too similar to “BLOCKCLOCK” and consumers would totally get confused that BTClock is a Coinkite product… and so they took all their repos and their GH org down
That’s crap! Name is not even close. I could understand if it were ClockBlock or even BlockWatch but one references the coin the other the chain. Weak and very fiat, and not a good look especially considering the community that it’s aimed at.
No. I’m referring to the class of attack used. Laser fault injection has existed since 2005 and defenses can be implemented for the protection of the chip, such as light sensors. There have been 3 revisions to the ATECC chips and they still do not incorporate light sensors while your cheap credit card or transit pass does.
didn't they also use trezor's source code for the coldcard and when foundation used theirs for the passport, coinkite switched from open source to source verifiable? yeah, i'm not interested in what you're selling.. open source or bust