Transaction

45230ff4e5d1ffab042cd1b00e31bce537e1da8c76ed6e69ed1d99f4d6fb059f
Timestamp (utc)
2024-03-22 12:42:43
Fee Paid
0.00000026 BSV
(
0.00692121 BSV
-
0.00692095 BSV
)
Fee Rate
10.26 sat/KB
Version
1
Confirmations
94,056
Size Stats
2,534 B

2 Outputs

Total Output:
0.00692095 BSV
  • j"1LAnZuoQdcKCkpDBKQMCgziGMoPC4VQUckMê<div class="post"><div class="quoteheader"><a href="https://bitcointalk.org/index.php?topic=1931.msg25064#msg25064">Quote from: zipslack on November 28, 2010, 08:53:00 AM</a></div><div class="quote">I suppose you are referring to the checkpoints? If so, as I understand it, they are only applied while verifying a block which has been downloaded. The contents of blk0001.dat and blkindex.dat are <i>never</i> checked by the client, because the client is designed to check that data <i>before</i> it gets written to those files.<br/></div><br/>Not quite true. &nbsp;"-checkblocks" (CheckBlock()) performs quite a few checks on the contents of blk0001.dat / blkindex.dat. &nbsp;AcceptBlock() does a bit more, adding context, but not much more. &nbsp;But let's ignore that for the moment.<br/><br/>I think a more important point you're missing is that <b>nobody is proposing that verification be skipped</b>. &nbsp;The bitcoin code is quite capable of verifying and indexing untrusted blk0001.dat data. &nbsp;It would just need a few modifications to behave sensibly if blkindex.dat is missing.<br/><br/>The proposal is simply:&nbsp; don't download massive amounts of uncompressed data using a protocol (bitcoin P2P) that wasn't designed for bulk data transfer.<br/><br/><div class="quoteheader">Quote</div><div class="quote">As satoshi indicated in this thread,<br/><br/><div class="quoteheader"><a href="https://bitcointalk.org/index.php?topic=1931.msg24438#msg24438">Quote from: satoshi on November 25, 2010, 05:51:39 PM</a></div><div class="quote">Doing your own verifying and indexing is the only way to be sure your index data is secure. &nbsp;If you copy blk0001.dat and blkindex.dat from an untrusted source, there's no way to know if you can trust all the contents in them.<br/></div></div><br/>The client is clearly capable of verifying the cryptographic integrity of blk0001.dat from an untrusted source, because it does that for blocks coming in over the network, and blk0001.dat contains... serialized blocks originally received from untrusted sources over the network.<br/><br/>It does not seem overly difficult to pass in blk0001.dat file position data to ProcessBlock(), and simply skip the WriteToDisk() storage call in downstream callee AcceptBlock().<br/><br/></div> text/html
    https://whatsonchain.com/tx/45230ff4e5d1ffab042cd1b00e31bce537e1da8c76ed6e69ed1d99f4d6fb059f