Timeline for Is double SHA-256 the best choice for Bitcoin?
Current License: CC BY-SA 4.0
13 events
when toggle format | what | by | license | comment | |
---|---|---|---|---|---|
Feb 14, 2021 at 19:48 | history | edited | Raoul722 | CC BY-SA 4.0 |
corrected spelling
|
Jan 11, 2021 at 17:35 | history | edited | kelalaka | CC BY-SA 4.0 |
added the first appearance of the trimming as countermeasure to length extension attack.
|
Jan 10, 2021 at 13:26 | vote | accept | Pinkovai Krisztian | ||
Jan 10, 2021 at 13:26 | vote | accept | Pinkovai Krisztian | ||
Jan 10, 2021 at 13:26 | |||||
Jan 9, 2021 at 23:22 | history | edited | kelalaka | CC BY-SA 4.0 |
added 6 characters in body
|
Jan 9, 2021 at 23:14 | history | edited | kelalaka | CC BY-SA 4.0 |
latex syntax
|
Jan 9, 2021 at 23:10 | history | migrated | from security.stackexchange.com (revisions) | ||
Jan 9, 2021 at 17:04 | comment | added | kelalaka | @Nayuki yes, my mistake. I need an updated, thanks, | |
Jan 9, 2021 at 16:47 | comment | added | Nayuki | "In March 2012, the standard was updated in FIPS PUB 180-4, adding the hash functions SHA-512/224 and SHA-512/256, and describing a method for generating initial values for truncated versions of SHA-512." -- en.wikipedia.org/wiki/SHA-2#Hash_standard | |
Jan 9, 2021 at 13:07 | comment | added | kelalaka | @SimonRichter The proof is easy just double hash, however, it can increase the race-attackers cost by double. Also, Satoshi may want to use it for the signature, too, instead of using many hash functions around. | |
Jan 9, 2021 at 12:44 | comment | added | Simon Richter | Optimizing for speed in a proof-of-work setup is kind of silly. | |
Jan 8, 2021 at 23:17 | comment | added | Pinkovai Krisztian | I wonder how collisions could be eliminated if that's what's missing from the puzzle.. | |
Jan 8, 2021 at 22:55 | history | answered | kelalaka | CC BY-SA 4.0 |