L2 — CoNET-DLE

Evidence level: Normative design digest. This section explains a controlled specification set; it is not evidence that the complete L2 system is deployed.

CoNET Distributed Ledger Expansion (CoNET-DLE) is a specified Layer-2-style architecture for many parallel, event-driven ledgers. Each ledger is a class-fixed state machine rather than a general-purpose VM.

This GitBook section is an explanatory digest. It does not create protocol requirements. Normative language and byte-level behavior are controlled by the English whitepaper and the three DLE-*Spec.md files listed in Normative sources.

Status boundary

CoNET L1 is a live network. DLE is not documented here as a fully launched production system.

This digest was checked against the whitepaper revision dated 2026-08-13.

The source set includes frozen product decisions, executable vectors, a bounded formal-model result, and TypeScript archive reference work. It also records unresolved production gates. In particular:

  • production asset ingress and new-chain admission remain disabled pending measured economic evidence;
  • the archive conformance specification forbids production signing until its interoperability, wrapper, networking, and custody blockers close; and
  • the DLE AssetBurnMintGateway is a target protocol component, not an alias for an already deployed Treasury contract.

“Frozen” therefore means the referenced design or serialization rule is fixed for its stated version. It does not mean the complete protocol has been deployed or independently verified in production.

For an ERC-20 issued on another chain, the target path has two separate state machines. An approved Treasury route first establishes the canonical CoNET L1 representation. A later DLE admission plus burn/activation protocol would establish L2 backing. A bridge transaction alone does not activate DLE.

Protocol digest

The target design has five main parts:

  1. Parallel tips. Each DLE chain advances independently. No event means no block.
  2. L1 birth certificate. A chain is bound to a unique CoNET L1 NFT and exactly one class: asset, storage, or trade.
  3. Validator production. A per-tip committee proposes event blocks; the current design uses seven selected validators and a five-signature threshold.
  4. Archive finality. The hosting archive group replays the candidate, checks data availability, and finalizes it through Tendermint-style prevote and precommit certificates.
  5. Separated economics. Protocol value fees, execution reserves, and availability budgets are different ledgers with different liabilities.

Scope of these pages

  1. Design thesis — why the design uses parallel class-fixed tips
  2. Archive availability and finality — validator production versus archive certification
  3. Ledger classes — asset, storage, and trade state machines
  4. Cross-chain assets in DLE — Treasury hand-off, admission, burn/activation, and conservation
  5. Economics — the three-ledger funding model
  6. Normative sources — controlling documents, evidence, and non-normative material

Developer how-to: L2 development.

Source anchors

Next

Design thesis →

Related: Decentralized cross-chain Treasury and Cross-chain assets in DLE.

results matching ""

    No results matching ""