Transaction

2e41548193e1f38c7bcdc5e55bd3d4e0e79bc893c44d41c3c991fcf1d942ef67
Timestamp (utc)
2024-03-25 07:00:12
Fee Paid
0.00000016 BSV
(
0.00044615 BSV
-
0.00044599 BSV
)
Fee Rate
10.38 sat/KB
Version
1
Confirmations
96,894
Size Stats
1,540 B

2 Outputs

Total Output:
0.00044599 BSV
  • j"1LAnZuoQdcKCkpDBKQMCgziGMoPC4VQUckM<div class="post"><div class="quoteheader"><a href="https://bitcointalk.org/index.php?topic=723.msg8007#msg8007">Quote from: Red on August 06, 2010, 11:08:28 PM</a></div><div class="quote">So for any new transaction, to verify it, you send it to the five closest nodes to each in-point on the transaction. They record the transaction and immediately tell you if they've seen a double spend. If any have, it's a bogus transaction, which gets broadcast to the other close nodes.<br/></div><br/>What happens when they disagree about which transaction happened first?&nbsp; Majority rule?&nbsp; Who decides what the majority is, and can it change if 4 of the five nodes leave the network and are replaced by another 5 nodes?<br/><br/>And if I know that I'm going to create a large transaction, can I do some work precomputing node IDs such that the transaction (which I haven't yet sent out) will hash to nodes that I control?&nbsp; &nbsp;If I control all the nodes storing the transaction, then I can just answer "yes, absolutely, that transaction is valid and hasn't been double-spent..."<br/><br/>The brilliant insight behind bitcoin is the distributed timestamping mechanism; everybody agrees on an order of transactions.&nbsp; I don't see how your scheme solves that problem.<br/></div> text/html
    https://whatsonchain.com/tx/2e41548193e1f38c7bcdc5e55bd3d4e0e79bc893c44d41c3c991fcf1d942ef67