Blockchains explained visually (part 1 of 2)
unwttng.com
unwttng.com
First time I've seen that. That should really be the standard for any author who decides to pepper their articles with 'memes' and other unrelated distractions.
Perhaps this is a cultural or generational thing that I am interpreting in the wrong way, but whenever I follow a link to a blog post filled with these kinds of distracting animated pictures I tend to just give up on the article after encountering the first one. I just can't fathom why someone who wishes to inform or enlighten readers on a certain topic feels the need to include a plethora of irrelevant distractions.
Nice to have a way to turn them off so I can give the article a chance based on its merits rather than the presence of memes.
A pity you site does not (yet :P ) have an rss feed for I'd like to follow your efforts.
Preach brother. It's memes and puns everywhere. I default to considering them lame attempts at wit. A ploy for attention. I want to believe they serve a small intermission but that's never the case.
If you're going to settle for this style of writing make the image or gif context relevant -- perhaps an illustration relating to the subject matter. Anything else is simply a distraction.
Nice article otherwise.
Would highly recommend watching this video for anyone who hasn't already.
It explains from ground up without getting complicated - it basically demystifies the whole thing completely
i give this to everyone - even to non technical people
[0]https://www.youtube.com/playlist?list=PLZHQObOWTQDNU6R1_6700...
https://softwareengineeringdaily.com/2017/10/12/blockchain-b...
The elliptic curve one is fascinating, where he has it implemented in like 30 lines of Python and no outside dependencies: https://www.youtube.com/watch?v=iB3HcPgm_FI
Edit: EC is a 2-part, second part is https://www.youtube.com/watch?v=U2bw_N6kQL8
Is that strictly required to understand that the entire chain is invalidated? Since blocks are in order, if block X's previous hash doesn't check out, can't we just assume that every block thereafter is also invalid? Effectively a fork has happened at X-1 block.
I'm guessing there are more dynamics (speed?) that come into this. Maybe the following questions will make it more clear:
1. How do the blocks update when there is a change in a past block?
2. In the real world, what process does a node use to validate the chain on an ongoing basis?
But does a blockchain, that is at the core of every(?) crypto currency really scale well?
Keeping the whole ledger constantly available seems rather storage and traffic intensive to me.
There are plans to fix this - sharding on Ethereum, Lightning Network on Bitcoin - but both are largely vaporware at this stage.
In practice, a lot of the transaction action happens inside the individual exchanges, not on the blockchain itself - so we already have a "level 1" and "level 2" system.
Also, there's issues of securing your bitcoins - "be your own bank" means "be your own extremely knowledgeable chief security officer". This is why even a lot of big holders keep a lot of money on exchanges (and lost lots in Mt. Gox). And why losses due to human error are extremely common.
The blockchain is more interesting than useful.
Can you expand on this a bit? Is it somewhat analogous to the role that dark pools play in the stock market?
So while the BTC blockchain is 137 GB in size, the UXTO is only 2.7 GB which easily fits in memory.
should be hexadecimal notation (that is, using 0-9 and a-f)
> There shouldn't be loads of them that start with an "A", or loads that end with ten "X"s, or anything like that.
This leads me to further doubt about the author's grasp of hexadecimal.
https://spectrum.ieee.org/static/special-report-blockchain-w...
It goes into permissioned ledgers and smart contracts, among other applications.
You should probably mention that what you are describing is a variant of a Merkle tree.