Avalanche-first agent wallet and execution SDK for AI agents, with multi-EVM support for holdings, payments, DeFi, bridge flows, prediction markets, and perpetuals.
- Latest release: v1.9.7
- Published package:
evalanche@1.9.7 - Current package surface:
- Hardened MCP HTTP mode so it now requires an explicit bearer token, binds to loopback by default, enforces request timeouts, and rejects oversized request bodies before parsing.
- Routed high-risk execution helpers through active spending-policy checks, including approve-and-call, UUPS proxy upgrades, Li.Fi bridge/swap execution, and Gas.zip funding.
- Tightened x402 paid-service hosting so settled endpoints require a settlement verifier by default, while preserving explicit
signed-intentmode for trusted peer flows and tests. - Fixed Polymarket collateral normalization for live pUSD spender allowances, and made
pm_approve/pm_depositsync both wallet USDC.e -> CLOB approval and Polygon pUSD spender approvals.
- Docs:
npm install evalancheimport { Evalanche } from 'evalanche';
const { agent } = await Evalanche.boot({ network: 'avalanche' });
console.log(agent.address);
const holdings = await agent.holdings().scan();
console.log(holdings.summary);npx evalanche-mcpEvalanche ships an MCP server for wallet actions, holdings discovery, DeFi, bridge and swap flows, Polymarket, and perpetual venues. The default MCP transport is stdio. HTTP mode is available for local automation, but requires an explicit bearer token:
EVALANCHE_MCP_HTTP_TOKEN="$(openssl rand -hex 32)" npx evalanche-mcp --http --port 3402- 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
Avalanche is the primary path, but Evalanche also supports Base, Ethereum, Arbitrum, Optimism, Polygon, BSC, and other EVM networks for execution and holdings discovery.
- Roadmap
- Release notes
- Release process
- Website source
- Smoke checklist
- Protocol notes
- Security
- Open gaps
- Security posture
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.
MIT