Evalanche

Avalanche-first agent wallet and execution SDK for AI agents, with multi-EVM support for holdings, payments, DeFi, bridge flows, prediction markets, and perpetuals.

Current Release

• Latest release: v1.9.0
• Published package: evalanche@1.9.0
• Current package surface:
  • Implemented pm_withdraw, so Evalanche can now withdraw Polygon USDC.e from the Polymarket wallet through the official Polymarket bridge flow
  • pm_withdraw gets a bridge quote, creates withdrawal addresses, submits the onchain USDC.e transfer, and returns the initial bridge-status snapshot for verification
  • MCP now exposes pm_withdraw alongside the existing Polymarket trading, reconciliation, deposit, and redemption flows
  • Added focused client and MCP regression coverage for the new Polymarket withdrawal path
• Docs:
  • Release notes
  • Roadmap
  • Release process
  • Security

Install

npm install evalanche

Quick Start

import { Evalanche } from 'evalanche';

const { agent } = await Evalanche.boot({ network: 'avalanche' });

console.log(agent.address);

const holdings = await agent.holdings().scan();
console.log(holdings.summary);

MCP

npx evalanche-mcp

Evalanche ships an MCP server for wallet actions, holdings discovery, DeFi, bridge and swap flows, Polymarket, and perpetual venues.

What It Does

• Avalanche-first wallet boot, identity, and agent execution flows
• Unified holdings discovery across wallet balances, DeFi positions, prediction positions, and perp venues
• Cross-chain bridge, swap, and gas-funding flows
• Avalanche and multi-EVM DeFi actions
• Polymarket market reads and execution
• Perpetual trading support for Hyperliquid and dYdX

Also Works Across EVM

Avalanche is the primary path, but Evalanche also supports Base, Ethereum, Arbitrum, Optimism, Polygon, BSC, and other EVM networks for execution and holdings discovery.

Docs

• Roadmap
• Release notes
• Release process
• Website source
• Smoke checklist
• Protocol notes
• Security
• Open gaps
• Security posture

Website

The public site for evalanche.xyz lives in website/. It is deployed separately from the npm package and is not included in the published package tarball. Git-based Vercel deploys use vercel.json plus build-website.mjs to publish only the website assets, not the SDK build.

License

MIT