L2 development
Evidence level: Normative design. CoNET-DLE is a controlled specification set. This page tells a developer how to work against those documents. It is not a production SDK, a public tip RPC, or evidence that asset ingress is enabled.
Public site: https://gitbook.conet.network/developers/l2.html
CoNET L1 (chainId 224422) is live. DLE is not documented here as a launched production system. Digest pages under L2 — CoNET-DLE explain the design; they do not create requirements. Byte-level behavior is controlled by the public whitepaper and the three DLE-*Spec.md files.
Reviewed whitepaper revision: 2026-08-13.
What you can develop today
| Work | Status |
|---|---|
| Read and implement against the public specs | Allowed — cite filename + section |
| Run published archive vectors / JSON Schema / TLA configurations | Allowed inside their declared domain |
| Write a class-fixed tip state machine from the whitepaper | Design / prototype — not a production deployment |
Call a public DLE tip API or production AssetBurnMintGateway |
Not available in this book |
| Treat a Treasury mint as L2 activation | Incorrect — two separate machines |
| Sign production archive certificates | Forbidden until the Archive spec’s production blockers close |
Public repository: CoNET-project/CoNET-DLE.
Controlling sources (read these first)
| Boundary | File | Declared status |
|---|---|---|
| Architecture and frozen product decisions | Decentralization Cluster multi-chain.md | Whitepaper; paired zh-CN |
| Archive bytes, voting, WAL, membership | DLE-Archive-Tendermint-Conformance-Spec.md | Normative draft; production closure incomplete |
| Asset burn, backing, refund, exit | DLE-AssetBurnMintGateway-Invariant-Spec.md | Normative v1 safety specification |
| Operator identity / correlated failure | DLE-OperatorDomainRegistryV1-Spec.md | Normative v1 identity specification |
Precedence when texts disagree: named spec for its boundary → whitepaper → executable vectors for their test domain → GitBook digest. Do not cite Canvas notes as a MUST. Full map: Normative sources.
Protocol shape (for implementers)
The target design has five parts:
- Parallel tips — each ledger advances independently; no event means no block.
- L1 birth certificate — a tip binds to a unique CoNET L1 NFT and exactly one class: asset, storage, or trade.
- Validator production — a per-tip committee proposes event blocks (current design: seven selected validators, five-signature threshold). This is not the CoNET L1 validator set.
- Archive finality — the hosting archive group replays the candidate and finalizes with Tendermint-style prevote / precommit certificates.
- Separated economics — protocol value fees, execution reserves, and availability budgets are different ledgers.
Class is immutable. A tip cannot host arbitrary bytecode or become a general-purpose VM. Digest: ledger classes, archive plane, economics.
ERC-20 path into DLE (not live)
A foreign ERC-20 must already be a Treasury-canonical CoNET L1 token. See Bring an ERC-20 into CoNET. DLE never burns a foreign-chain contract directly.
Treasury-canonical ERC-20 on CoNET L1
│ exact proxy + version
│ AssetAdmissionRegistry = ACTIVE
│ approved pool + frozen TWAP adapter
▼
BURNED_PENDING → ACTIVATED (or REFUNDED if genesis misses the deadline)
│
▼
asset-class tip (claim against burned units, not a wrapped L1 transfer)
Even conet-USDC must pass those gates in the design. Production asset ingress and new-chain admission remain disabled pending measured economic evidence. Digest: Cross-chain assets in DLE.
Suggested implementation order
- Clone CoNET-DLE and pin the whitepaper revision you implement.
- Pick one boundary: Archive conformance, Asset gateway invariants, or Operator-domain identity. Do not mix requirements across files without citing both.
- Implement against the spec’s frozen vectors / schemas. Record the revision in your artifact.
- Keep L0 coordination (wallet-addressed envelopes) and L1 settlement (Treasury, CNET gas) as external dependencies. DLE does not replace Layer Minus or CoNET L1.
- Stop at the documented production blockers: second independent Archive implementation, wrapper / networking / custody gates, and formal-verification release items in the Asset spec.
What not to claim
- Do not describe GitBook pages as the wire encoding.
- Do not treat Explorer-verified Treasury bytecode as an
AssetBurnMintGateway. - Do not use L1 validator counts as a DLE committee census.
- Do not invent a
dle.*hostname. Use existing CoNET / GitHub paths. - Do not present a successful L1 bridge as “the asset is on L2.”