Dual-Chain Model

Whitepaper

Dual-Chain Model

Every Cerulea deployment is one of two sovereign architectures, Public L1 or Cerulea Private. This selection, made at project creation in Studio, determines all subsequent decisions about governance, infrastructure ownership, compliance posture, and validator control. Both architectures are complete, standalone blockchain environments accessed through the same interface.

The Dual-Chain Model

One Interface · Two Architectures · Complete Sovereignty

Cerulea StudioSingle Interface · No-Code Configuration
Public L1
Consensus
DCF · Fixed Policy Set · Approved Registry
Governance
Token-weighted community voting
Data Visibility
Public via Cerulea Explorer
Target Use Case
dApps · Public Registries · Token Systems
Runtime
Full EVM Compatibility · WASM · Solidity
Cerulea Private
Consensus
DCF · Fully Configurable · Enterprise Rules
Governance
Authority-based · Multi-signature approval
Data Sovereignty
Enterprise-exclusive · Zero vendor access
Target Use Case
Regulated Industries · Government · Private Data
Infrastructure
AWS · GCP · Azure · On-Premise · Hybrid

Both chains connect optionally through the Cross-Chain Bridge Engine

Public L1

The Public L1 operates as Cerulea's open, permissionless blockchain network. Validators are admitted through the DCF policy registry. Governance is token-weighted and community-driven. All chain activity is publicly visible through Cerulea Explorer. The Public L1 is appropriate for dApps, token systems, public registries, and open ecosystem services.

Cerulea Private

Cerulea Private deployments are sovereign enterprise blockchain environments. The deploying organisation owns the validator infrastructure, holds governance authority, and has exclusive access to all chain state. Zero vendor access exists, Cerulea cannot read transaction payloads or smart contract state. This architecture is appropriate for regulated industries, government use cases, supply chain systems, and any environment where data sovereignty and compliance authority are non-negotiable.

Optional Bridge Connectivity

Both chain types can optionally connect through the Cross-Chain Bridge Engine. This enables selective asset transfers and message passing between Public L1 and Private Chain environments without compromising the sovereignty of either. Bridge connectivity must be explicitly configured, it is never assumed or applied by default.

DimensionPublic L1Cerulea Private
ParticipationOpen, permissionlessPermissioned, enterprise-controlled
GovernanceToken-weighted, community-drivenAuthority-based, organisation-defined
ValidatorsDCF registry, open onboardingEnterprise-selected, organisation-owned
InfrastructureDistributed network participantsCloud, on-prem, or hybrid (org-owned)
Data visibilityPublic via Cerulea ExplorerEnterprise-exclusive, zero vendor access
ComplianceNetwork-level rules onlyCustom enforcement modules, full control
Use casesdApps, tokens, ecosystem servicesEnterprise blockchain, regulated industries