Chains & networks
Avalanche: C-Chain, other chains and bridge exposure
Similar branding can cover different execution environments and validator arrangements.
Les enquêtes et les fiches de référence sont publiées en anglais. La navigation est disponible en sept langues.
Personnes et projets
Dans cet article
Avalanche's primary network contains distinct chains with different roles. The C-Chain supports EVM smart contracts; other chains serve additional asset and platform functions. Avalanche L1 deployments can also have their own configurations. Use the exact network name and documentation.
What changes across deployments
Application execution, validator participation, native fees and asset routes may differ. A token on one deployment is not automatically usable on another. Bridging can add a new issuer or verification mechanism even where both ends belong to the same broad ecosystem.
For a financial application, trace who can change its contracts, which feeds determine prices and where withdrawals settle. Do not assume that a familiar wallet connection screen means the underlying asset is the one you intended to use.
A chain comparison should describe the trust assumptions of each deployment. Marketing terms such as institutional, enterprise or sovereign are not substitutes for that description.
Sources
Recherche vérifiée le 5 septembre 2026. Historical cases retain the date and legal status of the cited record.