Losing fund: Creation of the son address in the HD letter pocket with false knot path
As a software developer, you are probably familiar with creating Bitcoin addresses using Hashcash or BIP32. When working with the HD letter bag, however, there is an essential step that can lead to lost means: Generate a subordinate address without specifying the correct knot path.
The problem: path of the wrong node in the HD portfolio
In the HD letter bag it is necessary to specify the path of the knot /0
when generating a subordinate address. This is crucial because the path of the node determines which Bitcoin core portfolio is to be used for the transaction. If the path of the node is not correct, the transaction rules out by the recipient’s portfolio or is rejected.
The problem: lack of path of the knot in the HD BIP32 portfolio
Unfortunately, many developers make this mistake without realizing it. When generating a subordinate address with BIP32, the path of the node /0
must indicate, which specifies the local Kern -Bitcoin portfolio. However, if you forget to record this decisive part of the address, the transaction fails or is rejected.
Consequences: Fund lost
This supervision can lead to lost means for several reasons:
Solution: correctly specify the path of the node correctly **
To avoid these problems, be sure to follow these steps:
1
2
.
Best Practice: Avoid lost funds
To prevent lost funds in the future:
According to these guidelines and the awareness of the importance of the knot path, it is possible to minimize the risk of lost funds that are connected to the generation of addresses for false children in the HD letter pocket.