News for hackers. Stuff that matters.
Re:On the dangers of a blockchain monoculture by brighton36 on Tuesday January 05, 2016 @03:22PM (#10845732)
If there's no work - it's not a blockchain. Distributed ledgers are a completely parrallel movement that was taken up by those who wanted to leverage the marketing momentum of blockchain, for their own database projects. Which is fine, but shouldn't get confused with blockchain innovations.
Re:On the dangers of a blockchain monoculture by mikeyouse on Tuesday January 05, 2016 @03:33PM (#10845811)
There can be proof-of-stake blockchains, proof-of-use, proof-of-minimum-aged-time, etc. etc. The blockchain is just a chain of blocks, there are innumerable ways to protect it, verify it, and distribute the data.
Re:On the dangers of a blockchain monoculture by wmf on Tuesday January 05, 2016 @03:54PM (#10845930)
But a bunch of the "blockchain blockchain blockchain" startups don't use proof of anything.
Re:On the dangers of a blockchain monoculture by brighton36 on Tuesday January 05, 2016 @03:55PM (#10845949)
If the blockchain is just a chain of blocks, then every database designed after 1985 is also a blockchain. Is that what you believe?

Also- proof of stake always forks due to work attacks, so that's probably not a secured database.

Re:On the dangers of a blockchain monoculture by mikeyouse on Tuesday January 05, 2016 @04:09PM (#10846067)
I think the core value of a blockchain (as opposed to any general database) is that the most recent blocks contain a hash of the state of the system up to that point. This provides a tamper-resistant historical record of what's occurred previously.

I think your second point is what some of the critics of the bitcoin obsession are talking about. Not every blockchain needs to be as attack-resistant as the bitcoin network. Many of the speculative blockchain uses like for the Internet of Things could benefit from a history of all transactions but don't depend on it. Proof-of-stake might work fine for many cases.

Re:On the dangers of a blockchain monoculture by CyberDildonics on Tuesday January 05, 2016 @06:59PM (#10847197)
What you are describing has been a core of any ledger/immutable database. It isn't new and in fact has been around for ages. You don't really think a bank keeps all you money in a sacred database cell do you?
Re:On the dangers of a blockchain monoculture by lmm on Wednesday January 06, 2016 @06:11AM (#10849852)
Plenty of banks use pretty horrifying technology. Append-only databases have been a cool research project for ages but I've never seen one in production.
Re:On the dangers of a blockchain monoculture by nickpsecurity on Wednesday January 06, 2016 @11:46AM (#10851526)
They're more likely to use mainframe database systems with the verification done in apps that interface with it or do batch runs on it. The mainframes and databases themselves cover the integrity and availability portions. So, it's a ledger in practice but not directly stored as one.

Matter of fact, storing it as one is incredibly wasteful. Banking systems have shown it's not necessary. Just need the transactions, timing, sources, and verification of them.

Re:On the dangers of a blockchain monoculture by lambdadmitry on Wednesday January 06, 2016 @08:38AM (#10850391)
Re:On the dangers of a blockchain monoculture by lmm on Wednesday January 06, 2016 @10:18AM (#10850903)
Are any of those dividend-paying companies? At the risk of no true scotsmanning, I wouldn't count it as "production" if the company isn't making money off it yet.
Re:On the dangers of a blockchain monoculture by smokeyj on Tuesday January 05, 2016 @09:25PM (#10848001)
> This provides a tamper-resistant historical record of what's occurred previously.

So git basically. Maybe instead of blockchain technology they could call it version control tech.

Re:On the dangers of a blockchain monoculture by gobengo on Wednesday January 06, 2016 @05:18AM (#10849658)
Maybe instead of version control tech they should call it a Merkle Tree https://en.wikipedia.org/wiki/Merkle_tree
Re:On the dangers of a blockchain monoculture by nickpsecurity on Wednesday January 06, 2016 @12:47PM (#10852070)
Or a series of files with numbers that go up and a data structure tracking their dependencies. Git and others might use Merkle Trees but they're not even necessary. Good, but not necessary. Lot of ways to represent these basic concepts with so many tradeoffs.

That's why it's exciting when people break away from the crowd dictating specific approaches and start asking themselves questions about alternative techniques. :)

Re:On the dangers of a blockchain monoculture by kang on Tuesday January 05, 2016 @05:10PM (#10846444)
All those "proof-of"s have a money origin problem.
Re:On the dangers of a blockchain monoculture by nickpsecurity on Tuesday January 05, 2016 @05:39PM (#10846653)
That problem was solved back when we started putting money into banks and using it with computerized transactions. Variations on that model with nonprofits and distributed transactions could go far as alternative go current system.
Re:On the dangers of a blockchain monoculture by nickpsecurity on Tuesday January 05, 2016 @05:12PM (#10846462)
Yes it's parallel but you got it backward. The use of distributed transactions, fault-tolerance, etc predates Bitcoin by over a decade. Bitcoin built on it and proof-of-work. As usual, people started re-discovering stuff they ignored in the process.
Re:On the dangers of a blockchain monoculture by pjc50 on Wednesday January 06, 2016 @08:25AM (#10850343)
Proof-of-waste is far too environmentally damaging to use at scale.