Avalanche X-Chain

Overview

Avalanche X-Chain is a specialized blockchain on the Primary Network that runs the Avalanche Virtual Machine. It supports the creation and transfer of Avalanche Native Tokens and historically used a DAG-oriented transaction structure before later protocol changes linearized its ordering. X-Chain is not EVM-compatible, and its addresses, transaction formats, APIs, and asset model differ from C-Chain. The same AVAX asset can move between Avalanche chains through explicit cross-chain operations, but a transfer on one chain is not automatically visible on another. Wallets, exchanges, and custody systems must label X-Chain clearly and use compatible address validation and signing logic. Deposit processing should verify the destination chain, transaction acceptance, asset identifier, and any required cross-chain export or import step before crediting funds.

Payment support for Avalanche X-Chain needs explicit asset and network allowlists, receipt or execution checks, reorganization handling, and recovery procedures. Changes to governance, validators, sequencers, bridges, or client versions can alter risk without changing the public brand. This prevents later renames, forks, or infrastructure changes from making previous settlement decisions impossible to reproduce. Historical records involving Avalanche X-Chain should retain chain identifiers, block hashes, transaction data, and the configuration version used at acceptance time.

Avalanche X-Chain should be identified by its active mainnet, chain or network identifiers, native fee asset, address rules, and currently supported software. A project name, associated token, testnet, legacy deployment, and bridged representation are different objects and should not be used interchangeably. Public endpoints and explorers are useful operational tools but are not independent proof that a node is synchronized or a transaction is canonical. Integration with Avalanche X-Chain should use current official specifications for RPC methods, transaction formats, fees, finality, contract addresses, and upgrade schedules.