Transaction

65de2235e67ee0603bbee73dbb7b759ccfcdfd4e4f0bcab7b2b4a14dd9fdc692
Timestamp (utc)
2024-03-24 06:27:28
Fee Paid
0.00000016 BSV
(
0.01738305 BSV
-
0.01738289 BSV
)
Fee Rate
10.1 sat/KB
Version
1
Confirmations
102,265
Size Stats
1,584 B

2 Outputs

Total Output:
0.01738289 BSV
  • j"1LAnZuoQdcKCkpDBKQMCgziGMoPC4VQUckM4<div class="post">I think Satoshi proposed a protection against this in the following post:<br/><br/><div class="quoteheader"><a href="https://bitcointalk.org/index.php?topic=434.msg3770#msg3770">Quote from: satoshi on July 17, 2010, 04:27:39 PM</a></div><div class="quote">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.<br/></div></div> text/html
    https://whatsonchain.com/tx/65de2235e67ee0603bbee73dbb7b759ccfcdfd4e4f0bcab7b2b4a14dd9fdc692