Transaction

649277f4e5dbeceb57fc09b4c8d4724ca7401bb10e8a63a3d24d5514c1ed7a9c
Timestamp (utc)
2024-03-22 12:35:25
Fee Paid
0.00000016 BSV
(
0.00699703 BSV
-
0.00699687 BSV
)
Fee Rate
10.53 sat/KB
Version
1
Confirmations
92,112
Size Stats
1,519 B

2 Outputs

Total Output:
0.00699687 BSV
  • j"1LAnZuoQdcKCkpDBKQMCgziGMoPC4VQUckMó<div class="post"><div class="quoteheader"><a href="https://bitcointalk.org/index.php?topic=788.msg8764#msg8764">Quote from: davidonpda on August 11, 2010, 04:19:43 PM</a></div><div class="quote"><div class="quoteheader"><a href="https://bitcointalk.org/index.php?topic=788.msg8761#msg8761">Quote from: gavinandresen on August 11, 2010, 04:10:56 PM</a></div><div class="quote">+ require some proof-of-work as part of the client-to-client connection process (helps prevent 'Sybil' attacks).<br/></div><br/>Isn't that a brilliant idea? Like hashcash? <br/><br/>You would be required to hash the string of the transaction, with a proof of work, that would say, take 5 seconds to calculate on a modern PC. Checking the POW just like in bitcoin would be easy and very quick for the receiving machines, but would stop a flood attack of random data without the attacker having limitless CPU power. <br/></div><br/>I was actually thinking of a minute or three of proof-of-work on initial connection, not when submitting a transaction, but requiring some proof-of-work for every transaction submitted into the network IS a very interesting idea!&nbsp; Should be straightforward to implement, too (add a nonce and either a full or partial hash to the transaction)...<br/></div> text/html
    https://whatsonchain.com/tx/649277f4e5dbeceb57fc09b4c8d4724ca7401bb10e8a63a3d24d5514c1ed7a9c