0 sats \ 15 replies \ @Zepasta 22 Nov 2023 \ parent \ on: Looking for a post discussing 2:2 vs 2:3 multisig cold storage bitcoin
deleted by author
That sounds like just 3 copies of a single sig backup, probably bad.
reply
deleted by author
reply
This, I understand:
"When you add a passphrase to a seedphrase, it is essentially a new private key."
This, I don't understand:
"Using one seedphrase with three distinct passphrases is much, much more secure compared to using one seedphrase with just one passphrase"
When using one seed phrase with three distinct passphrases - at that point, aren't you creating 3 separate private keys?
reply
Yes.
- Seedphrase #1 + Passphrase #1
- Seedphrase #1 + Passphrase #2
- Seedphrase #1 + Passphrase #3
Its all different private keys.
reply
Very interesting, I'd like to see a deep dive write up on this. Wen @DarthCoin?
reply
What more guide than that simple explanation Onions gave you need?
Is literally this:
When you add a passphrase to a seedphrase, it is essentially a new private key.
reply
If I knew I wouldn't need it...
I may just have to fuck around with it on regtest a few different ways with different software to check for blindspots
reply
Why do you want to complicate your life with multisig?
Are you a big fucking company with multiple users that need the access to that wallet?
For a simple individual, is not really necessary man.
Keep it simple, damn it.
reply
I’m in this camp
reply
Why would you complicate your lift with singlesig?
Are you an individual that doesn't want:
- Protection against a 'single point of failure.'
- Protection against loss/theft of private keys.
- Protection against 'evil maid' attacks.
- Protection against physical attacks.
- Protection against phishing.
- Protection against malware.
- Protection against supply chain attakcs
- Protection against non-standardized passphrases
- Inheritance planning
reply
I am a simple man, using simple solutions, that I know how to manage them.
Access to my stash will be only one person and that is me.
I am not afraid of any of those you mentioned because I know how to avoid those situations.
Yes, not every other user could do that. But complicating things more than is necessary is not the best way.
I've avoided it for a long time as seeing it as not worth the complexity...
But it invites disaster to trust any single chip or piece of software with your families future... And it would take a lifetime to audit a whole stack myself.
The check and balance of 2:2 puts the trust back on myself
reply
Please try hacking this
