Supported Chains

Octav supports over 65 blockchain networks with varying levels of integration. Each chain has different capabilities for portfolio tracking and transaction indexing.

Growing Network - We regularly add support for new chains. Check this page for the latest updates.

Support Levels

Portfolio Support

Portfolio Support means the chain is integrated with our portfolio tracking system.

Real-time balance tracking
Token holdings across protocols
DeFi position tracking
Net worth calculations
Multi-chain aggregation

Available on: /v1/portfolio, /v1/wallet, /v1/airdrop

Transaction Support

Transaction Support means the chain provides full transaction history indexing.

Complete transaction history
Transaction categorization
Fee tracking
Search and filtering
Advanced analytics

Available on: /v1/transactions

All Chains
By Ecosystem
Quick Reference

Full Support (Portfolio + Transactions)

These chains support both portfolio tracking and transaction history:

Chain	Key	Chain ID
Arbitrum	`arbitrum`	42161
Avalanche	`avalanche`	43114
Base	`base`	8453
Binance	`binance`	56
Blast	`blast`	81457
Ethereum	`ethereum`	1
Fraxtal	`fraxtal`	252
Gnosis	`gnosis`	100
Linea	`linea`	59144
Optimism	`optimism`	10
Plasma Testnet	`plasmatestnet`	-
Polygon	`polygon`	137
Solana	`solana`	-
Sonic	`sonic`	146
Starknet	`starknet`	-
Unichain	`unichain`	-

These chains offer the most comprehensive data coverage for building full-featured applications.

Portfolio Only

These chains support portfolio tracking but not full transaction history:

Chain	Key
Abstract	`abstract`
Arbitrum Nova	`arbitrum_nova`
Berachain	`berachain`
BOB	`bob`
Boba	`boba`
BounceBit	`bouncebit`
Celo	`celo`
Core	`core`
Corn	`corn`
Cronos	`cronos`
Etherlink	`ethlink`
Everclear	`everclear`
Fantom	`fantom`
Flare	`flare`
Fuse	`fuse`
HashKey	`hsk`
Hemi	`hemi`
HyperEVM	`hyperevm`
Hyperliquid	`hyperliquid`
Ink	`ink`
IoTeX	`iotex`
Katana	`katana`
Kava	`kava`
Manta	`manta`
Mantle	`mantle`
Merlin	`merlin`
Metis	`metis`
Mint	`mint`
Mode	`mode`
Morph	`morph`
Plasma	`plasma`
Plume	`plume`
Polygon zkEVM	`polygon_zkevm`
Rari	`rari`
Rootstock	`rsk`
Scroll	`scroll`
Shibarium	`shib`
Soneium	`soneium`
Sophon	`sophon`
SwellChain	`swellchain`
Taiko	`taiko`
Telos	`telos`
World Chain	`wc`
X Layer	`xlayer`
zkSync Era	`era`
Zora	`zora`

Using Chain Keys

Chain keys are used throughout the Octav API to filter and identify blockchain networks:

// Get only Ethereum transactions
const response = await fetch(
  `https://api.octav.fi/v1/transactions?addresses=${address}&networks=ethereum`,
  {
    headers: { 'Authorization': `Bearer ${apiKey}` }
  }
);

Chain Data Structure

When querying the API, chain data is returned in this format:

{
  "chains": {
    "ethereum": {
      "name": "Ethereum",
      "key": "ethereum",
      "chainId": "1",
      "value": "5432.10",
      "valuePercentile": "65.3",
      "imgSmall": "https://images.octav.fi/chains/ethereum_icon.svg",
      "imgLarge": "https://images.octav.fi/chains/ethereum_icon.svg",
      "color": "#627EEA"
    }
  }
}

name

string

Human-readable chain name

key

string

Unique identifier for API queries

chainId

string

Numeric chain ID (EVM chains)

value

string

Total USD value on this chain

valuePercentile

string

Percentage of total portfolio

Best Practices

Check Support Before Querying

Always verify the chain supports your required endpoint:

const SUPPORTED_CHAINS = {
  portfolio: ['ethereum', 'arbitrum', 'base', /* ... */],
  transactions: ['ethereum', 'arbitrum', 'base', /* ... */]
};

function isChainSupported(chainKey, endpoint) {
  return SUPPORTED_CHAINS[endpoint].includes(chainKey);
}

if (isChainSupported('ethereum', 'transactions')) {
  // Query transactions
}

Use Chain Filters

Filter API responses to specific chains for better performance:

// Instead of fetching all chains and filtering client-side
const allPortfolio = await fetch(
  `https://api.octav.fi/v1/portfolio?addresses=${address}`
);

// Prefer using network filters when available
const ethOnly = await fetch(
  `https://api.octav.fi/v1/transactions?addresses=${address}&networks=ethereum`
);

Handle Missing Chains

Not all addresses will have holdings on all chains:

const [portfolio] = await response.json();

// Safely check for chain
const arbitrumData = portfolio.chains?.arbitrum;

if (arbitrumData) {
  console.log(`Arbitrum value: $${arbitrumData.value}`);
} else {
  console.log('No Arbitrum holdings');
}

Frequently Asked Questions

Why doesn't a chain support transactions?

Transaction support requires deep integration with chain-specific indexers and explorers. We prioritize chains based on:

User demand
Chain activity and TVL
Technical feasibility
Data source availability

Portfolio support is faster to implement and covers the most common use case (checking balances).

How often are new chains added?

We add new chains regularly based on ecosystem growth and user requests. Major chains typically get portfolio support within weeks of mainnet launch.To request a chain, contact us via Discord.

Can I get testnet data?

Currently only Plasma Testnet is supported. We generally focus on mainnet data for production applications.

What's the difference between 'key' and 'chainId'?

key: Octav’s internal identifier (e.g., ethereum, arbitrum)
chainId: Standard EVM chain ID (e.g., 1 for Ethereum, 42161 for Arbitrum)

Use key for Octav API queries. ChainId is provided for reference.

Portfolio Endpoint

Query holdings across all chains

Transactions Endpoint

Filter transactions by chain

Supported Protocols

View all supported DeFi protocols

Request Support

Request a new chain on Discord

Getting Started

Endpoints

Playground

AI Development

Reference

Supported Chains

Support Levels