evalanche

Avalanche-first agent wallet infrastructure with multi-EVM execution, Avalanche L1 support, and policy rails.

Now shipping v1.14.0

ERC-8004 x402 Headless wallets Avalanche L1s Holdings Polymarket Hyperliquid LI.Fi Multi-EVM Policy-guarded

GitHub Install from npm

evalanche-v1.14.0.ts

import { Evalanche, listAvalancheL1s, getAvalancheL1Network } from "evalanche";

// Live mainnet or Fuji EVM L1 catalog
const l1s = await listAvalancheL1s();

// Checks the RPC's eth_chainId before use
const network = await getAvalancheL1Network(4337); // Beam

const agent = new Evalanche({
  privateKey: process.env.AGENT_PRIVATE_KEY,
  network,
});

console.log(agent.getChainInfo()); // BEAM, not AVAX

What Evalanche is now

Wallet stack

Agent-native execution layer

Reusable wallet and execution surface across Avalanche and the broader EVM stack without browser popups or custodial dependencies.

Identity

ERC-8004 native

Identity resolution, service endpoints, and trust-oriented agent workflows are built in instead of bolted on later.

Markets

More than wallet plumbing

Holdings, DeFi, Hyperliquid perpetuals, Polymarket, CoinGecko, Avalanche L1s, Robinhood Chain, and LI.FI cross-chain execution live behind the same agent-facing surface.

Infrastructure

Built broader than one app

Evalanche is open-source infrastructure that powers Eva Protocol and any other agent product that needs serious wallet and execution primitives.

Why v1.14.0 matters

01 Official Avalanche SDK by default

Native X/P/C operations now run on the official @avalanche-sdk/client. The legacy Core wallet and vulnerable HPKE dependency trees are gone from fresh installs, and clean consumer audits report zero production vulnerabilities.

02 Avalanche L1 discovery

Live mainnet and Fuji L1 catalog lookup, RPC chain ID verification, and native-token preservation, exposed as public SDK and MCP helpers. L1 wallets are EVM-only.

03 Leaner, hardened runtime

dYdX support is removed (Hyperliquid remains for perpetuals). X/P/C routing, offline signing, network switching and HTTP limits are hardened. Requires Node.js 20 or newer.