我们应该在钱包里预生成一批备用地址，需要新地址时取用。它们不大，多存一些也无妨。这样也能应对另一种情况，适用范围更广：某人做了备份，之后请求了一个新地址并用它收了一大笔款。也许应该分设几个队列，免得某一用途耗尽备用地址，导致其他用途无地址可用。
We should queue up a supply of pre-made addresses in the wallet to use when a new address is needed. They aren't very big, so it wouldn't hurt to have a lot of them. This would more generally cover the case also where someone backs up, then requests a new address and receives a big payment with it. Maybe there should be separate queues so one type of demand on addresses doesn't deplete it for the others.
这些地址会照常创建并存在常规位置，同时登记在另一个「已创建但从未使用」的名单上。请求地址时，从未使用队列队首的地址被发放，同时创建一个新地址加到队尾。
The addresses would be created and stored in the normal place, but also listed on a separate list of created-but-never-used addresses. When an address is requested, the address at the front of the never-used queue is handed out, and a new address is created and added to the back.
区块加载代码里有某种重新扫描机制，本来是用来修复有人复制了 wallet.dat 的情形。我需要确认，这个重新扫描机制能否从已经收到的区块中，重新找出那些因恢复钱包备份而丢失记录的收款。
There's some kind of rescan in the block loading code that was made to repair the case where someone copied their wallet.dat. I would need to check that the rescan handles the case of rediscovering received payments in blocks that were already received, but are forgotten because the wallet was restored.
当前版本尚未建立逐条校对状态记录。来源核验、历史审校与当前译文校对是不同事项。
译文内容版本：45c58f7529c8。用于比对文本，不代表校对等级或更新时间。
请填写对应原文、现译文、建议译法和理由。复制后通过你联系本站作者的渠道提交；此处不会自动发送。
