evalanche

Avalanche-first agent wallet infrastructure with multi-EVM execution, policy rails, and Polymarket-ready collateral flows.

Now shipping v1.9.7

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

GitHub Install from npm

evalanche-v1.9.7.ts

const { agent } = await Evalanche.boot({ network: "polygon" });

await agent.mcp().call("pm_approve", {});

const balances = await agent.mcp().call("pm_balances", {});

const topup = await agent.bridgeTokensDetailed({
  fromChain: "base",
  toChain: "polygon",
  fromToken: "USDC",
  toToken: "USDC",
  amount: "25",
});

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, Polymarket, Hyperliquid, dYdX, CoinGecko, and 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.9.7 matters

01 Hardened local MCP transport

HTTP MCP now requires an explicit bearer token, stays on loopback by default, enforces request timeouts, and rejects oversized request bodies before parsing.

02 Live Polymarket collateral truth

Venue balances now normalize live pUSD spender allowances, while pm_approve and pm_deposit keep wallet-side USDC.e and venue-side pUSD approvals in sync.

03 Policy-aware execution helpers

Approve-and-call, proxy upgrades, Li.Fi bridge/swap execution, and Gas.zip funding now route through the active spending policy before they can broadcast value.