Transaction

c007ffd64ec09c37be678cc7eea8bf87bde684f322faac2db04ebcd7982d4832
Timestamp (utc)
2024-03-22 09:20:47
Fee Paid
0.00000016 BSV
(
0.00921722 BSV
-
0.00921706 BSV
)
Fee Rate
10.23 sat/KB
Version
1
Confirmations
94,370
Size Stats
1,564 B

2 Outputs

Total Output:
0.00921706 BSV
  • j"1LAnZuoQdcKCkpDBKQMCgziGMoPC4VQUckM <div class="post">Satoshi pointed out that my scenario still required the hash function to be broken. That is true, but I was surprised to learn how successful some have been with that. MD4 and MD5 are obvious examples. But work is well underway at colliding SHA-1 and siblings like SHA-256.<br/><br/>What hash is being used in this part of Bitcoin?<br/><br/>He is also skeptical that you could you could use something other than a generated keypair.<br/><br/>On this point, I'm pretty confident that it is a simple matter of mathematics. I didn't pay enough attention to this until I learned about "blind signing" of documents.<br/><br/>It turns out you can take a document and multiply it by a random number. Then have someone sign the jumbled file. Finally, you divide your random number out of their signature and the result is still a valid signature for the original document. Who'd figured that would work!<br/><br/>Anyway, if keypairs are only secure if they are based upon pairs of primes. Then nothing changes any of the math if the numbers are not prime. They are just much easier to factor.<br/><br/>I'd be perfectly happy for some crypto guy to prove me an idiot. It effects some features of a previous project I created that relied on the same association. I didn't think of this then either.</div> text/html
    https://whatsonchain.com/tx/c007ffd64ec09c37be678cc7eea8bf87bde684f322faac2db04ebcd7982d4832