I recently came across a paper published in 1988 called "A quorum-based commit and termination protocol for distributed database systems". I could not read it because it is not free, but to me this sounds very similar to what a private blockchain using proof of stake for consensus achieves. I have a hard time believing that's all there is to it considering all the hype going on. With that in mind, I have the following questions:

  1. Is chaining blocks together the only innovation here? Why not just have trusted validators sign transactions in permissioned distributed databases? We have had these technologies for decades. What is the difference?
  2. Couldn't a 51% attack where someone has private keys for a certain transaction rebuild the chain from that point on for basically free? How does this achieve any realistic level of immutability?
  3. Why would financial institutions want to 1. Pay to store competitors data 2. Allow competitors to see their data?

I want to understand what everyone is finding so new and exciting about private blockchains.

  • This? hub.hku.hk/bitstream/10722/158032/1/Content.pdf?accept=1
    – Nick ODell
    Commented Jun 13, 2017 at 0:38
  • "Why not just have trusted validators sign transactions in permissioned distributed databases?" Because that requires trusted validators. Why trust anyone when you don't have to? Blockchain requires virtually NO trust of anyone at all.
    – abelenky
    Commented Jun 13, 2017 at 1:05

2 Answers 2


I have not read the paper, but here are some thoughts.

Private blockchains make little sense (to me). But of course maybe a clever person will figure out a killer app for/on private blockchains. To me they are analogous to corporate intranets of the mid/late 90s. Those were hyped up as well. IMO a public blockchain is the way to go, perhaps with encrypted transactions, or perhaps using Zero Knowledge Proofs (ala Zcash) if privacy is important.

To comment on your questions:

  1. Chaining blocks together provides a little more security as you could not just change one transaction in block X you would have to recalculate the hashes for each block forward and get others to agree to that change. In a DDB one could just delete/alter/change an entry.
  2. This would really depend on how the private blockchain is set up. Do we need others to accept each block? Would others recognize our new rebuilt blockchain? What consensus algo are we using here?
  3. Blockchains offer a lot (in the right user case). In the case of banks transactions can be encrypted and only the parties involved have the keys to decrypt. Why have a blockchain to store competitors data? Well, what if the blockchain is used only for inter-bank transactions, and not for internal ones. Then there is a immutable (hopefully) record of transactions between banks.

Keep in mind that private blockchains are in their experimental stages. Banks like to make announcements for publicity, this does not mean that they have a working model or using the technology commercially. More often than not it is simply an intent to explore the possibilities that the technology can provide.


Every tried searching for it? The full paper is the 3rd result if I google the tile. According to the first page in that PDF, it's even under a creative commons license. It's a PDF consisting of scanned pages but somehow the text is mapped to the characters anyway.

To me, the concept described in the paper seems to be nothing more than a usual quorum-based database system with the paper focusing on the voting protocol.

The paper doesn't talk about blocks, a blockchain, a hostile environment, competitors, stake, or anything related to that. Are you sure this is the correct paper?

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service and acknowledge you have read our privacy policy.

Not the answer you're looking for? Browse other questions tagged or ask your own question.