Timeline for How do I make multisig transactions using hardware wallets truly trust minimized?
Current License: CC BY-SA 4.0
4 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Apr 6, 2021 at 22:33 | comment | added | Donn Lee | I have a question about what is meant by using the trusted HWW for "general verification". Is this in the context of setting up the quorum and verifying the receive addresses, or sending to an address owned by the multisig quorum, or when signing/spending from a multisig UTXO? | |
| Apr 6, 2021 at 22:19 | comment | added | Donn Lee | The following info helped me understand the Trezor T: The Model T is stateless and doesn't store the XPUBs of the other cosigners. So, the computer must provide the XPUBs to the T. A malware infected computer could lie about / swap those XPUBs, so fw 2.1.8+ shows the cosigners' XPUBs on the T's screen for the user to manually verify (every transaction). Coldcard, Cobo, etc don't need XPUB verification for every transaction because they store the cosigners' XPUBs on the device when the quorum is setup (and you have verified the XPUBs at quorum setup time). | |
| Dec 24, 2020 at 18:32 | comment | added | m1xolyd1an | To minimize even more trust is to build the tx and sign it yourself in a raw transaction, but that opens up too many other pitfalls for most users. | |
| Dec 24, 2020 at 12:21 | history | answered | Michael Folkson | CC BY-SA 4.0 |