<blockquote>
  <p>How could I know what of external wallets (private keys) I should use to send btc using libraries assuming it usually changes?</p>
</blockquote>

<p>You can't without scanning the entire blockchain to find out what addresses have been used before.</p>

<blockquote>
  <p>How could I basically send BTC to some wallet having only seed hex or 12 words?</p>
</blockquote>

<p>You can't without scanning the entire blockchain to find the UTXOs that you can spend.</p>

<hr>

<p>In general, a mnemonic phrase or a seed is not enough to be able to send Bitcoin to someone else. You need to generate keys and scan the entire blockchain to find UTXOs that you can spend. This is why many wallets store more than just the seed phrase in their wallet files.</p>

CC BY-SA 4.0
2018-06-01T05:35:02.357Z
Thanks for your answer. What keys should I generate to scan for UTXOs? I can generate all the private keys for wallets... Btw I have xpub and xpriv keys from wallet.
Dj Solona
CC BY-SA 4.0
2018-05-31T22:04:54.680Z
2018-05-31T22:04:54.680Z
Ava Chow
<p>This Bitcoin <a href="https://github.com/libbitcoin/libbitcoin/wiki/Altcoin-Version-Mappings#7-bitcoin-btc-bip-3944-technology-examples" rel="nofollow noreferrer"><strong>example</strong></a>, posted almost 3 years ago, should succinctly answer most your questions. BIP 44 paths levels (<strong>m or M / purpose' / coin_type' / account' / change / address_index</strong>) can be tweaked as needed. Some of the adjacent examples demonstrate how BIP 32/39/44 technology can be extended to other altcoins.</p>

<p>For a given coin type, blockchain scanning of synthesized addresses, associated with a given sequential <strong>M</strong>, is required to identify applicable UTXOs. For a given M with associated UTXOs, there is a companion <strong>m</strong>. HD wallets applications innately perform such bookkeeping operations.  HD wallets also tend to use compressed private keys, compressed public keys, and compressed addresses to minimize transaction fees.</p>

<p>Either use something like <strong>bx</strong> (bitcoin-explorer) to synthesize the keys of the other wallet and use the synthesized addressed to send funds, or use commercial products like Trezor, Ledger, Jaxx, Mycellium... However, HD paths and details for Ethereum and Monero will vary and will introduce seed word interoperability issues. </p>

<p>For example, Ledger Ethereum paths do not follow the BIP 44 Standard. Also, details for standardizing Monero key synthesis from BIP 39 seed words is non existent.  This is likely to create seed word interoperability issues between existing Ledger support and future Trezor support.</p>

<p>Existing functionality at <a href="https://github.com/bholben/seaweed" rel="nofollow noreferrer">https://github.com/bholben/seaweed</a> can be extended to accomplish what you desire on a old decommissioned permanently air-gapped iOS or Android device to synthesize addresses for another HD wallet.  </p>

CC BY-SA 4.0
2018-09-07T19:03:10.047Z
2018-09-07T19:03:10.047Z
skaht
<p>I’m interested in sending BTC from wallet to another and probably automate it through some libraries.</p>

<p>I have a question: if I have a seed hex or 12 words I can generate all my wallets (addresses, private keys) with BIP39 mnemonic tool.</p>

<p>How could I know what of external wallets (private keys) I should use to send btc using libraries assuming it usually changes?</p>

<p>How could I basically send BTC to some wallet having only seed hex or 12 words?</p>

<transactions><bitcoin-core><blockchain><seed><mnemonic-seed>
Sending BTC using Seed Hex or mnemonic
Dj Solona
# Sending BTC using Seed Hex or mnemonic

(Asked by: username_0 on 2018-05-31)

I’m interested in sending BTC from wallet to another and probably automate it through some libraries.

I have a question: if I have a seed hex or 12 words I can generate all my wallets (addresses, private keys) with BIP39 mnemonic tool.

How could I know what of external wallets (private keys) I should use to send btc using libraries assuming it usually changes?

How could I basically send BTC to some wallet having only seed hex or 12 words?

**Tags:** transactions, bitcoin-core, blockchain, seed, mnemonic-seed


---

## 2 answers

### Answer by username_1 on 2018-05-31. Score: 2

> How could I know what of external wallets (private keys) I should use to send btc using libraries assuming it usually changes?

You can't without scanning the entire blockchain to find out what addresses have been used before.

> How could I basically send BTC to some wallet having only seed hex or 12 words?

You can't without scanning the entire blockchain to find the UTXOs that you can spend.

---

In general, a mnemonic phrase or a seed is not enough to be able to send Bitcoin to someone else. You need to generate keys and scan the entire blockchain to find UTXOs that you can spend. This is why many wallets store more than just the seed phrase in their wallet files.

> **Comments:**
> **username_0**: Thanks for your answer. What keys should I generate to scan for UTXOs? I can generate all the private keys for wallets... Btw I have xpub and xpriv keys from wallet.  

---

### Answer by username_2 on 2018-09-07. Score: 0

This Bitcoin [**example**](https://github.com/libbitcoin/libbitcoin/wiki/Altcoin-Version-Mappings#7-bitcoin-btc-bip-3944-technology-examples), posted almost 3 years ago, should succinctly answer most your questions. BIP 44 paths levels (**m or M / purpose' / coin\_type' / account' / change / address\_index**) can be tweaked as needed. Some of the adjacent examples demonstrate how BIP 32/39/44 technology can be extended to other altcoins.

For a given coin type, blockchain scanning of synthesized addresses, associated with a given sequential **M**, is required to identify applicable UTXOs. For a given M with associated UTXOs, there is a companion **m**. HD wallets applications innately perform such bookkeeping operations. HD wallets also tend to use compressed private keys, compressed public keys, and compressed addresses to minimize transaction fees.

Either use something like **bx** (bitcoin-explorer) to synthesize the keys of the other wallet and use the synthesized addressed to send funds, or use commercial products like Trezor, Ledger, Jaxx, Mycellium... However, HD paths and details for Ethereum and Monero will vary and will introduce seed word interoperability issues.

For example, Ledger Ethereum paths do not follow the BIP 44 Standard. Also, details for standardizing Monero key synthesis from BIP 39 seed words is non existent. This is likely to create seed word interoperability issues between existing Ledger support and future Trezor support.

Existing functionality at <https://github.com/bholben/seaweed> can be extended to accomplish what you desire on a old decommissioned permanently air-gapped iOS or Android device to synthesize addresses for another HD wallet.


---

