Recently we’ve encountered interesting edge cases where
Receive Payments API V2 users had long runs of unused addresses, which makes funds paid to later addresses not display within the wallet. We’re taking a proactive approach to prevent this from happening, and in this post we’ll explain these changes and their impact on our API users. Users may also have received an email version of this update.
The problem
When you make requests from the Receive V2 API, we create new addresses for you sequentially, ensuring that you don’t give two users the same address. If you request several addresses on behalf of your users without any of them making a payment, this will leave empty gaps between addresses with funds. This is fine, unless this consecutive empty address gap reaches 21 addresses or more.
Most wallet software will only look ahead 20 addresses from the highest index address it can
see (
due to the BIP 44 standard we are following). Let’s say you get paid to the first address, address 1 — the wallet will look ahead 2-21 addresses to see if there are any additional funds or transaction history in those addresses. If it doesn’t find anything, it will stop looking. So, if you get paid to address 22, the wallet software will not
see the funds because it stopped at 21. However, if you get paid to address 2, the wallet software will look ahead addresses 3-22, see the funds that were sent to the address 22, and then look an additional 20 ahead (addresses 23 – 43).
Terimakasih anda telah membaca artikel tentang Receive Payments API Update blockchain: Address Gap Limits. Jika ingin menduplikasi artikel ini diharapkan anda untuk mencantumkan link https://tradingforexlive.blogspot.com/2017/07/receive-payments-api-update-blockchain.html. Terimakasih atas perhatiannya.