Blockchain is pretty well defined.
Git doesn’t have update rules that are only valid if signed by a particular private key.
While blockchain is well defined, it in itself is not a product but a technology. I think what the other commenter is getting at is that simply saying something “is blockchain” means very little because what the blockchain does depends on the implementation, so when used in marketing it’s just a nebulous buzzword in that it doesn’t actually give you much information about what the product is. Same with terms like cloud, AI, virtual reality, etc.
Yes. There were a lot of companies selling “blockchain base” solutions where blockchain wasn’t really needed in the solution at all.
Then it was Metaverse based solutions. (I would argue VR is well defined)
Now it’s AI solutions.
But I think “cloud” is now post that marketing phase, and blockchain is heading that way.
Please share a source! I can’t find anything as robust as a whitepaper (the bitcoin whitepaper doesn’t use the term).
NIST informally defines it as:
A distributed digital ledger of cryptographically-signed transactions that are grouped into blocks. Each block is cryptographically linked to the previous one (making it tamper evident) after validation and undergoing a consensus decision. As new blocks are added, older blocks become more difficult to modify (creating tamper resistance). New blocks are replicated across copies of the ledger within the network, and any conflicts are resolved automatically using established rules.
Which git certainly meets this.
IBM informally defines it as:
Blockchain is a shared, immutable ledger that facilitates the process of recording transactions and tracking assets in a business network. An asset can be tangible (a house, car, cash, land) or intangible (intellectual property, patents, copyrights, branding).
Which git meets.
How does it “certainly meet it”? There is no consensus mechanism in git, new blocks are not replicated across the network, there is no network at all, git works offline. You can replicate changes with remotes but there is no “git network” in any similar sense. And conflicts are definitely not resolved automatically. And the git hashes are certainly not cryptographic.
That’s 4 ways it doesn’t meet the definition. You could maybe stretch the meaning of a network to make it 3.
Git is hash linked, not cryptographicly linked. Only cryptographicly valid changes are allowed to blockchain state. All data can be modified in git.
Yes. IBMs definition is bad and could equally apply to git. They’ve totally forgotten about the private key aspect.
I’ll see if I can source a better definition online, but make no promises.
Edit: https://aws.amazon.com/what-is/blockchain/ the last line is not applicable to Git
Oh a 3rd definition, that definitely hurts the case that blockchain is vague ill defined term. If it were a well-defined term, there would be whitepapers defining it like merkle trees or bitcoin. Blockchain is just a marketing term defined by businesses, not scientists or engineers and thus is vague and variable.
I also don’t think your definition is a very good definition. Do you think git fundamentally changes when it moves from sha1 to sha256? Or are you referring to the fact that the payloads of cryptocurrency’s blockchain is required to be signed (just like you can optionally require git commits to be signed)? I don’t think that’s fundamental to blockchain either.
Only cryptographicly valid changes are allowed to blockchain state. All data can be modified in git.
No. You can’t modify the chain in git. Each commit is an immutable snapshot of the repository. To change history you have to create a new hash and then broadcast that to everyone that they should stop using the old one. Depending in how your network is setup you may onky have to convince a centralized server, or you might have to convince 51% of the actors on your network or you may just choose to only form a network that agrees with you. You could alter bitcoin’s blockchain too, but you’d need 51% of the network to agree with you.
