y² = x³ + 7

"d3d11c1d33d3ff6ab2e61191afed653933541a0c83fbef3fe79ead7dd88d85fbf42f346606011ad41f6e422e7aad703a41b94a9addbf0a82a14f8c4745b9dae8"

Last Notes

2026-08-02 19:47:03 UTC

- reply

I know what supply chain attack is, but Trezor implements some counter measures so I am asking you what type of attack you mean exactly. For example, Trezor devices have Trezor's public keys embedded directly in hardware, so if the firmware of the device was tempered, the device integrity check would fail.

2026-08-02 19:33:56 UTC

- reply

What do you mean by that exactly? Would they temper the manufacturing/shipment?

2026-08-02 07:33:00 UTC

- reply

It's not. More Bitcoin were lost due to people trying to outsmart the cryptography. This CC "hack" is nothing more than a stupid error that should have been caught by testing. The mistake is really simple and so is it's exploitation method. Literally the same thing already happened in Bitcoin's history many times (Libbitcoin explorer, Blockchain.info, Java's SecureRandom bug, ...). Using a hardware TRNG (for example thermal noise) and testing your implementation would prevent all of this.

2026-08-02 06:55:15 UTC

- reply

Extreme use cases are important, permissionless P2P networks are fragile and that's why we need to have a rock solid consensus rules. BIP110 is broken by design.

2026-08-02 06:45:07 UTC

- reply

I don't think that's a good lesson since casual users should not have to do that for UX reasons and placing the entropy generation in the hands of casual users will end badly.

2026-08-01 20:22:37 UTC

- reply

Yeah, don't trust, verify, but at some point you have to trust something/somebody. Hardware wallets are the best way to securely store your sats and Trezor simply makes the best ones, they are not amateurs. The 12 years old Trezor One (without any secure element or ARM enclave) is still safe against overwhelming majority of attackers. 🤷‍♂️

2026-08-01 20:09:12 UTC

- reply

Just use Trezor

2026-07-25 20:35:06 UTC

- reply

Democracy?

2026-06-28 17:34:10 UTC

- reply

What was the prompt?

2026-06-28 07:31:23 UTC

- reply

Knotters lying as usual