⚫Blockchain
Testnet & Mainnet Blockchain Overview
This page gives a single, clean view of the AIRON blockchain: what it is, how it works at a high level, and what to expect for testnet and mainnet. It’s written for builders, partners, and community members who want clarity without digging through multiple pages.
At a glance
Network name: AIRON Smart Chain (ASC)
Layer: L1, EVM-compatible
Consensus: Proof of Authority (PoA)
Gas token: AIR
Block interval: short, fixed interval (target ~3s; subject to change after testing)
Quick sync: supported (snapshot / checkpoint)
Throughput: high TPS target for simple transfers (workload-dependent)
Standards: ERC-20, ERC-721, ERC-1155; meta-tx optional
Fee model: EIP-1559 style base fee + tip (proposed)
Final parameters are confirmed during public testnet and audits.
What makes AIRON different
Predictable operations through PoA and clear validator accountability.
Developer-first with full EVM compatibility and familiar tools.
Transparent governance: decisions, addresses, and reports are public.
Security as a habit: staged rollouts, audits, incident notes.
Networks
Devnet (internal)
Used for rapid iteration and load testing. Not public.
Public Testnet (coming)
A stable environment for developers and early partners.
What you’ll get:
Explorer & RPC: public endpoints and docs
Faucet: limited test tokens for developers
Status page: uptime and incident notes
Starter kits: token, NFT, and basic dApp templates
Reporting: monthly build log and release notes
Chain ID, RPC URLs, and explorer links will be published at testnet launch.
Mainnet (after audits)
Production network with governance and validator onboarding.
What you can expect:
Genesis docs and public addresses
Validator information (criteria, contact, regions)
Treasury transparency (multisig, reports)
Support & incident process with clear SLAs
Node roles
Validator: produces and signs blocks; operates behind sentry nodes.
Sentry: public-facing peers that protect validators and handle P2P traffic.
RPC: provides read/write access for wallets and apps.
Archive/Index: optional nodes for analytics and explorers.
Finality and performance
Deterministic finality at block commit (no probabilistic reorgs).
Short block interval for responsive UX.
Quick sync so new nodes can join without replaying the entire history. Actual throughput depends on workload mix, gas limits, and hardware.
Compatibility
Smart contracts: Solidity (and compatible toolchains).
Wallets: any EVM wallet (MetaMask, WalletConnect, etc.).
Bridges: canonical bridge planned; supported assets listed at launch.
Oracles & indexers: integrations announced as they go live.
Governance snapshot
Validator council stewards upgrades and membership.
Community participation grows toward an on-chain Governance DAO.
Records: proposals, decisions, and transactions logged publicly.
Security model (summary)
Identity-based validator accountability under PoA.
Audits before major releases; bug bounty at and after testnet.
Sentry architecture, rate limits on public RPC, incident reporting with timelines.
Upgrades through controlled, documented processes.
Release flow
Spec & devnet → internal testing, profiling, and fixes
Public testnet → explorer, faucet, docs, example apps
Audits → external reviews and remediation
Mainnet → genesis, validator onboarding, governance activation
Continuous improvement → quarterly transparency reports and versioned upgrades
What to prepare as a builder
Keep contracts standard (ERC-20/721/1155) and upgradable only if you need it.
Plan for testnet first, then migrate with verified source and metadata.
Use allowlisted tokens at the start; the list expands over time.
Follow the governance pages for proposal windows and addresses.
Last updated