A quick word from our CTO Alex Mizrahi about the Chromia project and the most effective way of communicating our objectives and progress to the community.
“We are 100% committed to delivering the platform that we outlined in our white paper, that is certain. The scale of this project should not be underestimated; we are building something entirely new from the ground up, there are many unknowns and the stakes are high.
When working on something entirely new, it is very difficult to forecast how long things will take because there is no precedent or history to base estimates on.
Similarly, while we can predict upcoming features, it is difficult to chart our long term milestones because of the enormous breadth of possibilities and branching paths which we might follow to reach approximately the same destination.
Finally, we work agile! That means that we are constantly reassessing our priorities and tasks, and incorporating feedback from the community to inform our decision making. We know that the market craves certainty and predictability, but tough lessons in the software industry have shown time and time again that the forecasts of fixed roadmaps and waterfall development will very likely fail to materialize. We, along with most of the software development world, prefer to embrace uncertainty and flexibility rather than expend our resources creating the illusion of predictability.”
Our consensus method is based on PBFT, but is our own custom implementation from the ground up. It is robust and flexible, built for Chromia’s massive horizontal scale.
Flexible Tokens is the Chromia token standard, supporting fungible and non-fungible tokens of arbitrary complexity, as well as implementing Chromia SSO, a decentralized authentication scheme which allows seamless login to dapps without exposing the root keypair.
Postchain 3 was the third major release of Postchain, the relational blockchain technology which underpins the Chromia platform. Postchain 3 featured a mature transaction scheme (GTX) with a full value serialisation model (GTV), and proof extractor.
A new facility which allows block producer nodes to play a more active role and inject data into a blockchain. Block producers need to form consensus about the data being injected in the same way they do it for blocks. This feature is uniquely suited for creation of layer-2 blockchains, as data from parent blockchains can be injected and be subject to consensus.
The Chromia Explorer is a decentralized blockchain explorer, possibly the first of its kind in the world.
This feature makes it possible for any Chromia blockchain to automatically perform an action at the beginning or end of any block.
While this may seem like a minor feature, the lack of it can create issues for dapp developers. For example, Maker CDPs can go bad if there is no mechanism to trigger liquidation, while on Chromia you can make it fully automatic and independent of outside actors.
The base set of L2 functionality in Chromia consists of a number of facilities including:
Currently cross-chain interaction is possible via confirmation proofs. While sufficiently general, this isn't particularly robust as it depends on clients to inject events. Using special transactions and ephemeral dependencies we can enable more direct cross-chain communication where block producer nodes will be responsible for facilitating communication directly on blockchain core level.
Rell continues to evolve with every passing day, but the first version with a fully implemented interpreter was a major milestone. That was when Rell became a full-fledged blockchain programming language.
Blockchain dependencies were a key milestone on the road to the hierarchically interconnected blockchain networks which support Chromia’s massive scale. Allowing one blockchain to pull data from another means not just greater efficiency, but also the ability to use decentralized governance to update configurations and parameters for dependent blockchains.
Managed mode allows a Postchain network to infer its own configuration (signers, validators, observers, pruning, historic configurations) from another blockchain. This abstracts the maintenance and updating of nodes from the node operator, allowing update operations to be safely coordinated in a decentralized way.
The Chromia Vault is our wallet software and dapp portal. It allows for token management and decentralized authentication to dapps running on other chains. It is itself a decentralized application.
Adding the possibility to sync a blockchain from any node which has a copy of it, and increasing the robustness of the synchronization subsystem. Previously it was only possible to sync from current block producers.
Framework for resource management for dapps across provider nodes, enabling decentralized resource allocation.
This feature builds on the previously implemented 'blockchain dependencies' feature, which allows one blockchain to directly read data from another. A capability that is, as far as we know, unique in the blockchain world.
While very powerful, it has a limitation: if blockchain A depends on blockchain B, we need to keep B around forever for blockchain A to be sync-able. This limitation limits ability to re-architect and optimize the system. This is particularly essential for system blockchains which need to be future-proof. Ephemeral dependencies would allow developers to remove dependencies over time when they are no longer needed.
Tools to instantiate a blockchain in “development mode” to make it easier to develop and test dapps in simulated environments.