Atomic AI Nexus
The public product surface.
Launch Readiness
Launch readiness.
Current state, missing trust items, and rollout order.
Core Terms
This page uses the same definitions as the main docs.
CAPPS
The access-control and route-policy system.
Capsule
The scoped verification session required before protected routes open.
Layer 6
The protected private core for sensitive services and vault logic.
AI Core
The private operational intelligence layer behind the public surface.
Launch Board
Public surfaces and rollout order in one map.
Current Technical State
What is already visible on the live stack.
Live domain and hardened headers
The public domain is live with strict security headers, route gating, origin checks, and Capsule-bound protected lanes.
Reserve and rail visibility
The homepage now exposes reserve totals, bridge-backed funding, payment counts, route status, and the DRK / wL6ETH rail split.
Protected route model
Marketplace, staking, games, trading, checkout, faucet, and Nexus are tied back into Capsule verification and CAPPS route policy.
Critical Before Full Public Push
These items still depend on operator action or external systems and should be treated as launch-gating work.
Verified contract source
The public launch standard should include verified source, compiler settings, constructor args, and public contract inspection on Etherscan.
Treasury multisig
The treasury and any meaningful operator-controlled funds should be moved under a multisig model before broad public trust is requested.
Liquidity lock and distribution proof
Public buyers will look for locked liquidity, visible LP terms, and a defensible distribution story instead of opaque concentration.
Registrar and DNS controls
Registrar lock, DNSSEC, hardened recovery, and hardware-backed 2FA should be treated as production prerequisites for the public brand domain.
Public trust signals
Contract verification, public docs, tokenomics, audit or review status, and transparent change control matter as much as the frontend itself.
Soft launch before mass launch
The practical recommendation remains a controlled beta first, then transaction stress testing, exploit review, UX cleanup, and only then broad public announcement.
Recommended Launch Sequence
Best public rollout order for Dark Coin.
Phase 1
Controlled beta with a small user group and real monitored usage.
Phase 2
Stress-test wallet flows, settlements, game lanes, and premium route activation.
Phase 3
Fix exploits, tighten abuse handling, and reduce approval or wallet confusion.
Phase 4
Public announcement only after trust, docs, economics, and operations line up together.
Public Positioning
The strongest public framing is not “just another token.”
Dark Coin reads most strongly as the public access token for competitive gaming, AI services, CAPPS verification, and Layer 6 services. That framing is stronger than a generic meme or empty utility token because it ties DRK to real access, route priority, credits, premium systems, and future validator-style participation.
Trust hubPublished proof routes
StatusRoute and API health
TokenomicsPublic utility and revenue loops