0 sats \ 0 replies \ @SatsJoseph 8 May 2023 \ parent \ on: We are Trezor, the open source hardware wallet pioneer. Ask us anything! bitcoin
- secure and open source random number generator
- always-offline environment (both for private key storage and signing)
- the attack surface in a specific device such as a hardware wallet is much more narrow than a general-purpose device (laptop, phone)
We usually have Pilsner Urquell and Birell as a non-alcoholic variant :-). And we actually have a Trezor Beer Fund where satisfied users can send us tips! https://trezor.io/support/a/trezor-beer-fund
Yes, we aim to popularize Shamir Backup more in the future through various types of educational content such as our recent tutorial video:
https://www.youtube.com/watch?v=W54g3T4WyIg
I think it's unfortunate to say the least as such users could potentially become a target. Users should instead be guided to good opsec practices.
- that bitcoin is actually stored on the device (while the thing that matters the most is the recovery seed)
- that passphrase is a sort of a password that can be reset by us (while it isn't stored anywhere, not even the device, and cannot be reset)
Trezor is never shipped with a preloaded firmware. Users have a choice to choose either universal or bitcoin-only firmware during the onboarding.
What are we doing in Ghana? The answer is supporting local bitcoin meetups and educating people about bitcoin and self-custody (the curriculum for the Trezor Academy is stricly bitcoin-only).
That’s a great question that should be asked and discussed more! Personally I believe that Shamir backup has qualities that are quite useful for inheritance planning. I have actually written an article on how to approach inheritance with Shamir backups: https://bitcoinmagazine.com/technical/protecting-bitcoin-shamir-backup. I think the crucial thing is to have some sort of “treasure map” that will become accessible to the family in the case something happens to you. Such treasure map would explain the nature of the inheritance and the location of the Shamir shares (not necessarily precise addresses to prevent theft if an “evil maid” discovers it). The precise inheritance plan is an individual thing, but I think there are some basic recommendations everyone should follow, as I describe in the linked article.
As for Trezor’s plans around this topic: we’d like to inform our users more about the use cases for Shamir backups such as this one.
GENESIS