Transaction

0ae1032cb0e698fd566543a4e72cc68356288d681b0c296ebedef266e010f9e9
Timestamp (utc)
2024-03-22 01:10:52
Fee Paid
0.00000015 BSV
(
0.00225638 BSV
-
0.00225623 BSV
)
Fee Rate
10.06 sat/KB
Version
1
Confirmations
94,021
Size Stats
1,491 B

2 Outputs

Total Output:
0.00225623 BSV
  • j"1LAnZuoQdcKCkpDBKQMCgziGMoPC4VQUckM×<div class="post"><div class="quoteheader"><a href="https://bitcointalk.org/index.php?topic=360.msg3174#msg3174">Quote from: mcdett on July 15, 2010, 03:56:42 PM</a></div><div class="quote">...<br/><br/>2^255 Number of attempts to find the key value from above<br/></div><br/>1) Your equations don't take into account reversible computing advancements at all. These techniques could halve the search space by being able to take advantage of algorithms that traditional computers find impossible.<br/><br/>2) Your equations assume the algorithm is perfectly secure. Given that NIST is rather gung ho about developing SHA-3, I'm not terribly confident in that analysis.<br/><br/>3) An attacker does not need to find a specific key to compromise the system, they just need to find the keys to someone's wallet. If you want this to be a viable currency for Earth's population, plus corporate accounts, you drop the search space by 10^10 to 10^12.<br/><br/>That 2^256 search space could get whittled down to the 2^110 range by the end of the century. Assuming no major attacks on its integrity exist.<br/><br/>I'm not particularly sold on the technical soundness of this program, honestly. Why use SHA256 rather than Whirlpool or SHA512? </div> text/html
    https://whatsonchain.com/tx/0ae1032cb0e698fd566543a4e72cc68356288d681b0c296ebedef266e010f9e9