Seed restore from one wallet to another

Seed restore from one wallet to another

Researching about restore walletS using seeds, I have one question:

  • I have 1 Jaxx wallet and the seed assigned to it.
  • Then, let´s say that I find another wallet that I like more, that supports the same cryptocurrencies that I had in Jaxx and also the same seed protocol (BIP39)

Can I restore my previous wallet (basically, the same cryptocurrencies, amounts, addresses...) in the new wallet, using the seed that Jaxx provided to me?

Then, there is one more question that comes to my mind...If the answer for the first question is "Yes": Can I use two wallets at the same time that use the same seed?

https://ift.tt/2OhwxyK

Comments

Post a Comment

Popular posts from this blog

Bitcoin Core errors with database block

Bitcoin Core errors with database block I've had the follow issue: on one machine I've launced Bitcoin Core v0.16.0 and Litecoin Core v0.16.0. Each application work in separate datadir also each application have setted callback call for event walletnotify . For now I use both application with testnets. Recently, there have been frequent cases when these applications stop sending transactions, when restarting, an error occurs: "Corrupted block database detected. Do you whant to rebuild the block database now ?". It happens on both apps Bitcoin Core and Litecoin Core, after rebuild applications continue to work, but after a while it happens again Please help me, what I doing wrong? Thank you for any advice https://ift.tt/2z6j9rL
Read more

sendrawtransaction and txn-mempool-conflict

sendrawtransaction and txn-mempool-conflict When i sendrawtransaction to bitcoind, i get error (exceptions) 18: txn-mempool-conflict (use Bitcoin JSON-RPC denpamusic/php-bitcoinrpc ) But the transaction is sent to the network and is subsequently confirmed. Example one decoded transaction : https://jsfiddle.net/rn58a4j6/ then i send this transaction: 94ec12fc463230b4285a29b047608627c05572a4c6eabe6688a201ce49ae72f7 https://ift.tt/2MY2KP0
Read more