Satoshi's paper never included the word.
I agree though that there is a lot of hype for "blockchain technology" and this seems like a weird use of it, since you already have a central third party that everyone has to trust.
They described the blockchain as an "ongoing chain of hash-based proof-of-work, forming a record that cannot be changed without redoing the proof-of-work"
[1] https://www.gov.uk/government/publications/introducing-govuk...
That aside, one of the identity partners is Verizon, which don't even do business in the UK. What's their incentive here? Why is giving my passport or driving license details to Verizon better than giving it to Government, a branch of which issued it in the first place? Frankly I think it's nuts and not a win for privacy.
Have you heard of the health benefits of being naked? Naked is so easy to clean. You never need to mend naked. Naked never goes out of style. Naked is easy to color coordinate.
It isn't entirely relevant to the emperor whether he succeeds in getting naked accepted as the latest fashion or not, as long as he succeeds in not getting laughed at. Being naked is ultimately survivable, being tricked is not.
Techies look upon the financial world and find its messy structures
hard to reconcile with the physical reality around them.
Which is why we’re going to propose that the blockchain fad is mostly
about putting finance in terms that are understandable to techies — i.e.
as something absolute – and having them learn for themselves through
trial and error why that’s actually a flawed assumption in finance.
http://ftalphaville.ft.com/2015/10/30/2143506/if-you-call-it...However, what I hear there is "oh sure, you might be able to write software for all of these other things, but not this thing that I'm an expert in, that's way too complicated". Many people have been wrong about this in other domains, and it seems to me that essential complexity can only delay the point at which software can usefully automate things, not prevent it entirely.
-John Kenneth Galbraith, Money: Whence it Came, Where it Went
She's contrasting that with a "techie" view where all that matters is securely and immutably recording the fact that a borrower has received the "coin" (which represents mainstream blockchain implementations, though I'm sure blockchains could be designed to reflect debt relationships and even enforce debt repayment), and suggesting that what the distributed consensus actually records is only a subset of the relationships a centralised accounting/clearing system deals with.
She also pointed out that our financial system being built around debt relationships actually guarantees there will be some non-zero level of demand for dollars/Euros/Yen etc in future, whereas building the Bitcoin ecosystem around who holds the Bitcoin at a given point in time doesn't actually guarantee people will still want them tomorrow (especially if they owe repayments on dollar-denominated debt to buy BTC or mining equipment)
It just reads like a poorly structured argument against a huge strawman.
But most arguments in favour of blockchains as a superior way of doing things are centred around the idea that replicating cash is the most important thing about building a monetary system, when cash is actually the least important (and most likely to be deprecated!) part of the monetary system the world today is built on. If you still need a separate authority or method of reaching consensus to reconcile debts, then making the record of who controls the assets independent and immutable is a bug of the monetary system rather than a feature.
They would probably be better handpicking a group of institutions / people / orgs and have them regularly sign statements of what's been going on since last time.
With regards to Bitcoin: The value in a distributed block chain is to ensure participants don't double-spend their coins. An attacker in a Sybil attack would spend their coins, broadcast the transaction and (after the recipient believes he's received the transfer) use fake identities to "vote against" including said transaction in the public ledger. That way, he could then go on to spend the coins again. To prevent this, Bitcoin uses a proof of work function: each participant in the network gets a share of the voting power corresponding to the effort he or she spends on calculating sha256 hashes, not to the number of identities one represents.
Which leads to the problem that whoever can spend the most money on computing power gets the most votes.
This is a particularly gross distortion of reality by people who for whatever reason want people to believe cryptographic currencies won't scale.
In the infancy of a currency, when there aren't many transactions, the mining power amortized over each transaction will be much more than when many transactions are happening. Each transaction doesn't take mining power, the number of transactions and mining are completely decoupled.
Bitcoin can currently handle about 2 transactions per second.
First, this isn't the real number and second 'handle' doesn't describe the situation, which is an artificial limitation built in as an artifact. Whether you are in the camp that believes this will be worked around in bitcoin or not is irrelevant, on a technical level any cryptocurrency can be created that can handle MANY more transactions.
Right now you could sync to the blockchain on the bandwidth T-Mobile gives for free while on international roam in 100 countries.
So the amount of data handled by every node is not even close to any sort of practical limit. Anyone with Netflix could sync to 50x the number of transactions.
That isn't the problem with things like this. The problem is trust, transparency and accountability. The old "A rasberry PI could handle the same amount of transactions" misses the point completely.
But how is that relevant to a gvt? The gvt controls all its servers so what do these ledgers add? I also see these ledger technologies being proposed for financial transactions clearing systems. Again, what problem are we trying to solve here?
The article says security if a central server is hacked. But if a client gets hacked you are not really better off.
Plus my understanding is that these ledgers do not scale. Each transaction takes a lot of computing power.