Again, find the difference. Each block(commit object) has its content(blobs and trees) and metadata like parent blocks(commit objects), time(and message). So one commit corresponds only to one history.
Still haven’t found it. You suddenly started talking about consensus protocol. Bitcoin consensus protocol sets last block(HEAD in git) to block with longest history.
Ive not suddenly started talking about consensus protocols. Yes, selecting the next (not necessarily longest) block is part of that consensus, but so is checking that the data contained in a block is cryptographicly sound and is following the rules of that specific blockchain. That second part is not native to GIT.
If you like, you can think of blockchain as a subset of GIT that includes additional constraints.
uis@lemm.ee 6 months ago
Again, find the difference. Each block(commit object) has its content(blobs and trees) and metadata like parent blocks(commit objects), time(and message). So one commit corresponds only to one history.
Knock_Knock_Lemmy_In@lemmy.world 6 months ago
But git can branch in multiple forks and states of the database. Blockchain has mechanisms to ensure there is convergence to one state.
uis@lemm.ee 6 months ago
Still haven’t found it. You suddenly started talking about consensus protocol. Bitcoin consensus protocol sets last block(HEAD in git) to block with longest history.
Knock_Knock_Lemmy_In@lemmy.world 6 months ago
Ive not suddenly started talking about consensus protocols. Yes, selecting the next (not necessarily longest) block is part of that consensus, but so is checking that the data contained in a block is cryptographicly sound and is following the rules of that specific blockchain. That second part is not native to GIT.
If you like, you can think of blockchain as a subset of GIT that includes additional constraints.