Integration

High-level guide for builders connecting to Aegis on Sonic.

Chain

Field	Mainnet
Chain ID	146
RPC	https://rpc.soniclabs.com
Explorer	https://sonicscan.org

Reading state

• Use your own Sonic RPC or a provider you trust — do not rely on a single centralized read path for high-value flows.
• Contract ABIs and address manifests ship in signed releases.

Writing transactions

• Users sign in their wallet; relayers only submit intents users authorized via EIP-712.
• New modules must be authorized on the shielded token before consuming commitments.

Environment configuration

Production frontends load addresses from build-time env vars generated against a canonical deployment. Operators regenerate env from the contracts repo after deployments — exact commands are in the integration kit, not duplicated here.

TIP

Never commit .env files. Cloudflare Pages injects VITE_* at build time for app and TGE projects.

Chain pack

The app bundles a sonic chain pack JSON — bridge tokens, gateway addresses, quoter hints. It rebuilds with each signed release.

Next steps

Read Partners and request the integration kit if you are shipping a product on Aegis.