I haven't seen the recent crop of materials, but I grocked it watching a 60 minute or so video presentation which I think was from someone at Mozilla. Oh, here it is: https://vimeo.com/27177893
I'll check out the video when I have time tonight.
Where I disagree is that I don't believe that all ideas/concepts can be made "easy to understand" to a general audience. Many concepts - especially those technical in nature - simply require a large amount of background knowledge to understand.
You can be the best mathematics teacher in the world, but you won't be able to (and no one expects you to) make the Riemann hypothesis widely understood to the general public. It's just not feasible. And I posit that Bitcoin (whilst maybe not as technical as the Riemann hypothesis) similarly requires a large amount of background knowledge and is not an "easy" concept to understand in 30 minutes.
The good news is that there are millions of things that people use every day that they don't understand - cars, computers, TVs - in fact, due to the specialization of knowledge, most things people encounter they do not fully understand. I don't think this is a big deal.
How long have you spent looking into it?
I wrote an academic paper on Bitcoin; now, I don't understand e.g. the detailed cryptanalysis of SHA256, which it uses. But I've a pretty solid understanding of how, given the availability of such hashing functions, and assuming they live up to their promises, you build a distributed ledger from them, and what some of the properties of that ledger might be. Not every implementation detail, but the high level principles.
I reckon most folk with degree or grad level CS education (or equivalent) would get to around that point in a few weeks (full-time?) study, probably less. (Given we can read the Bitcoin paper, nice explanations of it etc - not if we had to invent it ourselves.) I even think I've explained the main principles successfully to technical friends over the course of a few hours.
Yes, you don't just read a blog and understand how the whole system works, but thats true of many systems. Compare understanding Paxos (I'd say this is harder?), or DynamoDB, etc.
IMO there's nothing especially mysterious about Bitcoin here. Its clever, and its too complicated to explain in a paragraph in a media article, but its not an order of magnitude more complex than comparable distributed systems.
On the other hand, understanding _why_ it works is difficult, as it requires understanding the hard math underlying the system. In fact, nobody knows _why_ it works, because, AFAIK, we do not know whether the hash functions used have the necessary properties (in fact, it is worse: we do not even know whether one-way functions exist, let alone that we can point to one)
Moreover, there's not much point in saying things like that to people who are trying to learn, as it adds nothing except to suggest that if someone doesn't understand this easily just by reading that paper, they might be a bit less capable than some of the rest of us.
http://www.michaelnielsen.org/ddi/how-the-bitcoin-protocol-a...
When I finally came to the realisation about what mining is actually doing and why it's necessary to reward miners (it actually keeps the entire network secure): mind = blown.
I think that lack of simple explanation is what has slowed down innovation around blockchain. A lot of developers simply don't understand fully what they are dealing with. The presentations were mediocre at best and the recurrent question was "How is this better than what people currently use?" Unfortunately, the answer was mostly, "It uses blockchain." I doubt that suffices.
Or maybe I'm just the daft one, I doubt so.
You understand the bitcoin software and how the system is built and functions, end to end? Cool, I'm jealous.
You think most other developers share that understanding? Given that in my experience most developers have only a so-so understanding of basic cryptography to begin with, I find that very, very dubious.
I just read the original whitepaper and it isn't exactly trivial. Statements of the form "Because we do X in the implementation, bitcoin has property Y" are where it takes a fairly strong knowledge to truly follow along with the logic. The implications of the methodologies are not obvious, or else this whitepaper (and by extension the identity of Nakamoto) wouldn't be quite so important.
http://www.righto.com/2014/02/bitcoins-hard-way-using-raw-bi... http://www.righto.com/2014/09/mining-bitcoin-with-pencil-and... http://www.righto.com/2014/02/bitcoin-mining-hard-way-algori...
I think it's difficult to create an all encompassing post for that reason. It's a bit like trying to describe how any application protocol works - can you assume knowledge of TCP/IP? Do you just black-box it? etc.
My contact details are in my profile and I'm happy to lend a hand if you think that might be useful.
You'll also need to know what Proof of work is, explained in https://en.wikipedia.org/wiki/Proof-of-work_system
See also https://en.bitcoin.it/wiki/Introduction, or the rest of the wiki, or the StackExchange site.
I am just now beginning to try to research it to really understand it, because despite being a developer and having a decent understanding of public-key cryptography, I am at a total loss to understand how this system works or achieves its apparent purposes.
My impression is that it's actually quite complex, and that the press (and developer community at large) is failing to really explain it in any meaningful way to people who don't already get it. Not that this is out of the norm with tech topics, but this is very flagrant.