Ask Lemmy
A Fediverse community for open-ended, thought provoking questions
Please don't post about US Politics. If you need to do this, try [email protected]
Rules: (interactive)
1) Be nice and; have fun
Doxxing, trolling, sealioning, racism, and toxicity are not welcomed in AskLemmy. Remember what your mother said: if you can't say something nice, don't say anything at all. In addition, the site-wide Lemmy.world terms of service also apply here. Please familiarize yourself with them
2) All posts must end with a '?'
This is sort of like Jeopardy. Please phrase all post titles in the form of a proper question ending with ?
3) No spam
Please do not flood the community with nonsense. Actual suspected spammers will be banned on site. No astroturfing.
4) NSFW is okay, within reason
Just remember to tag posts with either a content warning or a [NSFW] tag. Overtly sexual posts are not allowed, please direct them to either [email protected] or [email protected].
NSFW comments should be restricted to posts tagged [NSFW].
5) This is not a support community.
It is not a place for 'how do I?', type questions.
If you have any questions regarding the site itself or would like to report a community, please direct them to Lemmy.world Support or email [email protected]. For other questions check our partnered communities list, or use the search function.
Reminder: The terms of service apply here too.
Partnered Communities:
Logo design credit goes to: tubbadu
view the rest of the comments
Probably nothing, but that depends on your definition. Let's look at the technicalities.
You have a number of crypto transactions that are bundled together into a block. Then you compute a hash - a checksum - for this block. If the data changes, then the checksum no longer matches. The trick that makes it a chain is to include the checksum of the previous block in the next block.
If someone manipulates the transaction history, they need to recalculate the checksum to match. But then they also need to change the following block and recalculate its checksum and so on.
This is a pruned down version of a Merkle Tree, which was thought up ~50 years ago. It doesn't have to be a chain. You can allow a block to have more than 1 succeeding block; making a fork. Blockchains are one use of that data structure. Wikipedia lists some others. Git, for example, also uses this.
The bitcoin maker knew to use this trick when he needed it. When Torvalds wrote git a few years before that, he also knew to use it.
When you ask about Blockchain specifically rather than Merkle Trees, you greatly limit what can be done with it. So there aren't a lot of uses left. Most people would say that a Blockchain is more than just a limited Merkle Tree. When you add in those features, you make it even more specific to the original application. So you are probably left with just crypto.