Re:Git hash function transition plan
by derekmhewitt on Friday December 01, 2017 @01:52AM
(#15822403)
Can someone explain why they would transition to a new hash function and not a block chain based system of tracking? If one of the goals of introducing a stronger hash function is signage of individual commits it seems like a block chain would be ideal.
[ Parent
| on HN ]
Re:Git hash function transition plan
by milkey_mouse on Friday December 01, 2017 @02:14AM
(#15822469)
Chains of Git commits are already a blockchain - at least, already a DAG, and to be more specific, they are both Merkle trees. Internally, each commit contains the hash of the previous commit it was based on:
$ git cat-file -p HEAD
tree e013f4d121199d60b70043f525aef4a7e641b5f6
parent 152bbb43b30ced1b32e9ed6f5ba2ac448de725b6
author Linus Torvalds <[email protected]> 1510512373 -0800
committer Linus Torvalds <[email protected]> 1510512373 -0800
Linux 4.14
You can even GPG sign each commit if you want to ensure authenticity. The other aspects of cryptocurrency blockchains don't really apply here: we don't need a single "true chain," in fact that's the point of branching.(Kids these days with their blockchains...)
git already is a hash linked datastore with the ability to sign your 'transactions'. The doc just points out that SHA1 is not a reliable hash to address objects anymore.