Overview

Figment’s Avalanche API

Figment’s Avalanche API provides endpoints to interact with the C-Chain and P-Chain.

C-Chain

The Avalanche C-Chain (Contract Chain) is an EVM-compatible blockchain that runs as part of Avalanche’s Primary Network. Avalanche’s consensus protocol powers it but uses the Ethereum Virtual Machine (EVM), allowing it to run all Solidity smart contracts like Ethereum.

• EVM Compatibility: The C-Chain runs a fork of go-ethereum called coreth, making it compatible with existing Ethereum tools, wallets, and smart contracts.
• Low Fees and Fast Finality: Thanks to Avalanche’s consensus, C-Chain offers much lower transaction costs and near-instant finality.

P-Chain

The Avalanche P-Chain (Platform Chain) is a core component of Avalanche’s Primary Network, responsible for managing validators, staking, and the creation of new blockchains (Avalanche L1s and Subnets).

• Validator Management: The P-Chain handles all validator and staking operations for the Avalanche network. A node must stake at least 2,000 AVAX on the P-Chain to become a validator.
• Subnet and Blockchain Creation: The P-Chain enables the creation and management of new blockchains (Avalanche L1s) and Subnets, allowing developers to launch custom blockchains with their own rules and tokens.
• BLS Public Key Registry: Validators can register their BLS public keys on the P-Chain, which are used for secure cross-chain communication and signature verification.

X-Chain

The Avalanche X-Chain (Exchange Chain) is a core blockchain in Avalanche’s Primary Network, designed specifically for the creation, transfer, and management of Avalanche Native Tokens and digital assets.

• Asset Creation and Transfer: The X-Chain is optimized for operations involving digital smart assets, known as Avalanche Native Tokens. These can represent real-world resources (like equity or bonds) and can have custom rules (e.g., transfer restrictions).
• High Throughput: The X-Chain leverages Avalanche’s consensus protocol to enable high transaction throughput and low latency for asset transfers.

Endpoints

Export

Move AVAX from the C-Chain into Avalanche’s atomic memory pool.

• export endpoint

Import

Claim AVAX on the P-Chain from the memory pool (after an export).

• import endpoint

Delegate

Stake AVAX on the P-Chain by delegating to a validator.

• delegate endpoint

Self bond

• self-bond endpoint

Broadcast

Submit any signed Avalanche transaction (C, P, or X chain) to the network.

• broadcast endpoint

Allowed networks

• Mainnet
• Fuji

Derive path address of Fireblocks

Derive Addresses: Fetch the ECDSA public key from your vault via BIP44 path and convert it to C‑Chain, P‑Chain, and X‑Chain addresses.