Multi-Chain Architecture

Circular is designed to support multiple chains operating in parallel on a shared node set. Conceptually, this allows capacity to grow as participating resources grow, with realized throughput depending on implementation details, network conditions, and the distribution and capability of nodes.

Nodes may participate in validation and block production for one or more chains, subject to protocol rules and any chain-specific parameters. This enables different chains to coexist with distinct settings and policies, including settings that may be appropriate for public deployments or for permissioned deployments in regulated contexts.

Efficient Resource Utilization

A core design objective is to reduce idle time in node operation by allowing nodes to perform useful work across multiple chains rather than waiting on a single global block schedule. This is intended to improve overall resource utilization compared to single-chain designs, while preserving verifiability and auditability of on-chain actions.

Public and Permissioned Deployments

Chains may be operated with different participation models. Some chains may be open-participation, while others may be permissioned based on compliance or operational requirements. Where chains are permissioned, participation and policy enforcement are governed by the relevant chain rules and associated governance processes.

Cross-Chain Transactions

Cross-chain interactions are supported in cases where chains share compatible rules and where the participating nodes are able to validate the relevant state transitions. Practical support for cross-chain transactions depends on which subnets or node groups can observe and process the required data for both chains.

Block Production

Block production follows the consensus rules of each chain. Parameters that affect block cadence and confirmation behavior are defined by protocol and chain-level configuration. Any example timings referenced are targets and may vary across deployments and over time.