Transaction

2656f91fd7592c9b5e25993ac4fa2d9286f9c2b60cbd5400a49933bc5730b8d4
Timestamp (utc)
2024-03-28 19:11:54
Fee Paid
0.00000011 BSV
(
0.00513043 BSV
-
0.00513032 BSV
)
Fee Rate
10.24 sat/KB
Version
1
Confirmations
92,777
Size Stats
1,074 B

2 Outputs

Total Output:
0.00513032 BSV
  • j"1LAnZuoQdcKCkpDBKQMCgziGMoPC4VQUckM6<div class="post"><div class="quoteheader"><a href="https://bitcointalk.org/index.php?topic=691.msg7290#msg7290">Quote from: jgarzik on August 03, 2010, 06:12:28 PM</a></div><div class="quote">A good way to prevent long-chain takeover is to store the signature of the last-known "good" block in each bitcoin release binary.<br/><br/></div><br/>But that is only as good as the trust you have in the distribution channels, which are being discussed in other threads. If a compromised client was to be served as an upgrade, and most running clients would be using this version, then a new chain would replace the old one. What would happen when, after some time, the attack was disclosed and new clients with the real block chain signatures were run? Would the old (real) chain still be alive and replace the bogus one?</div> text/html
    https://whatsonchain.com/tx/2656f91fd7592c9b5e25993ac4fa2d9286f9c2b60cbd5400a49933bc5730b8d4