# Chromia Docs > Chromia is a public Layer-1 relational blockchain: apps and AI agents keep data in real tables (PostgreSQL under EBFT consensus), write and query it in Rell, one chain per app, users pay no gas. These docs cover install, Rell, FT4 accounts and assets, client SDKs, the chr CLI, deployment, and node operation. Every page has a Markdown twin: replace the trailing `/` with `/index.md`. - [llms-full.txt](https://docs.chromia.com/llms-full.txt): all guide pages in one file (API reference excluded) - [sitemap.xml](https://docs.chromia.com/sitemap.xml): all 1842 pages ## Get started - [Zero to a running dapp in 10 minutes](https://docs.chromia.com/get-started/index.md): tested quickstart: install chr, create a Rell dapp, local node, query, transaction, redeploy (every command run 1 Nov 2026). - [Rell Playground](https://docs.chromia.com/playground/index.md): edit Rell examples in the browser; run them locally with chr test. - [Search the docs](https://docs.chromia.com/ask/index.md): retrieval helper that quotes these docs with source links. - [Introduction](https://docs.chromia.com/get-started/about/index.md): Official documentation for Chromia blockchain developers. - [Architecture](https://docs.chromia.com/get-started/about/architecture-summary/index.md): Chromia organizes blockchains and dapps into clusters with reliable consensus, secure anchoring, and elastic resources. - [Architecture](https://docs.chromia.com/get-started/about/architecture/index.md): The Chromia network consists of clusters of nodes. Each cluster is responsible for running a set of blockchains. System - [Governance](https://docs.chromia.com/get-started/about/architecture/chain-governance/index.md): Governance in Chromia focuses on managing chain updates, proposals, and overall network operations, ensuring that the - [Chromia System Chains](https://docs.chromia.com/get-started/about/architecture/chains/index.md): The Chromia ecosystem has multiple system chains. These chains ensure among other things tamper-proof data, efficient - [Cluster Anchoring Chain](https://docs.chromia.com/get-started/about/architecture/chains/cluster-anchoring-chain/index.md): The Cluster Anchoring Chain is an important part of the Chromia network's security. Its main job is to keep data safe - [Directory Chain](https://docs.chromia.com/get-started/about/architecture/chains/directory-chain/index.md): Overview - [Economy Chain](https://docs.chromia.com/get-started/about/architecture/chains/economy-chain/index.md): Overview - [System Anchoring Chain](https://docs.chromia.com/get-started/about/architecture/chains/system-anchoring-chain/index.md): The System Anchoring Chain is at the top of the anchoring hierarchy in the Chromia network. It anchors all blocks from - [Token Chain](https://docs.chromia.com/get-started/about/architecture/chains/token-chain/index.md): Overview - [Nodes](https://docs.chromia.com/get-started/about/architecture/node/index.md): A node in the Chromia network is a computer, either a virtual or physical server, that runs the core Chromia software - [Platform architecture](https://docs.chromia.com/get-started/about/architecture/platform-architecture/index.md): The Chromia platform is organized into clusters, each consisting of multiple - [Benefits](https://docs.chromia.com/get-started/about/benefits/index.md): Chromia is an advanced Layer-1 blockchain ecosystem that developers use to create high-performance and scalable - [Chromia vs EVM](https://docs.chromia.com/get-started/about/chromia-vs-evm/index.md): This page provides a high-level comparison between Chromia and traditional EVM-based blockchains like Ethereum. If - [Build dapps (Rell & Clients)](https://docs.chromia.com/get-started/about/dapp/index.md): A decentralized application, or dapp, consists of various components that work together to serve a valuable purpose for - [What are Chromia extensions?](https://docs.chromia.com/get-started/about/extensions/index.md): Chromia extensions serve as pre-built docker images that add specialized features or services to containers within the - [Hosting](https://docs.chromia.com/get-started/about/hosting/index.md): Chromia provides a cloud-like hosting experience with the advantages of decentralization and no gas fees, meaning users - [Protocols](https://docs.chromia.com/get-started/about/protocols-summary/index.md): Chromia's protocol stack defines how data is serialized, transactions are executed, accounts and tokens are managed, and - [Protocols](https://docs.chromia.com/get-started/about/protocols/index.md): Chromia provides a set of protocols that help you manage accounts, tokens, and communication between blockchains in the - [FT4](https://docs.chromia.com/get-started/about/protocols/ft4/index.md): The FT4 protocol offers a library that assists developers in creating complex blockchain solutions related to fungible - [Generic Transfer Value (GTV)](https://docs.chromia.com/get-started/about/protocols/gtv/index.md): The Generic Transfer Value (GTV) protocol serves as the foundation for data serialization in Postchain. It supports a - [Generic Transaction Protocol (GTX)](https://docs.chromia.com/get-started/about/protocols/gtx/index.md): The Generic Transaction Protocol (GTX) is a protocol built on top of the Generic Transfer Value (GTV). It focuses - [Inter-chain Confirmation Facility (ICCF)](https://docs.chromia.com/get-started/about/protocols/iccf/index.md): Overview - [Inter-chain Messaging Facility (ICMF)](https://docs.chromia.com/get-started/about/protocols/icmf/index.md): Overview - [Providers](https://docs.chromia.com/get-started/about/providers/index.md): Providers are individuals or organizations that contribute computing power to the Chromia network by running nodes. - [Staking](https://docs.chromia.com/get-started/about/staking-summary/index.md): Chromia relies on staking to secure clusters, compensate providers, and let token holders participate without running - [Staking](https://docs.chromia.com/get-started/about/staking/index.md): Staking is a fundamental mechanism in the Chromia network that ensures security, incentivizes participation, and enables - [Provider staking](https://docs.chromia.com/get-started/about/staking/provider-staking/index.md): Providers in the Chromia network must stake CHR tokens in order to get rewarded for participating in block production - [User staking and delegation](https://docs.chromia.com/get-started/about/staking/user-delegation/index.md): Anyone holding CHR tokens can participate in network staking by delegating their tokens to providers. This allows users - [Supported wallets](https://docs.chromia.com/get-started/about/supported-wallets/index.md): Chromia lets users securely manage their assets and interact with the network through various compatible wallets. Here's - [Rell](https://docs.chromia.com/get-started/about/what-is-rell/index.md): Rell (Relational Language) is Chromia's purpose-built programming language for developing decentralized applications - [Create a Hello World dapp](https://docs.chromia.com/get-started/create-dapp/index.md): This section covers how to build and run Hello World dapp with different available tools for Rell. You can choose the - [Deploy your dapp to Testnet](https://docs.chromia.com/get-started/create-dapp/deploy-to-testnet/index.md): Run these commands from your Hello World project folder. - [Build and run](https://docs.chromia.com/get-started/create-dapp/run-dapp-cli/index.md): In this topic, you'll build and deploy the Hello World dapp with the - [Get started with Chromia](https://docs.chromia.com/get-started/installation/index.md): Choose how to set up your Chromia development environment: - [Use Cases](https://docs.chromia.com/get-started/use-cases/index.md): Welcome to the Chromia use cases section. This is where we collect practical applications and implementations you can - [AI applications](https://docs.chromia.com/get-started/use-cases/ai-on-chain/index.md): Chromia's unique architecture makes it possible to run sophisticated AI operations on-chain, opening up new - [AI inference applications](https://docs.chromia.com/get-started/use-cases/ai-on-chain/ai_inference/index.md): Challenge - [Vector database applications](https://docs.chromia.com/get-started/use-cases/ai-on-chain/vector-db/index.md): Challenge - [Cross-chain applications](https://docs.chromia.com/get-started/use-cases/cross-chain/index.md): Cross-chain communication is essential for building truly interconnected blockchain ecosystems that can leverage the - [Cross-chain verification applications](https://docs.chromia.com/get-started/use-cases/cross-chain/iccf/index.md): Challenge - [Cross-chain communication applications](https://docs.chromia.com/get-started/use-cases/cross-chain/icmf/index.md): Challenge - [Real-time data applications](https://docs.chromia.com/get-started/use-cases/real-time-data/index.md): Real-time data is the lifeblood of modern decentralized applications, enabling responsive and intelligent systems that - [Real-time data feed applications](https://docs.chromia.com/get-started/use-cases/real-time-data/stork/index.md): Challenge ## Rell - [Rell](https://docs.chromia.com/rell/index.md): Rell: every page in this section of the Chromia docs (11 topics). - [Rell code optimization](https://docs.chromia.com/rell/analyze-rell-dapp-code/index.md): This topic provides insights into the process of analyzing and optimizing your dapp code written in Rell. You can use - [Core concepts](https://docs.chromia.com/rell/core-concepts/index.md): Language overview - [Rell language reference](https://docs.chromia.com/rell/language-features/index.md): Rell is the programming language for the Chromia blockchain. This reference covers the language syntax, type system, - [Database operations](https://docs.chromia.com/rell/language-features/database/index.md): This section covers Rell's database operations, including creating, updating, and deleting records with various options - [Create statement](https://docs.chromia.com/rell/language-features/database/create/index.md): Must specify all attributes that don't have default values: - [Delete statement](https://docs.chromia.com/rell/language-features/database/delete/index.md): You can use operators @, @?, @*, @+ to specify cardinality, like for the at-operator. A run-time error occurs if - [Overview](https://docs.chromia.com/rell/language-features/database/overview/index.md): Rell provides several built-in functions for database operations. Rell allows both the comma notation and the and - [Update statement](https://docs.chromia.com/rell/language-features/database/update/index.md): You can use operators @, @?, @*, @+ to specify cardinality, like for the at-operator. A run-time error occurs if - [Expressions](https://docs.chromia.com/rell/language-features/expressions/index.md): Expressions in Rell are used to perform operations and control program flow, combining data, variables, and operators. - [Conditional expressions](https://docs.chromia.com/rell/language-features/expressions/conditional-expressions/index.md): Both if and when can be used as expressions, producing a value instead of branching over statements. For their - [Jump expressions](https://docs.chromia.com/rell/language-features/expressions/jump-expressions/index.md): return, break, and continue can be used as expressions in addition to their statement forms. A jump expression - [Lambda expressions](https://docs.chromia.com/rell/language-features/expressions/lambda-expressions/index.md): A lambda expression is an anonymous function written with arrow syntax (->). It evaluates to a first-class function - [Operators](https://docs.chromia.com/rell/language-features/expressions/operators/index.md): Member access - [Values](https://docs.chromia.com/rell/language-features/expressions/values/index.md): Rell offers various data types for managing information in your dapps. Here's an overview of the fundamental types - [Identifiers](https://docs.chromia.com/rell/language-features/identifiers-syntax/index.md): Identifiers in Rell are names used for variables, functions, and other declarations. They must follow specific syntax - [Definitions](https://docs.chromia.com/rell/language-features/modules/index.md): Definitions in Rell create reusable code components, including entities, objects, structs, enums, queries, operations, - [Abstract module](https://docs.chromia.com/rell/language-features/modules/abstract/index.md): Abstract modules and functions allow you to design reusable code components that you can adapt to specific needs within - [Entity](https://docs.chromia.com/rell/language-features/modules/entity/index.md): Entities in Rell are persistent data structures mapped to database tables rather than residing solely in memory. This - [Enum](https://docs.chromia.com/rell/language-features/modules/enum/index.md): Enumeration types, or enums, creates maintainable sets of constants in Rell, enhancing code readability and preventing - [Function](https://docs.chromia.com/rell/language-features/modules/function/index.md): In Rell, functions streamline repetitive tasks by encapsulating reusable logic, such as validation or data retrieval. - [Mount names](https://docs.chromia.com/rell/language-features/modules/mount/index.md): Entities, objects, operations, and queries have mount names: - [Namespace](https://docs.chromia.com/rell/language-features/modules/namespace/index.md): Namespaces provide essential structure and clarity to your Rell projects, allowing for better organization and - [Object](https://docs.chromia.com/rell/language-features/modules/object/index.md): An object is similar to an entity, but there can be only one instance of an object: - [Operation](https://docs.chromia.com/rell/language-features/modules/operation/index.md): Operations are declared using the operation keyword, followed by a unique operation name and a list of parameters - [Query](https://docs.chromia.com/rell/language-features/modules/query/index.md): Queries provide a controlled way to retrieve data in Rell. - [Size constraint annotations](https://docs.chromia.com/rell/language-features/modules/size-constraint-annotations/index.md): You can add size constraint annotations to parameters of functions, queries, and operations, to struct attributes, and - [Struct](https://docs.chromia.com/rell/language-features/modules/struct/index.md): A struct is similar to an entity, but its instances exist in memory, not in a database. - [Statements](https://docs.chromia.com/rell/language-features/statements/index.md): Statements in Rell are essential for controlling program flow and data handling. This section explores variable - [Basic statements](https://docs.chromia.com/rell/language-features/statements/basic-statements/index.md): In Rell, the fundamental building blocks of programming are encapsulated within basic statements. These statements - [Conditional statements](https://docs.chromia.com/rell/language-features/statements/conditional-statements/index.md): Rell has two conditional statements: if for branching on a boolean condition, and when for multi-way branching. Both - [Variable declarations](https://docs.chromia.com/rell/language-features/statements/local-variable/index.md): In Rell, local variables play a important role in storing and managing data within a specific scope. They provide a way - [Loop statements](https://docs.chromia.com/rell/language-features/statements/loop-statements/index.md): In Rell, loop statements include the for, while, break, and continue statements, each serving distinct purposes - [System library](https://docs.chromia.com/rell/language-features/systemlib/index.md): This section covers Rell's system library, which provides core entities, built-in namespaces and functions, and system - [Global functions](https://docs.chromia.com/rell/language-features/systemlib/global-functions/index.md): Rell provides a collection of built-in global functions for common tasks. For complete API documentation, see the - [Namespaces](https://docs.chromia.com/rell/language-features/systemlib/namespaces/index.md): Namespaces in Rell group related functions, variables, and data structures, each serving a specific purpose. For - [chain_context](https://docs.chromia.com/rell/language-features/systemlib/namespaces/chain_context/index.md): The chain_context namespace provides access to blockchain configuration and module arguments. For complete API - [crypto](https://docs.chromia.com/rell/language-features/systemlib/namespaces/crypto/index.md): The crypto namespace provides cryptographic functions for hashing, key management, signing, and Ethereum operations. - [meta](https://docs.chromia.com/rell/language-features/systemlib/namespaces/meta/index.md): The rell.meta type provides meta-information about definitions like operations, entities, and queries. For complete - [op_context](https://docs.chromia.com/rell/language-features/systemlib/namespaces/op_context/index.md): The op_context namespace provides information about the current operation context, including block information, - [rell.time](https://docs.chromia.com/rell/language-features/systemlib/namespaces/time/index.md): The rell.time namespace formats and parses UTC dates and times. Its central type, - [require and error handling](https://docs.chromia.com/rell/language-features/systemlib/require-function/index.md): The require function allows you to verify Boolean conditions, check for null values, or ensure non-empty collections. - [System entities](https://docs.chromia.com/rell/language-features/systemlib/system-entities/index.md): In Rell, once data is stored within block and transaction entities, it becomes immutable, meaning it cannot be - [System queries](https://docs.chromia.com/rell/language-features/systemlib/system-queries/index.md): System queries provide information about the Rell environment, Postchain version, build metadata, and your dapp’s - [Types](https://docs.chromia.com/rell/language-features/types/index.md): In Rell, the type system is designed to handle a wide range of data representations and operations. It includes simple - [Collection types](https://docs.chromia.com/rell/language-features/types/collection-types/index.md): Rell supports the following collection types: - [Complex types](https://docs.chromia.com/rell/language-features/types/complex-types/index.md): Complex data types in the Rell programming language provide advanced features and capabilities beyond basic types like - [Iterables](https://docs.chromia.com/rell/language-features/types/iterables/index.md): Iterable values introduce a unified concept for processing sequences in various data structures. While the compiler uses - [Simple types](https://docs.chromia.com/rell/language-features/types/simple-types/index.md): In Rell, there are several simple data types to represent different kinds of data. They're not composed of other data - [Subtypes](https://docs.chromia.com/rell/language-features/types/sub-types/index.md): In Rell, the concept of subtypes enhances code flexibility and reusability by allowing seamless assignment between - [Virtual types](https://docs.chromia.com/rell/language-features/types/virtual-types/index.md): Virtual types use Merkle trees to efficiently verify data integrity and selectively retrieve specific elements. - [Rell modules](https://docs.chromia.com/rell/modules/index.md): The Rell dapp consists of modules. A module is either a single .rell file or a directory with one - [Rell releases](https://docs.chromia.com/rell/releases/index.md): | Release | Changes/Updates - [Rell best practices](https://docs.chromia.com/rell/rell-best-practices/index.md): This topic shares real examples and best practices for building Rell dapps on Chromia, using actual implementations from - [RellDoc: Documentation Comments for Rell](https://docs.chromia.com/rell/rell-doc/index.md): RellDoc is the documentation comment format for the Rell programming language. It provides a standardized way to - [Introduction to Rell](https://docs.chromia.com/rell/rell-intro/index.md): This section covers the advantages of Rell and its position within the Chromia platform. - [Security tips for Chromia dapps](https://docs.chromia.com/rell/security/index.md): Protection against malicious dapps - [Special operations](https://docs.chromia.com/rell/special-operations/index.md): Special operations are specific types of operations that facilitate various events on the Rell dapp side. These - [Test Rell code](https://docs.chromia.com/rell/tests/index.md): To write unit tests for Rell code, use test module. You need to use the @test annotation to define ## Build - [Build](https://docs.chromia.com/build/index.md): Build: every page in this section of the Chromia docs (10 topics). - [CLI](https://docs.chromia.com/build/cli/index.md): CLI: every page in this section of the Chromia docs (7 topics). - [Seeder command](https://docs.chromia.com/build/cli/Seeder/index.md): The Seeder command is a powerful CLI tool that helps you manage and populate your Chromia blockchain with initial data. - [Configurable generators](https://docs.chromia.com/build/cli/Seeder/configurable-generators/index.md): The following generators support additional configuration options: - [Available generators](https://docs.chromia.com/build/cli/Seeder/generator/index.md): This topic provides a comprehensive catalog of all data generators available in the Rell Toolbox Seeder module. These - [Using the seeder](https://docs.chromia.com/build/cli/Seeder/seeder-example/index.md): This topic explains how to use the seeder commands to generate test data for your Rell projects. The seeder - [Chromia CLI release notes](https://docs.chromia.com/build/cli/cli-release-notes/index.md): The release notes lists all new features, resolved issues, and known issues of Chromia CLI in chronological order. - [CLI command reference](https://docs.chromia.com/build/cli/commands/index.md): Complete Chromia CLI command reference - chr commands for build, deploy, test, and manage Rell dapps - [build](https://docs.chromia.com/build/cli/commands/build/index.md): The build command (chr build) creates a blockchain configuration for your - [code](https://docs.chromia.com/build/cli/commands/code/index.md): You can use the code command (chr code) for code quality management (formatting and linting). - [create-rell-dapp](https://docs.chromia.com/build/cli/commands/create-rell-dapp/index.md): You can use the create-rell-dapp command (chr create-rell-dapp) to create a new Rell - [deployment](https://docs.chromia.com/build/cli/commands/deployment/index.md): deployment create - [eif](https://docs.chromia.com/build/cli/commands/eif/index.md): The Ethereum Interoperability Framework (EIF) command chr eif generate-events-config allows you to generate Solidity - [generate](https://docs.chromia.com/build/cli/commands/generate/index.md): generate client-stubs - [help](https://docs.chromia.com/build/cli/commands/help/index.md): The help command (chr help) shows general help information and lists all available commands. - [keygen](https://docs.chromia.com/build/cli/commands/keygen/index.md): Generate keys - [library](https://docs.chromia.com/build/cli/commands/library/index.md): You can use the library command (chr library) to manage organizations and libraries in the Chromia library ecosystem. - [multi-signature](https://docs.chromia.com/build/cli/commands/multi-signature/index.md): You can use the multi-signature command (chr multi-signature) for handling transactions that need multiple signers. - [node](https://docs.chromia.com/build/cli/commands/node/index.md): You can use the node command (chr node) to start or update a node with your applications running on it. - [query](https://docs.chromia.com/build/cli/commands/query/index.md): You can use the query command (chr query) to test and interact with a chain that's either local or deployed without - [repl](https://docs.chromia.com/build/cli/commands/repl/index.md): You can use the repl command (chr repl) to run specific Rell methods in the shell, which can be suitable for - [seeder](https://docs.chromia.com/build/cli/commands/seeder/index.md): You can use the seeder command (chr seeder) to generate mock data for a local database. This is an early-stage feature - [test](https://docs.chromia.com/build/cli/commands/test/index.md): You can use the test command (chr test) to run the tests specified in the test key in the - [tools](https://docs.chromia.com/build/cli/commands/tools/index.md): You can use the tools command (chr tools) provides a set of miscellaneous tools for various tasks related to Chromia. - [tx](https://docs.chromia.com/build/cli/commands/tx/index.md): You can use the tx (transaction) command (chr tx) in the same way as the query command, but you need to sign it with - [version](https://docs.chromia.com/build/cli/commands/version/index.md): The version command (chr version) displays version information for the chr CLI tool and its components. - [Generate documentation](https://docs.chromia.com/build/cli/generating-doc-site/index.md): This topic explains how to generate a documentation site from your Rell source code and how to customize it to match - [Introduction to Chromia CLI](https://docs.chromia.com/build/cli/introduction/index.md): Official Chromia CLI documentation - command-line tool for developing, building, testing, and deploying Rell dapps on Chromia blockchain - [Key pair management in Chromia CLI](https://docs.chromia.com/build/cli/key-pair-management/index.md): This document describes how key pairs are read and managed within the Chromia CLI for various commands. - [Library commands](https://docs.chromia.com/build/cli/library/index.md): The Library commands provide a CLI interface for discovering and installing libraries from the Chromia library registry. - [Clients](https://docs.chromia.com/build/clients/index.md): Clients: every page in this section of the Chromia docs (8 topics). - [Chromia bridge client](https://docs.chromia.com/build/clients/bridge-client/index.md): The Chromia bridge client is a TypeScript library with utilities - [Chromia Filehub client](https://docs.chromia.com/build/clients/filehub-client/index.md): The Filehub client is written in TypeScript for persisting and reading files on - [Chromia FT4 client](https://docs.chromia.com/build/clients/ft4-client/index.md): The FT4 client is written in TypeScript. It is made for easier access to - [Chromia MCP Server](https://docs.chromia.com/build/clients/mcp-server/index.md): A Model Context Protocol (MCP) server that provides access to Chromia blockchain infrastructure and deployed dapps - [Clients](https://docs.chromia.com/build/clients/overview/index.md): The Clients section highlights tools and libraries that enable integration of applications with the Chromia - [Chromia Postchain clients](https://docs.chromia.com/build/clients/postchain-clients/index.md): Postchain clients offer libraries for interacting with a blockchain using JavaScript/TypeScript, Kotlin, C#, Rust, or - [C# client](https://docs.chromia.com/build/clients/postchain-clients/c-sharp-client/index.md): client - [Go client](https://docs.chromia.com/build/clients/postchain-clients/go-client/index.md): The Go client offers a range of built-in functions and utilities designed to simplify interaction with decentralized - [JavaScript/TypeScript client](https://docs.chromia.com/build/clients/postchain-clients/javascript-typescript/index.md): The JavaScript/TypeScript client library provides a comprehensive set of functions and utilities for interacting with - [Hello World Quickstart](https://docs.chromia.com/build/clients/postchain-clients/javascript-typescript/hello-world-quickstart/index.md): This quickstart guide shows you how to send transactions to a blockchain node running - [JavaScript/TypeScript client details](https://docs.chromia.com/build/clients/postchain-clients/javascript-typescript/reference/index.md): We are currently updating this documentation. While it offers a general overview, some details may be outdated. Please - [Kotlin client](https://docs.chromia.com/build/clients/postchain-clients/kotlin-client/index.md): We are currently updating this documentation. While it offers a general overview, some details may be outdated. Please - [Python client](https://docs.chromia.com/build/clients/postchain-clients/python-client/index.md): We are currently updating this documentation. While it offers a general overview, some details may be outdated. Please - [Rust client](https://docs.chromia.com/build/clients/postchain-clients/rust-client/index.md): We are currently updating this documentation. While it offers a general overview, some details may be outdated. Please - [Postchain Rest API](https://docs.chromia.com/build/clients/postchain-rest-api/index.md): We are currently updating this documentation. While it offers a general overview, some details may be outdated. Please - [Chromia React Kit](https://docs.chromia.com/build/clients/react-kit/index.md): We are currently updating this documentation. While it offers a general overview, some details may be outdated. Please - [Configuration](https://docs.chromia.com/build/configuration/index.md): To build and run a dapp on Chromia, set up your project and configure your blockchain to connect the frontend with the - [Configuration properties](https://docs.chromia.com/build/configuration/blockchain-properties/index.md): This topic outlines the key configuration options available in the BaseBlockChainConfiguration, providing - [Project settings file](https://docs.chromia.com/build/configuration/project-config/index.md): Most configurations for your dapp are available in the project configuration file. By default, it's called - [Project structure](https://docs.chromia.com/build/configuration/project-structure/index.md): In Chromia, projects help you organize your Rell code and resources in a single unit that is easy to store and share. In - [Cookbook](https://docs.chromia.com/build/cookbook/index.md): Cookbook: every page in this section of the Chromia docs (6 topics). - [Account creation](https://docs.chromia.com/build/cookbook/account-creation/index.md): This section contains practical, hands-on recipes for common Chromia CLI development workflows. Each topic provides - [How to create account with open strategy](https://docs.chromia.com/build/cookbook/account-creation/open-strategy/index.md): The open strategy allows developers to create a registration process that does not require users to pay any fees. In - [How to create account with transfer fee strategy](https://docs.chromia.com/build/cookbook/account-creation/transfer-fee-strategy/index.md): The transfer fee strategy allows users to create an account by transferring assets to a non-existent account. Part - [How to create account with transfer open strategy](https://docs.chromia.com/build/cookbook/account-creation/transfer-open-strategy/index.md): The transfer open strategy allows users to create an account by transferring assets to a non-existent account. The - [How to create account with transfer subscription strategy](https://docs.chromia.com/build/cookbook/account-creation/transfer-subscription-strategy/index.md): The transfer subscription strategy allows users to create an account by transferring assets to a non-existent - [CLI](https://docs.chromia.com/build/cookbook/cli/index.md): This section contains practical, hands-on recipes for common Chromia CLI development workflows. Each topic provides - [How to create a new Rell dapp](https://docs.chromia.com/build/cookbook/cli/create-rell-dapp/index.md): Bootstrap a new project with chr create-rell-dapp - [How to run operations](https://docs.chromia.com/build/cookbook/cli/run-operations/index.md): Execute transactions with chr tx commands - [How to run queries](https://docs.chromia.com/build/cookbook/cli/run-queries/index.md): Test your dapp with chr query commands - [How to run tests](https://docs.chromia.com/build/cookbook/cli/run-tests/index.md): Execute project tests with chr test - [Data inspection](https://docs.chromia.com/build/cookbook/data-inspection/index.md): Explore simple, practical recipes for reading on‑chain data (blocks, transactions, events). - [How to get an account by ID](https://docs.chromia.com/build/cookbook/data-inspection/get-account-by-id/index.md): This recipe demonstrates how to retrieve an account from the Chromia blockchain by its ID using the FT4 library. - [How to get accounts by signer](https://docs.chromia.com/build/cookbook/data-inspection/get-account-by-signer/index.md): This recipe demonstrates how to retrieve all accounts associated with a specific signer's public key or EVM address - [How to get account transfer history](https://docs.chromia.com/build/cookbook/data-inspection/get-account-transfer-history/index.md): This recipe demonstrates how to retrieve the transfer history for a specific account on the Chromia blockchain using the - [How to fetch and decode block data](https://docs.chromia.com/build/cookbook/data-inspection/get-block-data/index.md): To fetch and decode block data, first extract the block RID from a given transaction RID, then use Postchain - [How to get and decode transaction data](https://docs.chromia.com/build/cookbook/data-inspection/get-transaction-data/index.md): This recipe demonstrates how to get and decode transaction information from the Chromia blockchain. - [How to get transaction status](https://docs.chromia.com/build/cookbook/data-inspection/get-transaction-status/index.md): This recipe demonstrates how to retrieve the status of a transaction on the Chromia blockchain using its RID (Resource - [Welcome to the Chromia Cookbook](https://docs.chromia.com/build/cookbook/overview/index.md): This Cookbook provides concise, real-world examples and step-by-step recipes for common tasks, from managing accounts - [Create queries](https://docs.chromia.com/build/cookbook/query-creation/index.md): Explore simple, practical recipes for querying blockchain data and inspecting account states. - [How to check account memo requirement](https://docs.chromia.com/build/cookbook/query-creation/check-account-memo-requirement/index.md): This recipe demonstrates how to query whether a given FT4 account requires a memo for transfers on the Chromia - [How to get account balance](https://docs.chromia.com/build/cookbook/query-creation/get-account-balance/index.md): This recipe demonstrates how to fetch an FT4 account balance using an EVM key pair. This is essential for checking asset - [How to make queries with parameters](https://docs.chromia.com/build/cookbook/query-creation/make-query/index.md): This recipe demonstrates how to perform queries with parameters using the postchain-client against a Chromia - [How to implement pagination with FT4](https://docs.chromia.com/build/cookbook/query-creation/pagination-with-ft4/index.md): This recipe demonstrates how to implement cursor-based pagination using FT4 utilities in Rell and consume it from a - [How to implement custom pagination](https://docs.chromia.com/build/cookbook/query-creation/pagination/index.md): This recipe demonstrates how to implement cursor-based pagination using custom pagination utilities in Rell and consume - [Create & manage transactions](https://docs.chromia.com/build/cookbook/transaction-creation/index.md): Explore simple, practical recipes for creating transactions. - [How to call operations with FT4 authentication](https://docs.chromia.com/build/cookbook/transaction-creation/call-operation-with-ft4-auth/index.md): This recipe demonstrates how to call dapp operations that require FT4 authentication using a Web3 provider (e.g., - [How to make crosschain transfers](https://docs.chromia.com/build/cookbook/transaction-creation/crosschain-transfer/index.md): This recipe demonstrates how to perform crosschain transfers between different Chromia blockchains using EVM keys with - [How to enable/disable memo for transfers](https://docs.chromia.com/build/cookbook/transaction-creation/enable-disable-memo/index.md): This recipe demonstrates how to enable or disable the memo requirement for transfers on your account. When enabled, all - [How to make a transfer](https://docs.chromia.com/build/cookbook/transaction-creation/make-transfer/index.md): This recipe demonstrates how to create and execute asset transfers on the Chromia blockchain using both EVM and FT4 key - [How to register assets](https://docs.chromia.com/build/cookbook/transaction-creation/register-asset/index.md): This recipe demonstrates how to register local (non-crosschain) assets using FT4 admin operations. This is essential for - [How to register crosschain assets](https://docs.chromia.com/build/cookbook/transaction-creation/register-crosschain-asset/index.md): This recipe demonstrates how to register crosschain assets using FT4 admin operations. This is essential for enabling - [How to send a simple transaction](https://docs.chromia.com/build/cookbook/transaction-creation/simple-transaction/index.md): This recipe demonstrates how to send a transaction using the signAndSendUniqueTransaction helper function, which - [How to create time-bound transactions](https://docs.chromia.com/build/cookbook/transaction-creation/time-bound-transactions/index.md): This recipe demonstrates how to create transactions that are only valid within a specific time window using the timeb - [How to make a transfer with memo](https://docs.chromia.com/build/cookbook/transaction-creation/transfer-with-memo/index.md): This recipe demonstrates how to create and execute asset transfers that include memo data on the Chromia blockchain. - [Database](https://docs.chromia.com/build/database/index.md): Database: every page in this section of the Chromia docs (2 topics). - [Getting started](https://docs.chromia.com/build/database/getting-started/index.md): Spin up a local Chromia stack, deploy schemas, and explore core database tooling. - [Chromia Database overview](https://docs.chromia.com/build/database/overview/index.md): Understand what makes the Chromia Database unique and when to use it for your application workloads. - [Deployment](https://docs.chromia.com/build/deployment/index.md): Deploy your production-ready dapp to Chromia Mainnet. This section covers the complete deployment process from container - [Deploy the frontend of your dapp on-chain](https://docs.chromia.com/build/deployment/deploy-frontend-dapp/index.md): This topic provides a detailed guide on deploying a frontend application into the blockchain. It includes steps for - [Deploy to Mainnet](https://docs.chromia.com/build/deployment/mainnet/index.md): This section covers information about configuring your client and deploying and updating your dapp to the public - [Connect a client](https://docs.chromia.com/build/deployment/mainnet/connect-client/index.md): This section covers how to connect a frontend or other client to a dapp backend deployed on a Chromia network. The - [Deploy your dapp to Mainnet](https://docs.chromia.com/build/deployment/mainnet/deploy-dapp/index.md): This topic covers deploying and updating a dapp with the Chromia CLI to the public Mainnet. For more information, see - [Get a container for your dapp](https://docs.chromia.com/build/deployment/mainnet/get-container/index.md): In this topic, you'll go through the steps of getting a container for your dapp. - [Get started with Mainnet deployment](https://docs.chromia.com/build/deployment/mainnet/getting-started/index.md): Deploying a decentralized application (dapp) to the Chromia Mainnet involves several key steps. Here's an overview of - [Multi-owner dapp deployment and updates](https://docs.chromia.com/build/deployment/mainnet/multi-deployment/index.md): This guide provides step-by-step instructions for deploying and updating decentralized applications (dapps) on Chromia - [Get Testnet tokens](https://docs.chromia.com/build/deployment/testnet-tokens/index.md): In this section you will discover how to claim Testnet tokens on the Chromia Testnet and Binance Testnets. - [Get Chromia test tokens (tCHR) on Binance Smart Chain Testnet](https://docs.chromia.com/build/deployment/testnet-tokens/get-tchr-binance/index.md): This guide will walk you through obtaining test tokens (tCHR) on the Binance Smart Chain Testnet. These tokens can be - [Get Chromia test tokens (tCHR) on the Chromia Testnet](https://docs.chromia.com/build/deployment/testnet-tokens/get-tchr-chromia/index.md): This guide will walk you through obtaining test tokens (tCHR) on the Chromia Testnet. These tokens are essential for - [Deploy to testnet](https://docs.chromia.com/build/deployment/testnet/index.md): This section covers information about configuring your client and deploying and updating your dapp to the public - [Connect a client](https://docs.chromia.com/build/deployment/testnet/connect-client/index.md): This section covers how to connect a frontend or other client to a dapp backend deployed on a Chromia network. The - [Deploy your dapp to testnet](https://docs.chromia.com/build/deployment/testnet/deploy-dapp/index.md): This topic covers deploying and updating a dapp with the Chromia CLI to the public testnet. For more information, see - [Get a container for your dapp](https://docs.chromia.com/build/deployment/testnet/get-container/index.md): In this section, you’ll complete the steps needed to obtain a container for your dapp. - [Getting started](https://docs.chromia.com/build/deployment/testnet/getting-started/index.md): Deploying a decentralized application (dapp) to the Chromia testnet involves several key steps. Here's an overview of - [List your dapp on the Chromia Testnet Vault](https://docs.chromia.com/build/deployment/testnet/list-dapp-vault/index.md): This guide provides step-by-step instructions for listing your decentralized application (dapp) on the Chromia Testnet - [List your dapp on the Chromia Vault](https://docs.chromia.com/build/deployment/vault-listing/index.md): To list your dapp on the Chromia Vault, you need to implement a finddappdetails query that provides metadata about - [Dynamic Vault listing (database-based metadata)](https://docs.chromia.com/build/deployment/vault-listing/dynamic-vault-listing/index.md): Flexible approach to list your dapp on the Chromia Vault using database-stored metadata. Perfect for production dapps or - [Quick Vault listing (hardcoded metadata)](https://docs.chromia.com/build/deployment/vault-listing/quick-vault-listing/index.md): Fast and simple approach to list your dapp on the Chromia Vault using hardcoded metadata. Perfect for quick prototypes - [FT4](https://docs.chromia.com/build/ft4/index.md): FT4: every page in this section of the Chromia docs (12 topics). - [Account management](https://docs.chromia.com/build/ft4/account-management/index.md): FT4 provides flexible account management for dapps, supporting multi-user accounts and customizable registration - [Auth descriptors](https://docs.chromia.com/build/ft4/account-management/auth-descriptors/index.md): One of the core features of FT4 is the ability to use multiple key pairs or accounts to control a single account. - [Introduction to Multisig](https://docs.chromia.com/build/ft4/account-management/multisig/index.md): When handling on-chain operations as an organization, it is in general a good idea to use multisignature access, or - [Manage FT4 accounts](https://docs.chromia.com/build/ft4/account-management/overview/index.md): FT4 provides powerful tools for managing accounts in a decentralized environment. Each account is represented by an ID, - [Asset management](https://docs.chromia.com/build/ft4/asset-management/index.md): FT4 provides tools to easily manage your assets, such as tokens, on the Chromia blockchain. You can register new assets, - [Manage assets in FT4](https://docs.chromia.com/build/ft4/asset-management/asset/index.md): FT4 offers extensive asset management capabilities, supporting multiple types of assets within the same ecosystem. Each - [Transfer assets](https://docs.chromia.com/build/ft4/asset-management/transfer-assets/index.md): FT4 assets on Chromia can be transferred both on-chain (within a single blockchain) and cross-chain (across - [FT4 Backend](https://docs.chromia.com/build/ft4/backend/index.md): FT4 provides a comprehensive set of tools for managing decentralized applications, with features for flexible account - [Accounts](https://docs.chromia.com/build/ft4/backend/accounts/index.md): FT4 accounts can be registered with transfer open, transfer fee, or transfer subscription strategies, each offering - [Link FT4 accounts](https://docs.chromia.com/build/ft4/backend/accounts/account-linking/index.md): The account_link entity is a versatile structure designed to represent a relationship between two accounts. This - [Use auth descriptors for accounts](https://docs.chromia.com/build/ft4/backend/accounts/accounts-and-auth-descriptors/index.md): Accounts can have multiple account descriptors connected to them. Each can be made to serve a different purpose, but the - [Transfer fee strategy](https://docs.chromia.com/build/ft4/backend/accounts/fixed/index.md): The transfer fee strategy simplifies the process for users by requiring a one-time purchase of a specific amount of - [Transfer open strategy](https://docs.chromia.com/build/ft4/backend/accounts/open/index.md): The transfer open strategy requires users to transfer a specific amount of tokens to a non-existent account, which they - [Register FT4 accounts](https://docs.chromia.com/build/ft4/backend/accounts/overview/index.md): In the FT4 library, accounts function as digital identities, enabling users to transfer assets, interact with dapps, and - [Transfer subscription strategy](https://docs.chromia.com/build/ft4/backend/accounts/subscription/index.md): When implementing a transfer subscription strategy for your dapp, users will need to pay regularly to access its - [Assets](https://docs.chromia.com/build/ft4/backend/assets/index.md): FT4 allows secure asset registration, ensuring unique identity and metadata via admin or custom operations. Asset - [Manage asset balances](https://docs.chromia.com/build/ft4/backend/assets/asset-amounts/index.md): The FT4 library allows managing various assets, each potentially having its own precision and formatting requirements, - [Lock FT4 assets](https://docs.chromia.com/build/ft4/backend/assets/locking-assets/index.md): In the FT4 library, a "lock account" functions as a secure storage for assets that users should not be able to access - [Register assets in FT4](https://docs.chromia.com/build/ft4/backend/assets/register-assets/index.md): Asset registration is a crucial process within the FT4 library. It involves defining and initializing new assets (such - [Authentication](https://docs.chromia.com/build/ft4/backend/authentication/index.md): FT4 authentication utilizes auth descriptors to define key pairs, permissions, and multi-signature security. Custom auth - [Set up auth descriptors](https://docs.chromia.com/build/ft4/backend/authentication/auth-descriptors-and-rules/index.md): Auth descriptors are a mechanism that defines the authorized key pairs and their associated permissions for interacting - [Use auth handlers for authentication](https://docs.chromia.com/build/ft4/backend/authentication/auth/index.md): Authentication in decentralized applications (dapps) verifies if a user has permission to perform specific actions. - [Handle multi-signature transactions](https://docs.chromia.com/build/ft4/backend/authentication/multi-sig/index.md): Multi-signature (multi-sig) transactions provide an added layer of security and shared control over blockchain - [Cross-chain](https://docs.chromia.com/build/ft4/backend/cross-chain/index.md): FT4 enables smooth asset transfers within the Chromia network, supporting stages like inittransfer, applytransfer, and - [Automate cross-chain asset registration](https://docs.chromia.com/build/ft4/backend/cross-chain/automate-cross-chain-asset-registration/index.md): This topic provides an example of automating cross-chain FT4 asset registration. It is not intended as a best practices - [Manage cross-chain assets](https://docs.chromia.com/build/ft4/backend/cross-chain/cross-chain-assets/index.md): In the FT4 library, cross-chain assets are assets that originate on one blockchain but can be registered, tracked, and - [Transfer assets across chains](https://docs.chromia.com/build/ft4/backend/cross-chain/cross-chain-transfers/index.md): This topic provides information about the architecture that's designed to facilitate the seamless transfer of FT4 assets - [Get started with cross-chain operations](https://docs.chromia.com/build/ft4/backend/cross-chain/introduction/index.md): Cross-chain transfers enable seamless asset movements between multiple blockchains. Within the Chromia network, - [Client](https://docs.chromia.com/build/ft4/client/index.md): The FT4 Client provides the interface through which applications interact with the blockchain. It facilitates operations - [Register an account](https://docs.chromia.com/build/ft4/client/client-account-registration/index.md): This section demonstrates how to register a new account on the blockchain using either Chromia-native keys or - [Use auth descriptors](https://docs.chromia.com/build/ft4/client/client-auth-descriptors/index.md): The FT4 client library provides flexible tools for creating Single-Signature (SingleSig) and Multi-Signature - [Manage key stores](https://docs.chromia.com/build/ft4/client/client-key-store/index.md): In the FT4 client library, the KeyStore interface represents a general abstraction for managing cryptographic keys. - [Disposable keys and login management](https://docs.chromia.com/build/ft4/client/client-login/index.md): To improve the user experience in web applications, FT4 provides a mechanism for generating disposable keys and adding - [Perform cross-chain transfers](https://docs.chromia.com/build/ft4/client/client-orchestrator/index.md): The orchestrator is a utility object that facilitates cross-chain transfers. It can be instantiated, listen to events, - [FT4 client setup with TypeScript](https://docs.chromia.com/build/ft4/client/client-setup/index.md): This section discusses how to install and initialize the FT4 client. - [Transfer assets with FT4 client](https://docs.chromia.com/build/ft4/client/client-transfer-assets/index.md): Transferring assets is a fundamental operation in decentralized applications built on the FT4 framework. FT4 provides a - [Code examples](https://docs.chromia.com/build/ft4/code-examples/index.md): This section showcases practical examples demonstrating how to use the client library. These scripts provide valuable - [FT4 configuration values](https://docs.chromia.com/build/ft4/configuration-values/index.md): This topic provides the key configuration options available for FT4 modules, providing descriptions, types, and default - [FT4 (Flexible Token 4)](https://docs.chromia.com/build/ft4/intro/index.md): Chromia FT4 (Flexible Token 4) is an advanced token standard designed for the Chromia blockchain, offering enhanced - [Pagination](https://docs.chromia.com/build/ft4/pagination/index.md): Each query in FT4 has pagination enabled by default. The query will return a paged result containing the result and the - [Prioritize transactions](https://docs.chromia.com/build/ft4/prioritization/index.md): The prioritization is used to determine which transactions should be processed first on the blockchain. The FT4 library - [Releases](https://docs.chromia.com/build/ft4/releases/index.md): Releases: every page in this section of the Chromia docs (1 topics). - [FT4 changelog](https://docs.chromia.com/build/ft4/releases/ft4/index.md): All notable changes to this project will be documented in this file. - [Project setup](https://docs.chromia.com/build/ft4/setup/index.md): Setting up your FT4 project involves installing the necessary packages, configuring your project files, and initializing - [Set up your FT4 project](https://docs.chromia.com/build/ft4/setup/ft4-setup/index.md): In this section, you'll learn how to set up a project to use FT4. If you want to see an example of a complete dapp using - [Import FT4 into your project](https://docs.chromia.com/build/ft4/setup/imports/index.md): When you import the entire FT4 library, you might unintentionally expose many operations. It's crucial to consider - [Glossary](https://docs.chromia.com/build/ft4/terms/index.md): This section provides a high-level explanation of the terms most commonly used in the documentation for the FT4 library. - [Integrations](https://docs.chromia.com/build/integrations/index.md): Chromia integrations provide comprehensive guides and tools for seamlessly connecting external systems, exchanges, and - [Exchange integration guide](https://docs.chromia.com/build/integrations/exchange-guide/index.md): This guide is designed for technical teams at exchanges that have decided to list Chromia and are focused on completing - [Additional resources](https://docs.chromia.com/build/integrations/exchange-guide/additional-resources/index.md): - Official website - [Core concepts of Chromia](https://docs.chromia.com/build/integrations/exchange-guide/overview/index.md): Chromia is a Layer-1 blockchain platform designed to deliver high performance and scalability for decentralized - [Step 1: Account creation](https://docs.chromia.com/build/integrations/exchange-guide/step-1-account/index.md): Creating an account on Chromia's Economy Chain is a crucial first step for integrating with the network. An account acts - [Step 2: Access Chromia's Economy Chain](https://docs.chromia.com/build/integrations/exchange-guide/step-2-access/index.md): To access Chromia's Economy Chain, you have two primary options: - [Step 3: Deposits, withdrawals, and transaction monitoring](https://docs.chromia.com/build/integrations/exchange-guide/step-3-transaction/index.md): Handling deposits, withdrawals, and monitoring transactions are essential components of integrating with Chromia's - [Step 4: Sending assets to non-existent accounts](https://docs.chromia.com/build/integrations/exchange-guide/step-4-non-existent-accounts/index.md): Exchanges can send assets to users who do not yet have a Chromia account by transferring funds to an unregistered - [Memo integration guide](https://docs.chromia.com/build/integrations/memo-guide/index.md): The memo feature adds an optional memo requirement for FT4 transfers, ensuring that certain accounts mandate memos for - [Token Chain](https://docs.chromia.com/build/token-chain/index.md): The Token Chain provides functionality for token management, account creation, and bridge setup. This section covers the - [Developer token proposal and bridge setup](https://docs.chromia.com/build/token-chain/developer-token-proposal/index.md): Developers and project teams can propose new FT4 tokens and optional bridges on the Token Chain. The process includes - [User account creation](https://docs.chromia.com/build/token-chain/user-account-creation/index.md): End users interacting with dapps on Chromia will need an account on the Token Chain to bridge assets or hold newly - [Vector search](https://docs.chromia.com/build/vector-search/index.md): Vector search: every page in this section of the Chromia docs (2 topics). - [Vector and Search overview](https://docs.chromia.com/build/vector-search/overview/index.md): Learn how Chromia pairs relational data with native vector and full-text search workloads. - [Sample workloads](https://docs.chromia.com/build/vector-search/sample-workloads/index.md): Try common AI-powered use cases on Chromia's vector-ready data layer. ## Ecosystem - [Ecosystem](https://docs.chromia.com/ecosystem/index.md): Ecosystem: every page in this section of the Chromia docs (6 topics). - [Block Explorer](https://docs.chromia.com/ecosystem/block-explorer/index.md): The Chromia Block Explorer is a comprehensive tool for monitoring blockchain activity on both Mainnet and Testnet - [Explorer features](https://docs.chromia.com/ecosystem/block-explorer/features/index.md): The Chromia Block Explorer is a blockchain explorer for the Chromia Mainnet and Testnet that provides a - [About Chromia Block Explorer](https://docs.chromia.com/ecosystem/block-explorer/overview/index.md): Chromia Block Explorer is a powerful tool that provides insight into transactions and network activity within the - [Use the Block Explorer to test and validate your dapp deployment](https://docs.chromia.com/ecosystem/block-explorer/using-explorer/index.md): Search for blockchain data - [Bridge](https://docs.chromia.com/ecosystem/bridge/index.md): Bridge: every page in this section of the Chromia docs (6 topics). - [Chromia bridge client](https://docs.chromia.com/ecosystem/bridge/bridge-client/index.md): This section covers how to set up Chromia bridge client to facilitate token transfers between Chromia and Ethereum - [Configure the Chromia bridge client](https://docs.chromia.com/ecosystem/bridge/bridge-client/client/index.md): The Chromia bridge client is a TypeScript library with utilities - [Example usage: Bridge from EVM to Chromia and vice versa](https://docs.chromia.com/ecosystem/bridge/bridge-client/example/index.md): Bridge from EVM to Chromia - [Work with the client](https://docs.chromia.com/ecosystem/bridge/bridge-client/work-with-client/index.md): To interact with the Chromia blockchain using the bridge client, you'll need to manage an active Session that handles - [Lease a bridge](https://docs.chromia.com/ecosystem/bridge/bridge-lease/index.md): Leasing a bridge allows you to utilize the Chromia bridge component without manually deploying it. This process replaces - [Troubleshoot the deployed bridge](https://docs.chromia.com/ecosystem/bridge/bridge-troubleshooting/index.md): This section provides a guide for troubleshooting and debugging a Chromia Bridge deployment to help identify any - [Bridge deposit troubleshooting guide](https://docs.chromia.com/ecosystem/bridge/bridge-troubleshooting/bridge-deposit-troubleshooting/index.md): If your deposit from the EVM to Chromia does not appear on the Chromia side, follow these steps to identify and resolve - [Bridge withdrawal troubleshooting guide](https://docs.chromia.com/ecosystem/bridge/bridge-troubleshooting/bridge-withdraw-troubleshooting/index.md): If your withdrawal from Chromia to EVM doesn't appear on the EVM chain, follow these steps to identify and resolve the - [Deploy the bridge](https://docs.chromia.com/ecosystem/bridge/deploy-bridge/index.md): This section outlines the process of deploying the Chromia and EVM components of a token bridge, using BSC - [Deploy Chromia bridge chains](https://docs.chromia.com/ecosystem/bridge/deploy-bridge/deploy-bridge-chains/index.md): This section describes deploying the Event Receiver Chain and the Bridge Chain on Chromia, enabling ERC20 token - [Deploy the token bridge contract](https://docs.chromia.com/ecosystem/bridge/deploy-bridge/deploy-bridge-contract/index.md): This section walks through deploying the token bridge contract on BSC Testnet, enabling ERC20 token transfers - [Deploy an ERC20 token](https://docs.chromia.com/ecosystem/bridge/deploy-bridge/deploy-erc20-token/index.md): This section walks through deploying the ALICE ERC20 token on the BSC Testnet using Hardhat. - [Interact with the frontend](https://docs.chromia.com/ecosystem/bridge/deploy-bridge/interact-with-frontend/index.md): This section guides you through configuring and running the frontend for the Chromia Bridge Demo. - [Register the Chromia bridge on EVM](https://docs.chromia.com/ecosystem/bridge/deploy-bridge/register-bridge/index.md): To enable transfers between networks, we need to register the Chromia bridge component on the EVM bridge contract so - [Mass exit](https://docs.chromia.com/ecosystem/bridge/mass-exit/index.md): This section explains how to secure user funds using snapshot-based withdrawals in the event of validator - [Mass exit operations](https://docs.chromia.com/ecosystem/bridge/mass-exit/operations/index.md): This section explains how to trigger the mass exit process and enable users to withdraw their funds using account state - [How mass exit works](https://docs.chromia.com/ecosystem/bridge/mass-exit/overview/index.md): Mass exit serves as a critical emergency mechanism in the Chromia token bridge, safeguarding user funds when a crisis - [Mass exit API and CLI reference](https://docs.chromia.com/ecosystem/bridge/mass-exit/reference/index.md): This topic summarizes key CLI commands, Rell queries, and EVM contract calls used throughout the mass exit flow. - [Set up mass exit](https://docs.chromia.com/ecosystem/bridge/mass-exit/setup/index.md): This guide helps you enable the mass exit mechanism by configuring your bridge contracts and Chromia chains for - [EVM bridge](https://docs.chromia.com/ecosystem/bridge/overview/index.md): Chromia provides a bridging mechanism called Ethereum Interoperability Framework (EIF) that allows transferring ERC-20 - [Extensions](https://docs.chromia.com/ecosystem/extensions/index.md): Chromia extensions enhance the ecosystem by providing modular and scalable features that help developers quickly - [AI Inference](https://docs.chromia.com/ecosystem/extensions/ai_inference/index.md): The AI Inference extension brings AI inference capabilities directly into dapps, enabling intelligent, real-time - [What are Chromia extensions?](https://docs.chromia.com/ecosystem/extensions/overview/index.md): Chromia extensions serve as pre-built docker images that add specialized features or services to containers within the - [Stork Oracle](https://docs.chromia.com/ecosystem/extensions/stork/index.md): Stork is the leading oracle for low-latency DeFi protocols, delivering price data at ultra-low latency. Stork supports a - [Vector DB](https://docs.chromia.com/ecosystem/extensions/vector-db/index.md): Chromia’s Vector DB extension allows for the efficient storage and querying of complex multi-dimensional data in a - [Zero-knowledge Proof](https://docs.chromia.com/ecosystem/extensions/zkp/index.md): The Zero-knowledge Proof (ZKP) extension for Chromia enables developers to integrate advanced privacy-preserving - [Filehub](https://docs.chromia.com/ecosystem/filehub/index.md): Filehub: every page in this section of the Chromia docs (3 topics). - [Configure and work with Filehub](https://docs.chromia.com/ecosystem/filehub/configure-filehub/index.md): This section covers how to configure Filehub, including Filechain registration, payment setup, and enabling/disabling - [Configure Filehub](https://docs.chromia.com/ecosystem/filehub/configure-filehub/filehub-configure/index.md): This topic describes the steps to set up and manage a Filehub instance effectively. It covers how to register - [Work with Filehub](https://docs.chromia.com/ecosystem/filehub/configure-filehub/filehub-work/index.md): Filehub allows users to store files on-chain and retrieve them using the - [Filehub setup and deployment](https://docs.chromia.com/ecosystem/filehub/filehub-setup/index.md): This section covers the setup and deployment of Filehub, including the configuration of Filehub, Filechain, and the - [Deploy Filehub and Filechain bundle](https://docs.chromia.com/ecosystem/filehub/filehub-setup/deploy-bundle/index.md): A Filechain is inherently dependent on a Filehub, meaning that each Filechain must be deployed in conjunction with a - [Deploy Filechain](https://docs.chromia.com/ecosystem/filehub/filehub-setup/deploy-filechain/index.md): This topic outlines how to deploy a Filechain, which serves as a storage solution for managing and storing file chunks - [Deploy Filehub](https://docs.chromia.com/ecosystem/filehub/filehub-setup/deploy-filehub/index.md): This topic outlines how to deploy a Filehub instance. Filehub acts as a decentralized solution for managing file storage - [Overview of Filehub](https://docs.chromia.com/ecosystem/filehub/overview/index.md): Filehub is a scalable, reliable, and secure storage platform that Chromia's relational blockchain powers. It provides - [Governance](https://docs.chromia.com/ecosystem/governance/index.md): Governance: every page in this section of the Chromia docs (5 topics). - [Alternative solutions](https://docs.chromia.com/ecosystem/governance/alternative-sol/index.md): Comparison of governance systems - [Getting started](https://docs.chromia.com/ecosystem/governance/getting-started/index.md): This section provides step-by-step guidance on how to use the Governance Tool. You will learn how to set up governance, - [Extensions](https://docs.chromia.com/ecosystem/governance/getting-started/extensions/index.md): Extensions are modular components in the library that enhance the Governance Tool's functionality. They enable you to - [Governance Tool Delegates extension](https://docs.chromia.com/ecosystem/governance/getting-started/extensions/delegates/index.md): The Governance Tool Delegates extension introduces delegate functionality to your dapp. This means that users can - [Governance Tool EIF extension](https://docs.chromia.com/ecosystem/governance/getting-started/extensions/eif/index.md): The Governance Tool EIF extension enables synchronization with EVM events and handles them within the dapp. It uses - [Governance Tool ICMF extension](https://docs.chromia.com/ecosystem/governance/getting-started/extensions/icmf/index.md): The Governance Tool ICMF extension adds ICMF functionality to your decentralized application (dapp). It is important not - [The Governance Tool Starter Kit](https://docs.chromia.com/ecosystem/governance/getting-started/governance-starter-kit/index.md): Unlock decentralized governance with the Governance Tool Starter Kit. This guide helps you set up and manage governance - [Customizing functions](https://docs.chromia.com/ecosystem/governance/getting-started/governance-starter-kit/customize-functions/index.md): The Governance Tool allows you to create reusable code components tailored to your Decentralized Autonomous Organization - [Customizing with EIF and event configuration](https://docs.chromia.com/ecosystem/governance/getting-started/governance-starter-kit/eif-configuration/index.md): This topic provides a detailed explanation of the EIF configuration in chromia.yml, which defines chain-specific - [Setting up governance in your project](https://docs.chromia.com/ecosystem/governance/getting-started/governance-starter-kit/import/index.md): To build and run the Governance Tool on Chromia, you need to set up the project and properly configure the blockchain to - [Governance Starter Kit](https://docs.chromia.com/ecosystem/governance/getting-started/governance-starter-kit/overview/index.md): The Governance Tool Starter Kit is a - [Governance structure](https://docs.chromia.com/ecosystem/governance/getting-started/governance-structure/index.md): This section offers an overview of the Governance Tool, focusing on its key modules, user roles, and the proposal - [Key modules in the governance system](https://docs.chromia.com/ecosystem/governance/getting-started/governance-structure/key-modules/index.md): This topic outlines the core components of the Governance Tool, detailing how citizens interact with proposals, voting, - [User and proposal flows](https://docs.chromia.com/ecosystem/governance/getting-started/governance-structure/user-proposal-flows/index.md): User flow - [User types](https://docs.chromia.com/ecosystem/governance/getting-started/governance-structure/user-types/index.md): The governance system comprises four main user roles, each with specific rights and responsibilities. - [Vote power strategies](https://docs.chromia.com/ecosystem/governance/getting-started/governance-structure/vote-power-strategies/index.md): Vote power strategies are used to calculate the voting power of a user. You can add any strategy you want to the - [Vote requirements](https://docs.chromia.com/ecosystem/governance/getting-started/governance-structure/vote-requirements/index.md): Vote requirements are criteria used to determine whether a user has sufficient voting power to participate in a - [Vote weight strategies](https://docs.chromia.com/ecosystem/governance/getting-started/governance-structure/vote-weight-strategy/index.md): Vote weight strategies are methods used to determine the weight of a vote. The LINEAR calculation is the standard vote - [Rell overview](https://docs.chromia.com/ecosystem/governance/getting-started/rell-language/index.md): Rell is a programming language designed explicitly for dapp development on the Chromia blockchain. - [Work with proposals](https://docs.chromia.com/ecosystem/governance/governance-proposals/index.md): This section covers how to create and manage proposals within the Governance Tool. - [Create a proposal](https://docs.chromia.com/ecosystem/governance/governance-proposals/create-proposal/index.md): Creating a proposal is the first step in a governance dapp, which allows citizens to suggest changes or decisions for - [Voting process](https://docs.chromia.com/ecosystem/governance/governance-voting-process/index.md): This section explains how voting works in the Governance Tool and how you can participate in the decision-making - [Vote on a proposal](https://docs.chromia.com/ecosystem/governance/governance-voting-process/vote-proposal/index.md): Voting is an essential part of the Governance Tool, enabling citizens to participate in decision-making. Follow the - [Voting flow](https://docs.chromia.com/ecosystem/governance/governance-voting-process/voting-flow/index.md): Voting requirements and strategies for voting power - [Voting types](https://docs.chromia.com/ecosystem/governance/governance-voting-process/voting-types/index.md): The Governance Tool operates on a simple majority voting system. This approach counts only the percentage of "yes" votes - [Overview](https://docs.chromia.com/ecosystem/governance/overview/index.md): The Governance Tool is an advanced, on-chain voting solution built on the Chromia blockchain. It - [Providers](https://docs.chromia.com/ecosystem/providers/index.md): Providers: every page in this section of the Chromia docs (7 topics). - [APIs](https://docs.chromia.com/ecosystem/providers/apis-1/index.md): This section provides detailed information on the Postchain APIs and REST tools, which facilitate querying nodes on the Chromia network or a - [Blockchain authentication of Directory Chain operations](https://docs.chromia.com/ecosystem/providers/blockchain-based-provider-authentication/index.md): Blockchain authentication allows you to authenticate your provider operations through a transaction on another - [Container management](https://docs.chromia.com/ecosystem/providers/container-management/index.md): This section outlines a clear step-by-step process for adding a dapp provider to your container voter set and - [Add a dapp provider to your container voter set](https://docs.chromia.com/ecosystem/providers/container-management/add-dapp-provider-to-voterset/index.md): When you lease a container, you must provide the public key of an initial dapp provider to manage the container. This - [Transfer container lease ownership](https://docs.chromia.com/ecosystem/providers/container-management/transfer-container-ownership/index.md): This guide provides a comprehensive overview of how to transfer ownership of a container lease from one user to another, - [Set up and start a node](https://docs.chromia.com/ecosystem/providers/nodes/index.md): This section guides you through the complete process of installing PMC, configuring the provider keypair, setting up - [Add a node to the network](https://docs.chromia.com/ecosystem/providers/nodes/add-node/index.md): Register the node - [Add a replica node to the network](https://docs.chromia.com/ecosystem/providers/nodes/add-replica-node/index.md): A Chromia replica node plays a vital role in the Chromia blockchain ecosystem. Its main duty is to maintain a complete - [Node management API](https://docs.chromia.com/ecosystem/providers/nodes/api/index.md): When postchain is run in managed mode (as it always does with a management chain), the module in bc0 must fulfill a - [Automated network setup](https://docs.chromia.com/ecosystem/providers/nodes/automated-network-setup/index.md): This guide details the repository containing a script that automates the - [Change the FT4 key](https://docs.chromia.com/ecosystem/providers/nodes/change-ft4-key/index.md): In the Chromia network, the system uses the provider key by default for both controlling the financial FT4 account and - [Configure Directory Chain](https://docs.chromia.com/ecosystem/providers/nodes/directory-chain-config/index.md): Module arguments - [Configure Economy Chain](https://docs.chromia.com/ecosystem/providers/nodes/economy-chain-config/index.md): Module arguments - [Install PMC CLI](https://docs.chromia.com/ecosystem/providers/nodes/install-pmc/index.md): The Postchain Management Console (PMC) CLI is a command-line interface that submits transactions to the management - [Enable logging and monitoring](https://docs.chromia.com/ecosystem/providers/nodes/logging/index.md): Prometheus - [Provider key management](https://docs.chromia.com/ecosystem/providers/nodes/manage-provider-keys/index.md): This guide explains how to manage provider keys for signing operations in the - [Configure node properties](https://docs.chromia.com/ecosystem/providers/nodes/node-config/index.md): This topic outlines node properties that can be configured via properties files or environment variables. For - [Node maintenance guidelines](https://docs.chromia.com/ecosystem/providers/nodes/node-maintenance-guidelines/index.md): Regular maintenance of provider nodes helps improve network stability and security by adding new features or fixing - [Prepare the node for deployment](https://docs.chromia.com/ecosystem/providers/nodes/prepare-node/index.md): Before you start a node, you must install the PostgreSQL database. For more information, see - [Configure provider key pair](https://docs.chromia.com/ecosystem/providers/nodes/provider-keypair/index.md): On the Chromia network, key pairs have different meanings and responsibilities. As a provider, you typically handle two - [Monitor your node with Prometheus and Grafana](https://docs.chromia.com/ecosystem/providers/nodes/setup-prometheus/index.md): When running a node, it's crucial to set up effective monitoring to ensure quick response times in case of failures and - [Set up a reverse proxy for TLS](https://docs.chromia.com/ecosystem/providers/nodes/setup-tls/index.md): Enabling TLS (Transport Layer Security) is essential for securing all nodes within the network. This can be achieved by - [Start a node](https://docs.chromia.com/ecosystem/providers/nodes/start-a-node/index.md): To start a node, you need to complete a few prerequisites. - [Upgrade Postchain](https://docs.chromia.com/ecosystem/providers/nodes/upgrade-postchain/index.md): This guide provides step-by-step instructions for upgrading Postchain to a new version. The process differs depending on - [Introduction to providers](https://docs.chromia.com/ecosystem/providers/overview/index.md): Providers are the backbone of the Chromia ecosystem. A provider is a person or organization responsible for nodes, which - [Postchain Management Console CLI](https://docs.chromia.com/ecosystem/providers/pmc/index.md): The Postchain Management Console (PMC) is a command line tool that submits transactions to the Directory and Economy - [PMC command reference](https://docs.chromia.com/ecosystem/providers/pmc/commands/index.md): This section contains information about all commands and settings available in the Chromia PMC CLI, including examples - [blockchain](https://docs.chromia.com/ecosystem/providers/pmc/commands/blockchain/index.md): The blockchain command (pmc blockchain) consists of sub-commands to interact with blockchains. For example, list - [cluster-anchoring](https://docs.chromia.com/ecosystem/providers/pmc/commands/cluster-anchoring/index.md): The blockchain command (pmc cluster-anchoring) consists of sub-commands to interact with Cluster Anchoring Chain - [cluster](https://docs.chromia.com/ecosystem/providers/pmc/commands/cluster/index.md): The cluster command (pmc cluster) consists of sub-commands to interact with clusters. For example, list existing - [config](https://docs.chromia.com/ecosystem/providers/pmc/commands/config/index.md): You can use the command (pmc config) to edit the configuration of the PMC. It uses the local config file if a global - [container](https://docs.chromia.com/ecosystem/providers/pmc/commands/container/index.md): The container command (pmc container) consists of sub-commands to interact with containers. For example, list existing - [economy](https://docs.chromia.com/ecosystem/providers/pmc/commands/economy/index.md): The economy command (pmc economy) consists of sub-commands to interact with the Economy Chain. For example, create - [help](https://docs.chromia.com/ecosystem/providers/pmc/commands/help/index.md): The help command (pmc help) displays the help message for PMC and exits. - [keygen](https://docs.chromia.com/ecosystem/providers/pmc/commands/keygen/index.md): The keygen command (pmc keygen) generates a public and private key pair. An elliptic curve secp256k1 generates these - [lease](https://docs.chromia.com/ecosystem/providers/pmc/commands/lease/index.md): The lease command (pmc lease) has sub-commands for container lease. - [network](https://docs.chromia.com/ecosystem/providers/pmc/commands/network/index.md): The network command (pmc network) consists of sub-commands that initialize a network and show a summary or version of - [node](https://docs.chromia.com/ecosystem/providers/pmc/commands/node/index.md): The node command (pmc node) consists of sub-commands used to manage nodes. - [proposal](https://docs.chromia.com/ecosystem/providers/pmc/commands/proposal/index.md): The command (pmc proposal) has sub-commands to see and vote on existing proposals in the network. - [provider](https://docs.chromia.com/ecosystem/providers/pmc/commands/provider/index.md): The provider command (pmc provider) consists of sub-commands used to manage providers. - [subnode-jar-extension](https://docs.chromia.com/ecosystem/providers/pmc/commands/subnode-jar-extension/index.md): The subnode-jar-extension command (pmc subnode-jar-extension) consists of sub-commands used to manage subnode JAR - [subnode-image](https://docs.chromia.com/ecosystem/providers/pmc/commands/subnode/index.md): The subnode-image command (pmc subnode-image) consists of sub-commands used to manage subnode image. - [transaction](https://docs.chromia.com/ecosystem/providers/pmc/commands/transaction/index.md): The transaction command (pmc transaction) consists of sub-commands to interact with transactions. For example, send - [version](https://docs.chromia.com/ecosystem/providers/pmc/commands/version/index.md): The version command (pmc version) displays the current version of the PMC CLI tool and exits. - [voterset](https://docs.chromia.com/ecosystem/providers/pmc/commands/voterset/index.md): The node command (pmc voterset) comprises sub-commands that manage voter sets. - [Install PMC CLI](https://docs.chromia.com/ecosystem/providers/pmc/pmccli-installation/index.md): This topic contains instructions to install and update Postchain Management Console (PMC) CLI. - [Postchain troubleshooting](https://docs.chromia.com/ecosystem/providers/pmc/troubleshooting/index.md): While Postchain is designed to be robust and reliable, issues can still arise from time to time. This topic covers some - [Provider rewards](https://docs.chromia.com/ecosystem/providers/rewards/index.md): Providers receive compensation from a pool of all fees paid by dapps for containers on the network. The compensation a ## Reference - [Reference](https://docs.chromia.com/reference/index.md): Reference: every page in this section of the Chromia docs (2 topics). - [FT4 API reference](https://docs.chromia.com/reference/ft4/index.md): Links to the autogenerated FT4 Rell and TypeScript API reference docs. - [Terminology](https://docs.chromia.com/reference/terminology/index.md): Account ID ## Updates - [Recent Updates](https://docs.chromia.com/updates/index.md): This page tracks major improvements and changes made to the Chromia documentation over time. Our goal is to continuously ## API reference (generated) - [FT4 Rell](https://docs.chromia.com/pages/ft4-rell/) - [FT4 TypeScript client](https://docs.chromia.com/pages/ft4-ts-client/) - [Postchain REST API](https://docs.chromia.com/pages/postchain-restapi/) - [Rell standard library](https://docs.chromia.com/pages/rell-stdlib/)