L2 — CoNET-DLE

Evidence level: mixed. The network identifiers and public services below describe the live DLE lab explorer and the deployed CoNET L1 routing facade. The rest of this section is a normative design digest. 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.

Network facts

0x44c45 is the CoNET-DLE Testnet EIP-155 chain id. It distinguishes this plane from CoNET L1 224422 and Base 8453. It is not Group ID. Do not add it to a wallet as if it were CoNET L1. https://dle.conet.network is the authorized explorer host; do not invent additional dle.* names, and do not write that hostname into Solidity.

The routing registry lives on CoNET L1. Bootstrap storage key groupId = 1 holds seven distinct participant wallets. The user-visible Group ID is that group’s register tx hash. That is routing identity, not Archive Certificate and not 30-day qualification. See Global Archive Routing Registry and DLE explorer.

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-09-23. Lab M6 fission is a laboratory gather (liveGroupCount: 2); hosts emit the G2 L1 registerLiveGroup tx as the second Group ID. The repository honesty track (P12–P22) is engine + tests. P23 keep-deploy evidence is landed as 6/7 LIVE_OK plus fd-01 new-chain 409→accept; later fd-06 remap / inventory freeze / clock start are not P26. P24 wires isolated node.ts to the same official-standby gate. P25 lands Explorer non-green overlays. Home / archive-detail seating copy is lab EIP-712, never HMAC. The 30-day wall clock elapsed on 2026-09-17T09:53:58.092Z. A read-only post-window scrape on 2026-09-23T15:16:45.701Z found formal seating QUALIFIED 7/7 but pilotQualified=false 7/7 and heartbeat quorum only 3/7. It also exposed roster / readiness boundary drift: formal nodes reported 9–10 roster entries and an “official” standby-ready count of four although the frozen official baseline is two. The freeze blocks new hash-catalogue writes; it is not a roster freeze. Final result: partial success, not qualified. Do not unfreeze, promote, enable production signing, claim production readiness, or invent P26. Review: Lab honesty track.

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 six 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. EIP-155 Chain ID vs Group ID. The plane’s unique EIP-155 id (testnet 0x44c45) is what wallets and eth_chainId use. User-visible Group ID is that group’s L1 register tx hash. L1 archiveGroupId[tokenId] remains a uint storage key (bootstrap 1). None of these is CoNET L1 224422 or the tip NFT id (whitepaper §5.2.0d).
4. Validator production. A per-tip committee proposes event blocks; the current design uses seven selected validators and a five-signature threshold. Archives do not produce blocks.
5. Archive finality. The hosting archive group replays the candidate, checks data availability, and finalizes it through Tendermint-style prevote and precommit certificates. Clients route history from the L1 Global Archive Routing Registry, not from gossip or explorer hostnames.
6. 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. Global Archive Routing Registry — deployed L1 facade and seven participant wallets
4. Ledger classes — asset, storage, and trade state machines
5. Cross-chain assets in DLE — Treasury hand-off, admission, burn/activation, and conservation
6. Economics — the three-ledger funding model
7. DLE explorer — public lab UI at https://dle.conet.network/
8. Lab honesty track — 2026-08-18 MVP review through the 2026-09-23 post-window assessment; P12–P24 engine; P23 keep-deploy 6/7 + 409→accept; P25 Explorer overlays; clock elapsed but qualification failed; roster / standby-count boundary drift recorded
9. Normative sources — controlling documents, evidence, and non-normative material

Developer how-to: L2 development.

Source anchors

• Public repository: CoNET-project/CoNET-DLE
• Whitepaper: Decentralization Cluster multi-chain.md, Abstract; §§3–6 including §5.2.0d; §13
• Archive conformance: DLE-Archive-Tendermint-Conformance-Spec.md
• Asset conservation: DLE-AssetBurnMintGateway-Invariant-Spec.md
• Operator correlation: DLE-OperatorDomainRegistryV1-Spec.md

Next

Design thesis →

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