Coinprism Unveils Openchain 0.5 with Componentized Architecture

Coinprism announced today the 0.5 release of its distributed ledger, Openchain, which has a significant number of improvements over the previous version.

The new features include a new componentized architecture, SQL server storage engine, an “account_create” permission, Namespace discovery, direct deployment, and a number of bug fixes.

Coinprism posted a description of these features on its blog:

  • New componentized architecture: Openchain has undergone a large refactoring work for the 0.5 version. Components such as storage engines are now isolated in their own modules. The core server (Openchain.Server) does not have any dependency on any external module anymore. Dependencies are added at deployment time, in function of what is needed, and pulled through NuGet. This allows anyone to extend Openchain by building third-party modules. Modules include: storage engines (such as SQLite), anchoring media (such as Blockchain anchoring) and validation modules (such as permission-based).
  • New SQL Server storage engine: Until today, the only available storage engine was based on SQLite. Since SQLite is a local database, it does not offer high availability. In this release, we are shipping a storage engine based on SQL Server. SQL Server offer high availability through mirroring, and can be hosted on Microsoft Azure. This also allows you to have several Openchain servers running on separate servers all connecting to the same database to achieve horizontal scalability.
  • New “account_create” permission: The new permission “account_create” works much like “account_modify”. “account_modify” is required for any transaction affecting an account, either positively or negatively. It is now being split in two: “account_create” is required if the record has never been touched before (version is an empty string). “account_modify” is required if the record has been touched before.
  • Namespace discovery: Previously, the namespace was based on the root URL of the Openchain endpoint. We are changing this so that the namespace is exposed directly by the Openchain server through a new “/info” endpoint. This will get rid of the infamous error “The namespace used in the transaction is invalid” that many people were experiencing.
  • Direct deployment: We now offer an easy way to deploy Openchain directly without using Docker. The only prerequisite is for you to have installed .NET Core.
  • Bug fixes: We have done a number of bug fixes, such as improvements in error handling.

Openchain is not literally a blockchain, but a “transaction chain” that consists of transactions in a chain created as soon as they are submitted to the network. This permits Openchain to support real-time transactions. Coding for the platform has also built in the ability for multiple instances of Openchain to be replicated from each other with validator and observer nodes. The source code of Openchain is available on GitHub and documentation on the project website.

Flavien Charlon, the founder of Coinprism, wrote the Open Assets Protocol in 2013, which permits storing and transferring of custom, non-native digital assets – called Colored Coins – on the Bitcoin blockchain.  Coinprism released the first colored coins wallet.