<p>That depends on the derivation path which was used for the xpub and derived address, to which the funds were sent to.</p>

<p>The xprv "owner" can scan "standard" derivation paths to determine whether these keys where used (funds were sent to these), by parsing the blockchain transaction history. If a standard BIP44 key derivation path schema was used, it can scan the following addresses by incrementing the index. </p>

<p>Let's say, the owner shared the xpub key <code>M/44'/0'/0'/0</code>. It can then search the following derivation paths for example to determine which one received funds.</p>

<ul>
<li><code>M/44'/0'/0'/0/0</code></li>
<li><code>M/44'/0'/0'/0/1</code></li>
<li><code>M/44'/0'/0'/0/2</code></li>
<li><code>M/44'/0'/0'/0/3</code></li>
<li>...</li>
<li>If a significant number of consequent keys are unused, the wallet may decide to stop the scan.</li>
</ul>

<p>If arbitrary derivation paths were used which are unknown to the "owner" instead of standard ones, the space to scan can be very large.</p>

CC BY-SA 4.0
2019-01-23T10:02:42.930Z
But actually, any string can be parsed to the path, if we use arbitrary query as the path, then we can generate counter less address.  I have two concerns here 1) Some address might generated by someone, but the owner don't notice that. 2) There will be too many useless UXTO in memory in long term.
Carpemer
CC BY-SA 4.0
2019-01-23T10:27:05.607Z
Yes if it is a nonstandard path it will be hard to recover the derived addresses.
James C.
CC BY-SA 4.0
2019-01-23T07:54:51.233Z
2019-01-23T07:54:51.233Z
James C.
<p>Suppose the owner of xpub share the xpub to others, and someone send some money to a xpub generated address.</p>

<p>If the owner of xprv does not know the path used to generate that new address, is that means money has lost forever and will always live in the UXTO.</p>

<address><address-generation><utxo>
The risk of sending money to a xpub generated address
Carpemer
# The risk of sending money to a xpub generated address

(Asked by: username_0 on 2019-01-23)

Suppose the owner of xpub share the xpub to others, and someone send some money to a xpub generated address.

If the owner of xprv does not know the path used to generate that new address, is that means money has lost forever and will always live in the UXTO.

**Tags:** address, address-generation, utxo


---

## 1 answers

### Answer by username_1 on 2019-01-23. Score: 0 | Accepted answer

That depends on the derivation path which was used for the xpub and derived address, to which the funds were sent to.

The xprv "owner" can scan "standard" derivation paths to determine whether these keys where used (funds were sent to these), by parsing the blockchain transaction history. If a standard BIP44 key derivation path schema was used, it can scan the following addresses by incrementing the index.

Let's say, the owner shared the xpub key `M/44'/0'/0'/0`. It can then search the following derivation paths for example to determine which one received funds.

* `M/44'/0'/0'/0/0`
* `M/44'/0'/0'/0/1`
* `M/44'/0'/0'/0/2`
* `M/44'/0'/0'/0/3`
* ...
* If a significant number of consequent keys are unused, the wallet may decide to stop the scan.

If arbitrary derivation paths were used which are unknown to the "owner" instead of standard ones, the space to scan can be very large.

> **Comments:**
> **username_0**: But actually, any string can be parsed to the path, if we use arbitrary query as the path, then we can generate counter less address.  I have two concerns here 1) Some address might generated by someone, but the owner don't notice that. 2) There will be too many useless UXTO in memory in long term.  
> **username_1**: Yes if it is a nonstandard path it will be hard to recover the derived addresses.  

---

