We would never say that Bitcoin (especially Bitcoin) or Ethereum are “not good enough” - in fact, our architecture specifically calls to leverage the massive and unprecedented value of public blockchains (especially Bitcoin with its hash power). This may be hard to quickly explain, but we want to make integration of legacy and new systems with blockchain much easier and less risky than it currently is.
As an example, currently, if you want to build a blockchain backed system with Bitcoin, you will need to both (1) create a wholly complete internal and centralized system to maintain your customer/private data and (2) have enough knowledge of Bitcoin to integrate that system with Bitcoin tokenization or other PoE capabilities.
With Ethereum, you will also need advanced Ethereum knowledge, and though you can now use more capable smart contracts than are available in the Bitcoin ecosystem, you will have to take some risk in the unknown unknowns with the network, as well as the known risks of community forking.
At the same time, an entirely private blockchain or permissioned ledger has many weaknesses.
We consider the Dragonchain architecture to offer a spectrum of risk from simple and total internal trust, up through various verification contexts, and all the way to a public bridge to a proof of existence/checkpoint into Bitcoin (or other) public blockchain.
We’re attempting to mix a “tried and true” classical software architecture (security and scalability) with a decentralized blockchain system, with simplified integration for those without blockchain experience, whilst allowing an organization to retain complete and explicit control over its data, processing, and network without worry about the community or public network.