Avalanche C-Chain, P-Chain, and Subnets covered together
AVAX moves between three chain types — C-Chain (EVM), P-Chain (staking), X-Chain (transfers) — and Wag3s reconciles the cross-chain flow correctly.
Avalanche's tri-chain architecture means a single AVAX can live on any of three chains, each with its own accounting profile. C-Chain is EVM-compatible — same flows as Ethereum. P-Chain is where validators and delegators stake; staking rewards land here, not on C-Chain. X-Chain is for asset transfers (legacy use). Most operating teams interact mostly with C-Chain, but treasuries running validators or delegating need P-Chain accounting too. Subnets — application-specific chains using their own validator sets — add a third surface; we cover the major ones (DeFi Kingdoms, Dexalot, Beam) and add new ones on request.
What's tracked on Avalanche
C-Chain EVM activity
AVAX, ERC-20, NFTs, Trader Joe / Pangolin / Benqi DeFi positions.
P-Chain staking
Delegation, validator rewards, undelegation timing (typically 14 days).
Cross-chain transfers
C-Chain ↔ P-Chain ↔ X-Chain reconciled with the right intermediate state.
Subnet activity
DFK Chain, Dexalot, Beam — Subnet-specific transactions decoded against the Subnet's tooling.
GMX V2 on Avalanche
Same depth as GMX on Arbitrum — open / close / GLP / GM positions.
Avalanche accounting questions
How does Wag3s handle the C-Chain ↔ P-Chain transfer?
As an intra-asset transfer (no realized gain), with the right balance debit / credit on each chain. The transfer takes a few minutes; we surface the in-flight state.
Are P-Chain delegation rewards taxable on accrual or on receipt?
We book them as ordinary income on receipt (the delegation reward distribution event). For accrual-basis taxpayers, we can also surface the accrued-but-unreceived amount per period.
Other chain coverage and tax guides relevant to this network.
Book Avalanche the right way
Free during Alpha. Connect a wallet, see every transaction reconciled to journal entries.