I have a security question that has been bugging me.
When a wallet broadcasts a Bitcoin transaction, we trust it's only sending the signature and transaction data. But how can we be certain that frag...
Cool! Many thanks @Dikaios1517 @karliatto @DETERMINISTIC OPTIMISM 🌞
I conclude from all your replies that:
🔸As a developer, you should verify the open-source code by:
1. Checking how the k value is generated. For any unique transaction, you should always get the same k value (Note: this will never happen after broadcasting the first transaction. Youll never get the exact same transaction again). For any different transaction, you should always get a different k value. (Note: E. g. Trezor uses RFC 6979 for generating deterministic k values.) This completely eliminates the risk of accidentally reusing a k value!
2. If code check passed, hash the downloaded firmware to confirm its integrity.
🔸Non-developers or ultra-paranoid users can perform a "signature test" against other devices. Sign the exact same transaction from two devices and compare them; the signatures should be completely identical.
🔸For ultimate protection that doesn't require verifying every update, use a multi-sig setup with hardware wallets from multiple manufacturers.
I conclude from all your replies that:
🔸As a developer, you should verify the open-source code by:
1. Checking how the k value is generated. For any unique transaction, you should always get the same k value (Note: this will never happen after broadcasting the first transaction. Youll never get the exact same transaction again). For any different transaction, you should always get a different k value. (Note: E. g. Trezor uses RFC 6979 for generating deterministic k values.) This completely eliminates the risk of accidentally reusing a k value!
2. If code check passed, hash the downloaded firmware to confirm its integrity.
🔸Non-developers or ultra-paranoid users can perform a "signature test" against other devices. Sign the exact same transaction from two devices and compare them; the signatures should be completely identical.
🔸For ultimate protection that doesn't require verifying every update, use a multi-sig setup with hardware wallets from multiple manufacturers.