private key – Is it possible to use BitGo’s wallet with other software (Electrum or else), what is the used derivation path?

1 Mins read

BitGo wallets are based on a 2-of-3 multi-signature, the end user have access to:

- Public key (xpub) of the 3rd signer (as the main wallet xpub)
- Native Segwit (Bech32), bc1... addresses to receive BTC assets
- Private key/seed (BIP39) of the 1st signer (and public key xpub as well)
- Private key/seed (BIP39) of the 2nd signer (and public key xpub as well)

Seeds can be converted to private key here, BitGo provide it’s own recovery-tool (it’s debug infos can be used to get the xpub keys of the first and second signer).

Public xpub keys can be converted to Zpub (p2wsh) here or with Electrum with the command ./electrum.AppImage convert_xkey 'xpub...' 'p2wsh' --offline (Electrum and xpub-converter uses those specs and derivations paths).

While it is possible to import the BitGo wallet into Electrum without error, Electrum never generate the same receiving address as BitGo, Following this and this bitcointalk’s forum threads:

1. What is the derivation path used by BitGo Bitcoin wallet?
2. Is it possible to use BitGo wallet in any other software like Electrum or else?

Other related QA: 1, 2, 3, (note that I am using Bitgo’s wallet through Bitwala)

Source link

Related posts

Mercado Bitcoin parent company 2TM raises $50M, further cementing unicorn status

1 Mins read
2TM, the parent company of Brazilian cryptocurrency exchange Mercado Bitcoin, has received $50.3 million in fresh financing to expand its operations across…

trading - Crypto exchange - what do BTCUSD SELL and LTCBTC SELL mean?

1 Mins read
BTCUSD sell | | Trading Pair Advice from the Platform So BTCUSD is a trading pair in trading you always exchange something…

bitcoin-cli decodescript wrong output - Bitcoin Stack Exchange

1 Mins read
If I try to get info in genesis block, there is 1 tx: “scriptPubKey”: { “asm”: “0496b538e853519c726a2c91e61ec11600ae1390813a627c66fb8be7947be63c52da7589379515d4e0a604f8141781e62294721166bf621e73a82cbf2342c858ee OP_CHECKSIG”, “hex”: “410496b538e853519c726a2c91e61ec11600ae1390813a627c66fb8be7947be63c52da7589379515d4e0a604f8141781e62294721166bf621e73a82cbf2342c858eeac”, “type”: “pubkey”…

Leave a Reply

Your email address will not be published. Required fields are marked *