Warning: mkdir(): No space left on device in /var/www/hottg/post.php on line 59

Warning: file_put_contents(aCache/aDaily/2025-07-22/post/librecryptography/--): Failed to open stream: No such file or directory in /var/www/hottg/post.php on line 72
Hash Chains @LibreCryptography
TG Telegram Group & Channel
LibreCryptography | United States America (US)
Create: Update:

Hash Chains

I
was wrong about my initial impression but also possibly on to something as it pertains to the hash tree that could be created with Blake.

Hash / Merkle Tree Concept

Rather than just creating an appended list (sort of like blockchain) and then adding an additional operation that merely hashes the last input, it feels like it would be prudent to have all of the values hashed together in some capacity.

So that means:

1) H = x

2) H(x)

3) H(H(X))

4) H(H(H(X)))

There's something that's missing in this construction.

Only way that this could work is if the generator of the hash chain kept at least a few values secret.

But it is impossible for this to be done in a way where all of those values are kept secret and this be seen as externally valid.

The only other way is to ensure that all of the values are public. But if you must do that then you need to devise another method that will require people to remain honest bc you've trapped off their avenues for "cheating".

This is why the write-up on the way that time is calculated on the blockchain is extremely fucking important - it is an objective source of randomness that keeps everyone honest if it can be adhered to.

The idea that I had about the UNIX time tracking was interesting, but ultimately one critical underpinning here (hmm...)

Hash Chains

I
was wrong about my initial impression but also possibly on to something as it pertains to the hash tree that could be created with Blake.

Hash / Merkle Tree Concept

Rather than just creating an appended list (sort of like blockchain) and then adding an additional operation that merely hashes the last input, it feels like it would be prudent to have all of the values hashed together in some capacity.

So that means:

1) H = x

2) H(x)

3) H(H(X))

4) H(H(H(X)))

There's something that's missing in this construction.

Only way that this could work is if the generator of the hash chain kept at least a few values secret.

But it is impossible for this to be done in a way where all of those values are kept secret and this be seen as externally valid.

The only other way is to ensure that all of the values are public. But if you must do that then you need to devise another method that will require people to remain honest bc you've trapped off their avenues for "cheating".

This is why the write-up on the way that time is calculated on the blockchain is extremely fucking important - it is an objective source of randomness that keeps everyone honest if it can be adhered to.

The idea that I had about the UNIX time tracking was interesting, but ultimately one critical underpinning here (hmm...)


>>Click here to continue<<

LibreCryptography




Share with your best friend
VIEW MORE

United States America Popular Telegram Group (US)


Warning: Undefined array key 3 in /var/www/hottg/function.php on line 115

Fatal error: Uncaught mysqli_sql_exception: Too many connections in /var/www/db.php:16 Stack trace: #0 /var/www/db.php(16): mysqli_connect() #1 /var/www/hottg/function.php(212): db() #2 /var/www/hottg/function.php(115): select() #3 /var/www/hottg/post.php(351): daCache() #4 /var/www/hottg/route.php(63): include_once('...') #5 {main} thrown in /var/www/db.php on line 16