1
0
mirror of https://github.com/bitcoinbook/bitcoinbook synced 2025-07-03 21:32:37 +00:00

Edited ch05_wallets.adoc with Atlas code editor

This commit is contained in:
claylock 2023-10-27 13:12:10 +00:00
parent 8d3299e0f1
commit 35a25da746

View File

@ -1245,6 +1245,7 @@ When a wallet application has distributed all of the keys up to its gap
limit and none of those keys have received a payment, it has three limit and none of those keys have received a payment, it has three
options about how to handle future requests for new keys: options about how to handle future requests for new keys:
[role="less_space pagebreak-before"]
1. It can refuse the requests, preventing it from receiving any further 1. It can refuse the requests, preventing it from receiving any further
payments. This is obviously an unpalatable option, although it's the payments. This is obviously an unpalatable option, although it's the
simplest to implement. simplest to implement.