Sonic network
Aegis deploys on Sonic — an EVM layer-1 with sub-second finality and high throughput. Sonic is the settlement layer; Aegis composes privacy and DeFi modules on top.
Network information
| Field | Mainnet |
|---|---|
| Network name | Sonic |
| Chain ID | 146 |
| RPC URL | https://rpc.soniclabs.com |
| Explorer | sonicscan.org |
| Currency symbol | S |
Why Sonic
- Speed — confirmations in under a second for responsive DeFi UX.
- EVM compatibility — deploy existing Solidity patterns without retooling the entire stack.
- Fee monetization — Sonic’s fee model rewards applications that drive network usage (see Sonic docs).
Bridging to Sonic
Users typically enter via the Sonic Gateway from Ethereum. The main app’s Bridge module wraps the official gateway flow. After assets land on Sonic, shield, swap, and govern inside Aegis.
TIP
Always use the official gateway addresses from Sonic’s documentation — not third-party “fast bridge” sites linked in DMs.
Wallets
Any EVM wallet that supports custom networks (MetaMask, Rabby, etc.) can add Sonic with chain ID 146 and the RPC above. The app prompts network switch when needed.
Verified contracts
Canonical deployed addresses are published in signed GitHub releases. Verify on SonicScan before sending funds — especially for AGS and the Dutch auction, where copycat contracts are common before TGE.
WARNING
Do not trust token lists or “official AGS” contracts that did not come from our community channels.