ETH or native gas
Technical execution
Use the standard Orbit and Sepolia-compatible gas path. Keep L2 gas very low during Devnet v0.1 and subsidize tester usage where needed.
Fee policy
Atomic Chain Devnet Fee Policy
Atomic Chain Devnet v0.1 keeps chain gas low for testing. Devnet gas may be subsidized while the network is validated. DRK is used as the user-facing access and usage rail. wL6ETH is reserved for protected settlement and bridge-related flows after runtime stability is confirmed.
Current status
Devnet v0.1
Low gas, operator-subsidized, DRK usage rail, and wL6ETH settlement rail pending full bridge integration.
Recommended model
Three rails, three jobs
Product pricing, settlement value, and technical chain execution should not be collapsed into one token story during devnet.
DRK
Access and usage
Use DRK for visible access, credits, app usage, CAPPS-linked utility, and premium route logic. DRK should remain separate from technical gas for now.
wL6ETH
Protected settlement
Reserve wL6ETH for protected settlement, bridge, checkout, and Capsule-linked value flows after the runtime, RPC, and evidence surfaces are stable.
Operator costs
Infrastructure funding
Batch posting, parent-chain RPC, beacon RPC, Docker host costs, monitoring, and deployment costs are operator-funded devnet infrastructure costs.
Public wording
What Atomic Chain should say publicly right now
This wording keeps the system understandable, proof-safe, and consistent with the actual devnet runtime.
Gas
Native and low-cost
Atomic Chain Devnet v0.1 uses low-cost native gas for testing. Devnet gas may be subsidized while the network is being validated.
Infrastructure
Operator-funded
During devnet, parent-chain posting and infrastructure costs are operator-funded while reliability, RPC availability, and public evidence are validated.
Usage
DRK is visible utility
DRK is the visible usage and access rail. It should be described as user-facing utility, not as the gas token for Devnet v0.1.
Settlement
wL6ETH stays protected
wL6ETH is the protected settlement rail. It should be reserved for bridge and settlement-sensitive flows after runtime stability is confirmed.
Not yet
What not to promise during devnet
These items add risk, confusion, or regulatory ambiguity before the chain and bridge have the evidence to support them.
Avoid
Custom gas token
Do not make wL6ETH or DRK the gas token during Devnet v0.1. Keep the runtime simple and easier to verify.
Avoid
Complex fee markets
Do not add fee-token pricing logic, reimbursement loops, or speculative gas-market design until bridge and operator economics are proven.
Avoid
Staking or return language
Do not attach fee policy to staking economics, revenue share, or investment-style promises while the network is still in devnet validation.
Avoid
Mainnet-style pricing claims
Keep the wording narrow. Devnet pricing is for testing and validation, not a public long-term fee promise.