4 ms·
"So, a database which history could be cryptographically audited." Doesn't git already meet that requirement?
by arethuza 10y ago
"So, a database which history could be cryptographically audited."
Doesn't git already meet that requirement?
- alexjarvis 10y agoNo because it's cheap to produce hashes for git.
- valarauca1 10y agoIt is cheap to make GIT hashes but it remains impossible to day to generate git collisions. The cost of hashing only has to do with the creation of blocks. Which blocks are not required to be cryptographically verifiable.
- alexjarvis 10y agoHow are blocks not required to be cryptographically verifiable?
- davidgerard 10y agoYes. I predict that in 2017 there will be many "business Blockchain" products that will be a transaction ledger in a Merkle tree - because this is actually really good and a useful idea! - and that developers will be able to tell buzzword-prone management "oh, we've been using, ahh, blockchain-related technologies since 2005!" cos they use git.