Explaining Blockchains to Developers
erickhun.com
Explaining Blockchains to Developers
1–10 of 44 posts
Re: Explaining Blockchains to Developers
#2Re: Explaining Blockchains to Developers
#3Re: Explaining Blockchains to Developers
#4Re: Explaining Blockchains to Developers
#5This article fails to mention one very fundamental property that makes blockchains interesting (and is the motivation for their design): The prevention of double-spend.
Else, you would just send a transaction updating the sender's and receiver's accounts, and there would be no double spent either.
You can build robust currency systems that are only partially decentralized, and partially distributed.
Re: Explaining Blockchains to Developers
#6OK, now explain it to non developers who think "it's the future of currency".
IMHO I see it as a tool for reaching democratic agreement on anything. The data stored in the blockchain exist only as long as the whole network exist and the majority agrees about the data. It can be basically any type of data!
Also by this logic it could be compromisable by a large enough party. Since the whole existence is based on agreement and 50/50 scenario would only further splice the two groups, each following what they think is the "truth" or "correct".
By no means I'm not an expert on this topic and anyone who has PLEASE correct my if my understanding is skewed. Thanks
Re: Explaining Blockchains to Developers
#7Re: Explaining Blockchains to Developers
#8Huh?
Re: Explaining Blockchains to Developers
#9If you have to ask what blockchains are, then it's not the tool you need.
If someone is telling/selling you blockchains, then you're talking to a cargo cultist.
Re: Explaining Blockchains to Developers
#10>In simple words, it’s a slow database. Huh?