quorum

they do the same thing with boring old technology? >“With increasing state and federal requirements relating to provider data maintenance and quality, tackling the high cost and redundancy in this space is a logical starting point" Backups and redundancy existed before the Blockchain, also I'm sure nobody wants to publish private user data publicly for all to see so it's not like random users around the world are going to mirror your database. So you end up with a "Blockchain" where only trusted people can access and contribute. What's the advantage over spinning up a PostgreSQL intance? I mean when you read the Quorum wiki[1] it reads more like a database setup guide than spinning a bitcoin node: >The P2P layer has been modified to only allow connections to/from permissioned nodes. And just like that the entire point of the Blockchain vanishes. >‘Proof of work’ consensus algorithm has been replaced with ‘QuorumChain’ consensus, a vote-based consensus mechanism. Surely I hope that medicare providers obey to some top-down rules to operate, not a consensus on a Blockchain. And given that all nodes are whitelisted anyway I'm not sure why such a voting is even required. It's pretty crazy to me that when I read articles like this one on Forbes or the Quorum website I see pages after pages of hype and praise and yet so far nobody is capable of giving me one simple use case demonstrating the practical usefulness of the technology outside of cryptocurrencies. The more I read about it the more I become convinced that the only real feature of the Blockchain is being a magic word that makes suits throw money at you. Maybe I'm just too dumb to understand it. [1] https://github.com/jpmorganchase/quorum/wiki

a 1.0 release which is imminent. It is the basis of the IBM Blockchain commercial offering, and is getting a lot of traction in Enterprise settings. https://www.ibm.com/blockchain/ The primary aim of the Enterprise Ethereum Alliance (EEA) is to build an extension/variant of the public Ethereum specification to cover the additional use-cases which Enterprises need to get into production - along the themes of scalability (usually just pluggable consensus), privacy and confidentiality and permissioning. JPM Quorum is an example of an Ethereum fork seeking to meet those needs: https://github.com/jpmorganchase/quorum Many of us see all of the public/consortium/private use-cases as being something which will likely converge over the next few years. Sufficiently modular codebases should be able to handle them all, with dynamic composition of components. We are working towards the creation of an extended Ethereum meeting all those needs. ---