Ethereum Mainnet
Root authority
- Canonical DRK and wL6ETH references
- Bridge escrow and root contracts
- Final settlement and proof anchor
- Emergency authority and treasury disclosures
Atomic AI Nexus roadmap concept
Atomic Chain
A proposed application-specific chain for Atomic AI Nexus. Public evidence stays visible. Sensitive writes stay controlled. Ethereum mainnet remains the settlement and proof anchor.
Mode
Hybrid appchain
Public layer
Evidence and verification
Controlled layer
CAPPS and Capsule checks
Positioning
Separate infrastructure inside the public trust surface
Atomic AI Nexus remains the application and trust platform. Atomic Chain is the proposed infrastructure layer beside it. This route documents the chain concept inside the public trust surface without treating it as live mainnet infrastructure.
Architecture
Three layers, one trust boundary
Mainnet stays canonical. Atomic Chain handles faster app activity. The public site publishes evidence instead of asking for trust by assertion.
Atomic Chain
App execution
- AI route activity and access records
- CAPPS-gated sensitive writes
- Capsule-gated value movement
- Marketplace, checkout, and proof-drop events
atomic-a-i.cloud
Public evidence surface
- Route status and evidence registry
- Risk notices and onboarding
- Bridge visibility and status exports
- Public verification links
Request enters
User or operator initiates an action on the app layer.
CAPPS checks
Route policy decides whether the write is allowed.
Capsule checks
Value-sensitive or identity-sensitive actions get extra verification.
Chain record
Atomic Chain records the event for lower-cost execution and auditability.
Mainnet anchor
Important evidence is anchored back to Ethereum.
Open site
Public user lands on the trust surface.
Inspect evidence
Route status, notices, and proof indexes stay visible.
Verify anchor
Higher-trust records point back to Ethereum-rooted proofs.
Bridge model
Canonical on mainnet, mirrored on Atomic Chain
The chain-side assets are execution forms, not replacements for the mainnet originals.
DRK
Public access rail
DRK remains the visible access and participation rail. On Atomic Chain it appears as a mirrored representation used inside approved workflows and proof surfaces.
wL6ETH
Protected settlement rail
wL6ETH remains the protected settlement reference. On Atomic Chain it supports controlled checkout and settlement-related actions without being framed as unrestricted native ETH.
Canonical asset enters a bridge-controlled root path.
Authorized proof or relay logic confirms the lock event.
Atomic Chain releases the mapped execution asset.
Reverse flow burns the mirrored form before release.
Launch decision
DRK should bridge first, not power gas first.
The fastest credible value path is to make DRK the required Atomic access and utility rail while keeping gas complexity and settlement-sensitive flows out of the first launch.
Chosen role
DRK as bridged utility
Use bridged DRK for CAPPS tiers, AI Core access, proof drops, premium routes, and fee-credit logic.
Settlement
wL6ETH stays protected
Keep wL6ETH in the checkout and settlement lane so DRK can create utility demand without carrying the entire settlement model.
Deferred
DRK as gas later
Custom-gas rollout is deferred until the bridge, batch poster economics, and fee-token pricer model are proven and reviewed.
Fastest value path
Utility before gas
Require DRK where users actually want access. That builds demand faster and with less production risk than a premature gas-token launch.
Integrated builder pack
DRK is now wired into the Atomic Chain module.
The DRK builder pack is staged as part of the Atomic Chain program so access, CAPPS, Capsule, AI Core, credits, bundles, and public artifacts can be reviewed beside the chain architecture instead of floating as a separate unlinked pack.
Public route
DRK module microsite
Open the integrated DRK access-layer page inside the Atomic Chain surface.
Docs
Integration notes
The docs hub now carries the DRK module as part of the Atomic Chain program boundary.
Code
Imported module
The source pack is staged under atomic-chain/drk-module/ so it can be reconciled with the chain core deliberately.
Proof-safe rule
Integrated, not declared live
The DRK module remains build material until live addresses, route status, and public evidence records are published.
Stack decision
Orbit first, OP Stack close behind
The current recommendation favors Arbitrum Orbit for configurable appchain rules, with OP Stack as the cleaner fallback if a more standard L2 posture becomes more important.
Primary
Arbitrum Orbit
Best fit for hybrid controls, app-specific policy, and Ethereum-rooted settlement.
Secondary
OP Stack
Best fit for the cleanest Ethereum L2 framing and a simpler public narrative.
Reserve
Polygon CDK
Useful if private or semi-private deployment modes become central.
Reserve
Cosmos SDK
Useful only if sovereignty outweighs Ethereum-native L2 alignment.
Documentation
Browse the full chain program
The microsite is the public front door. The docs set carries the technical narrative, separation rules, bridge assumptions, and testnet gates in more detail.
Docs index
Open documentation hub
Browse all Atomic Chain docs in one place.
Core
Architecture
Layer model, trust boundary, and execution flow.
Core
Bridge design
Canonical versus mirrored asset rules for DRK and wL6ETH.
Integrated pack
DRK module route
Review the integrated DRK builder-pack surface inside Atomic Chain.
Delivery
Testnet plan
Mainnet claims stay blocked until public artifacts exist.
Current status
Roadmap concept until public artifacts exist
Atomic Chain is a proposed application-specific blockchain layer. It should be treated as a roadmap concept until testnet, bridge contracts, validator or sequencer design, audits, and public evidence are published.
Arbitrum Orbit.
Architecture concept and microsite draft, not live mainnet infrastructure yet.
Avoid implying production readiness, decentralization, or unrestricted redemption before the evidence exists.