python-shamir-mnemonic VS staking-deposit-cli

You can recover with regular Linux/MacOS/Windows computer using this python script https://github.com/trezor/python-shamir-mnemonic

I suggest you do some further reading here https://github.com/trezor/python-shamir-mnemonic/issues/15

You can use Electrum or any third party wallet to enter the seed phrase. Otherwise with Shamir use https://github.com/trezor/python-shamir-mnemonic/

For even more security, shard the mnemonics with Shamir's secret sharing.

I do hope multisig gets easier in the comming years, but just the same, Shamir could also be standardized (the trezor team has already done the work and has the proposal and implementation) in the same way.

I mention that in the issue. The problem is this rationale seems unjustified because a 12-word BIP-0039 mneumonic encodes 16 bytes (128 bits) + 4 checksum bits of information before the passphrase comes in https://github.com/trezor/python-shamir-mnemonic/issues/40

However, the trezor reference implementation only allows to be given an existing secret in the form of hexadecimal seed key and not the actual mnemonic, as provided.

Trezor support Shamir backups (at least the model T does), but the cold wallet itself should be stored in the safety deposit box with the bank too (because if you know the device password and have the wallet with you then you are vulnerable to a wrench attack). You can generate one for an existing seed phrase with this command line tool also: https://github.com/trezor/python-shamir-mnemonic/

I am looking for a way to automatically create deposit data. So far I tried https://github.com/ethereum/staking-deposit-cli but although it offers a --non_interactive flag it still asks for an encryption password for the keystore files. Are there any other open source tools? I really don't want to fork and maintain my own version of the deposit cli.

First, you need to generate new keys using the staking deposit CLI software. It is recommended to do this on an offline computer. You can generate a new mnemonic phrase, but it seems simpler to reuse the same one as your other validators.

I am trying to setup a local devnet in my computer by using geth and prysm using https://docs.prylabs.network/docs/advanced/proof-of-stake-devnet. I can able to setup network with three execution nodes and three consensus nodes. Now I want to add new validators to the network. I tried with https://github.com/protolambda/eth2-val-tools and https://github.com/ethereum/staking-deposit-cli. I do get keystore-###.json and deposit_data-###.json files.

I’ve been trying to fix the initial language selection screen, and it displays right for me but not for a staking-deposit-cli dev. See https://github.com/ethereum/staking-deposit-cli/pull/325

Deposit cli will support it. See https://github.com/ethereum/staking-deposit-cli/issues/312

For those that are interested about the staking-deposit-cli PR: https://github.com/ethereum/staking-deposit-cli/pull/313

You can check this instructions: https://github.com/ethereum/staking-deposit-cli --eth1_withdrawal_address String. Eth1 address in hexadecimal encoded form