Introducing our Real World Assets (RWA) Protocol. Learn more here.

After all required features are operational on the Public Testnet, a Mainnet release candidate will be tested.

As an additional security measure, the system level anchor chain will intermittently record checkpoints on Ethereum.

A feature used in connection with native fees. When a dapp’s hosting fees are not paid, its data can be stored in a way that uses minimal resources. If the dapp is redeployed later, this data can be restored.

Chromia dapps function on a framework where network providers receive compensation in the form of CHR tokens. To streamline and simplify this process, we are developing a native fee system.

Once the FT4 Bridge Integration is completed, CHR tokens from Ethereum and BNB Network can be bridged to Chromia chains. At first, CHR will be primarily used to pay hosting fees.

After integrating the existing bridge code into the FT4 Protocol, users will be able to bridge ERC-20 assets from supported EVM chains to Chromia, where they will be represented as FT4 tokens.

Our official browser-based wallet. Chromia Vault will allow users to open accounts and manage their assets across the Chromia Network.

Done

This update adds cross-chain functionality to the FT4 library, enabling token transfers between supported dapp chains on the Chromia Network.

Done

Our official block explorer provides information regarding system chains, dapp chains, accounts, token transfer histories, and more. The explorer is toggleable between various networks (public testnet, Shared Appnet, etc.)

Done

Provides a set of tools allowing developers to deploy FT4 tokens and build dapp specific wallet implementations.

Done

FT4 is the recommended standard used to handle accounts and tokens in the Chromia ecosystem.

Done

An advanced system for blockchain configuration updates that utilizes the Directory and Anchoring chains. PCU assists the network by ensuring nodes update in sync and maintain consensus regarding blockchain configurations.

Done

Provided the base functionality to bridge a specific asset from an EVM chain to specific Chromia dapp. Used as the starting point for FT4 Bridge Integration, which will allow for generalized and permissionless bridging.

Done

Chromia nodes are arranged into clusters which run blockchains. The block headers of all the blockchains within a cluster are serialized and committed to an anchor chain. These are then committed to a system level anchor chain.

Done

Chromia CLI simplifies the development cycle and deployment of Rell dapps by providing a command-line tool that can interact with the Chromia Network.

Done

The EIF module facilitates decentralized communication between EVM-compatible chains and Chromia, allowing developers to build Chromia dapps that are interoperable with Ethereum and other platforms.

Done

ICMF is primarily used for internal network communication between utility chains, while ICCF is used by dapp developers for cross-chain communication. The net result of these tools is efficient and secure communication between dapp and system chains across the Chromia Network.

Done

The Mark 2 Testnet establishes a single cluster network on a preliminary group of provider nodes and provides the ability to stake CHR tokens (ERC-20 or BEP-20) to register a dapp on the testnet. Initially, dapp features are limited. More advanced features will become available during the Testnet Expansion Phase.

Done

Framework for resource management for dapps across provider nodes, enabling decentralized resource allocation.

Done

The Directory Chain is responsible for coordination of the Chromia Network as a whole. It stores all information needed to run the network, such as a list of providers and nodes, and the configuration of each blockchain.

Done

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.

Done

Chromia SSO is a decentralized authentication scheme which allows seamless login to dapps without exposing the root keypair.