Transaction

d92df28a5d9cd963b2159c0423eea3f76b2d8bfd78cecba74aeb58e11d0d407f
Timestamp (utc)
2024-03-28 07:24:16
Fee Paid
0.00000014 BSV
(
0.00608972 BSV
-
0.00608958 BSV
)
Fee Rate
10.63 sat/KB
Version
1
Confirmations
92,976
Size Stats
1,317 B

2 Outputs

Total Output:
0.00608958 BSV
  • j"1LAnZuoQdcKCkpDBKQMCgziGMoPC4VQUckM)<div class="post">We should queue up a supply of pre-made addresses in the wallet to use when a new address is needed.&nbsp; They aren't very big, so it wouldn't hurt to have a lot of them.&nbsp; This would more generally cover the case also where someone backs up, then requests a new address and receives a big payment with it.&nbsp; Maybe there should be separate queues so one type of demand on addresses doesn't deplete it for the others.<br/><br/>The addresses would be created and stored in the normal place, but also listed on a separate list of created-but-never-used addresses.&nbsp; 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.<br/><br/>There's some kind of rescan in the block loading code that was made to repair the case where someone copied their wallet.dat.&nbsp; 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.</div> text/html
    https://whatsonchain.com/tx/d92df28a5d9cd963b2159c0423eea3f76b2d8bfd78cecba74aeb58e11d0d407f