Skip to content

evalanche

Agentic Finance

HEY verified shipping evidence from the project’s own public sources; ownership of this page is not claimed yet.

Agent wallet SDK for Avalanche with onchain identity (ERC-8004) and payment rails (x402)

What HEY knows

Building
Shipped this weekDerivedShipping: 4 meaningful events in 30 days; latest ship yesterday. Details Source

Build Momentum 45How it is measured

Latest ship
Evalanche v1.14.0 · · GitHub release

Why it matters: First release after 28 quiet days.

FollowCreate alertTerminal previewView latest ship
ShareShare on X

Follow puts evalanche on your private watchlist and at the top of “Since you were last here” when you come back. Then pick what HEY should notify you about. Following needs an account; browsing never does.

Without an account:RSS
Email me evalanche’s changes

No account and no password. HEY stores the address and what you asked for, sends one confirmation, and nothing else until you confirm. Every email has a one-click unsubscribe that deletes the address.

Token market · context
No token tracked
Not yet known
Unknown3 gaps: Official docs (no source), API description (not enough yet), Official site changes (not enough yet). HEY read its website and found no link to docs.

HEY can answer 8 of the 11 research questions that apply · Research coverage

What HEY checked — why it says this
Shipping.
SHIPPING by the activity rule: 4 meaningful events in the last 30 days, the newest 2026-10-05.
SourceRepositories, changelogs and feeds HEY reads for this project, and the ship events recorded from them.ReadRecordsship:702dfbb4-b62d-4880-aca2-86284a88cb5fship:f409b853-a97d-4864-910d-f3757289973aship:15e4cfea-0cc2-4353-83d7-c8110852cb28+2 moreWhat HEY derivedThe activity rule under hbm-v24 gives SHIPPING.Not concludedIt says what HEY can read of the building, not how good the project is, who is behind it, or what its token will do. Quiet or unknown is not "abandoned".
Verified Builder.
The quality gate found verified building evidence from the project's own sources.
Source2 registered sources, 0 of them context only.ReadWhat HEY derivedVERIFIED_BUILDER (VERIFIED_BUILDER).Not concludedA verified builder is one whose shipping HEY confirmed from public evidence. It does not say who runs the project — that is the ownership claim, a separate check.
Market figures are context only and never change activity status. Methodology

Latest ship

Evalanche v1.14.0

GitHub releaseSource verified

Evalanche v1.14.0 — Avalanche SDK and L1 hardening This feature release strengthens Avalanche as Evalanche's default execution environment. Highlights · Make Avalanche the hardened default with the official @avalanche-sdk/client, removing the legacy Core wallet and vulnerable… Show all
  • Evalanche v1.14.0 — Avalanche SDK and L1 hardening This feature release strengthens Avalanche as Evalanche's default execution environment. Highlights
  • Make Avalanche the hardened default with the official @avalanche-sdk/client, removing the legacy Core wallet and vulnerable HPKE dependency trees from fresh consumer installs.
  • Expand Avalanche L1 support with live mainnet and Fuji catalog discovery, RPC chain ID verification, native-token preservation, and public SDK/MCP helpers.
  • Remove the dYdX SDK, exports, MCP tools, holdings detector, and transitive Cosmos dependencies…

Record ship:702dfbb4… · HEY counts it as building; it does not judge the release’s quality or what it means for the token.

Builder activity

Bars: meaningful, source-backed ships per week (count). Weeks run Monday to Sunday, UTC, labelled by their Monday. Commits are aggregated, a code week counted once. Hatched: 6 weeks before HEY began reading this project’s sources — not yet read, not zero.

Build timeline

  1. Code changes, week of 2026-10-05 – 2026-10-11 · 2 commits

    Code activitySource linked

    3 active days in ijaack/evalanche.

    What changed, in the repository’s own words:

    This week HEY looked inside 2 commits to see what changed: 1 changed code, 1 documentation or maintenance only.

  2. Code changes, week of 2026-09-07 – 2026-09-13 · 2 commits

    Code activitySource linked

    2 active days in ijaack/evalanche.

    What changed, in the repository’s own words:

    This week HEY looked inside 2 commits to see what changed: 1 changed code, 1 documentation or maintenance only.

  3. Evalanche v1.13.0

    GitHub releaseSource verified

    Evalanche v1.13.0 — Reliability and dependency hardening Highlights · Fix vault holdings conversion failures: preserve verified shares, omit unavailable underlying assets, emit a warning and lower confidence until conversion recovers. · Run SDK tests, type checking, builds, docs… Show all
    • Evalanche v1.13.0 — Reliability and dependency hardening Highlights
    • Fix vault holdings conversion failures: preserve verified shares, omit unavailable underlying assets, emit a warning and lower confidence until conversion recovers.
    • Run SDK tests, type checking, builds, docs parity, package validation and audit gates on pull requests and main pushes. Bound test workers to reduce CPU contention without increasing assertion timeouts.
    • Add bounded live read compatibility checks for Avalanche, Robinhood Chain, Hyperliquid, Polymarket and LI.FI quotes, with timestamped commit-linked…
  4. Evalanche v1.12.0

    GitHub releaseSource verified

    Highlights · Adds first-class Robinhood Chain mainnet support through the named robinhood network alias and chain ID 4663, with official ETH, RPC, explorer, and LI.FI metadata. · Extends wallet boot, network switching, MCP chain discovery and switching, and native holdings scans… Show all
    • Highlights
    • Adds first-class Robinhood Chain mainnet support through the named robinhood network alias and chain ID 4663, with official ETH, RPC, explorer, and LI.FI metadata.
    • Extends wallet boot, network switching, MCP chain discovery and switching, and native holdings scans to Robinhood Chain through Evalanche's central EVM registry.
    • Preserves the Robinhood network with RPC overrides supplied through ROBINHOODRPCURLS, EVALANCHEROBINHOODRPCURLS, and MCP AVALANCHERPC_URL, keeping the selected network alias authoritative.
    • Tests certify Robinhood bridge capabilities…
  5. Code changes, week of 2026-07-06 – 2026-07-12 · at least 13 commits

    Code activitySource linked

    4 active days in iJaack/evalanche.

    This week HEY looked inside 4 of 13 commits to see what changed: 1 changed code, 3 documentation or maintenance only. One code change is enough for the week to count, so HEY stopped there.

  6. Evalanche v1.11.0

    GitHub releaseSource verified

    Highlights · Replaces the Polymarket SDK execution path with the official polymarket CLI for authenticated venue operations. · Routes the MCP Polymarket wallet tools through a hardened CLI adapter that uses execFile, forces JSON output, avoids argv secrets, redacts signer… Show all
    • Highlights
    • Replaces the Polymarket SDK execution path with the official polymarket CLI for authenticated venue operations.
    • Routes the MCP Polymarket wallet tools through a hardened CLI adapter that uses execFile, forces JSON output, avoids argv secrets, redacts signer material, and fails closed on malformed CLI output.
    • Removes @polymarket/clob-client, @polymarket/clob-client-v2, and the local Polymarket client type shim from the package dependency surface.
    • Removes hidden raw/diagnostic Polymarket write paths so production agents use the advertised preflight, execution, and…
  7. Evalanche v1.10.1

    GitHub releaseSource verified

    Highlights · Retries the Polymarket release line on a fresh patch version after the v1.10.0 npm provenance publish failed at the transparency-log step despite the GitHub release succeeding. · Keeps the working Polymarket CLOB v2 buy path, funding fixes, and updated MCP/test… Show all
    • Highlights
    • Retries the Polymarket release line on a fresh patch version after the v1.10.0 npm provenance publish failed at the transparency-log step despite the GitHub release succeeding.
    • Keeps the working Polymarket CLOB v2 buy path, funding fixes, and updated MCP/test coverage introduced in v1.10.0.
    • Hardens the release workflow so a transparency-log duplicate during npm publish --provenance only auto-passes when the target package version is already live on npm. Validation
    • npm test
    • npm run typecheck
    • npm run build Notes
    • v1.10.0 remains published as a…
  8. Evalanche v1.10.0

    GitHub releaseSource verified

    Highlights · Switched Polymarket buy execution onto the current CLOB v2 path so live order submission works against the latest venue order format instead of failing on legacy order-version rejections. · Added explicit Polygon / Polymarket collateral handling improvements around… Show all
    • Highlights
    • Switched Polymarket buy execution onto the current CLOB v2 path so live order submission works against the latest venue order format instead of failing on legacy order-version rejections.
    • Added explicit Polygon / Polymarket collateral handling improvements around CLOB funding, venue reconciliation, and chain/network mapping needed for current Polymarket execution flows.
    • Expanded Polymarket MCP coverage with updated buy-path tests, geoblock envelope handling, v2 order behavior, and refreshed chain expectations. Validation
    • npm test
    • npm run typecheck
    • `npm run…
  9. Evalanche v1.9.7

    GitHub releaseSource verified

    Highlights · 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… Show all
    • Highlights
    • 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-intent mode for trusted peer flows and tests.
    • Fixed Polymarket collateral normalization for…
  10. v1.9.5

    GitHub releaseSource verified

    Highlights · Fixed Li.Fi EVM quote normalization so Base → Polygon USDC bridge requests strip CAIP-10 eip155: : prefixes before sending fromAddress / toAddress to Li.Fi. · Added regression coverage for Base → Polygon native USDC quote construction, matching Mony’s Polymarket… Show all
    • Highlights
    • Fixed Li.Fi EVM quote normalization so Base → Polygon USDC bridge requests strip CAIP-10 eip155: : prefixes before sending fromAddress / toAddress to Li.Fi.
    • Added regression coverage for Base → Polygon native USDC quote construction, matching Mony’s Polymarket buffer top-up path. Validation
    • npm test -- test/bridge/lifi.test.ts
    • npm run typecheck
    • npm run build
    • live bridge quote smoke: Base USDC → Polygon native USDC with CAIP-10 fromAddress Notes
    • This unblocks autonomous Polymarket cash-buffer top-ups where the wallet needs to bridge small…
  11. Evalanche v1.9.2

    GitHub releaseSource verified

    Highlights · Added macOS Keychain fallback for agent credentials, so Mony and other local agents can resolve the EvaWallet / EvaMain sovereign wallet after OpenClaw secrets and env vars and before the encrypted keystore path · Made Polymarket orderbook handling deterministic by… Show all
    • Highlights
    • Added macOS Keychain fallback for agent credentials, so Mony and other local agents can resolve the EvaWallet / EvaMain sovereign wallet after OpenClaw secrets and env vars and before the encrypted keystore path
    • Made Polymarket orderbook handling deterministic by sorting visible bids highest-first and asks lowest-first before pricing, preflight, and sell-fill estimation
    • Preserved the v1.9.0 Polymarket withdrawal flow while promoting the Mony-tested Evalanche runtime fixes into the public release line
    • Added focused regression coverage for keychain credential…
  12. Evalanche v1.9.0

    GitHub releaseSource verified

    Highlights · Implemented pmwithdraw, so Evalanche can now withdraw Polygon USDC.e from the Polymarket wallet through the official Polymarket bridge flow · pmwithdraw gets a bridge quote, creates withdrawal addresses, submits the onchain USDC.e transfer, and returns the initial… Show all
    • Highlights
    • Implemented pmwithdraw, so Evalanche can now withdraw Polygon USDC.e from the Polymarket wallet through the official Polymarket bridge flow
    • pmwithdraw 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 Validation
    • npm run test
    • npm run typecheck…
  13. Evalanche v1.8.9

    GitHub releaseSource verified

    Highlights · Implemented Polymarket redemption through the real pmredeem path on the Conditional Tokens Framework on Polygon · pmredeem now verifies resolution onchain, submits redeemPositions, and reports USDC plus token-balance deltas · Expanded the release workflow into a… Show all
    • Highlights
    • Implemented Polymarket redemption through the real pmredeem path on the Conditional Tokens Framework on Polygon
    • pmredeem now verifies resolution onchain, submits redeemPositions, and reports USDC plus token-balance deltas
    • Expanded the release workflow into a stricter certification pipeline with integrity, docs-parity, tarball, audit-regression, smoke, and manifest gates
    • Aligned published package entrypoints with the actual build output so the tarball matches both CommonJS and ESM consumers
    • Simplified release notes by removing redundant in-file version titles…
  14. Evalanche v1.8.8

    GitHub releaseSource verified

    Evalanche v1.8.8 Highlights · Added a universal in-repo holdings registry shared by all agents · Added unified holdings scanning through agent.holdings().scan() · Added MCP tools: · getholdings · searchregistry · registry_status · Unified DeFi routing and holdings discovery onto… Show all
    • Evalanche v1.8.8 Highlights
    • Added a universal in-repo holdings registry shared by all agents
    • Added unified holdings scanning through agent.holdings().scan()
    • Added MCP tools:
    • getholdings
    • searchregistry
    • registry_status
    • Unified DeFi routing and holdings discovery onto the same universal registry
    • Added DefiLlama import tooling for maintainers via npm run sync:defillama-registry
    • Updated the README and npm package metadata to match the shipped package surface Holdings Coverage The unified scanner now covers:
    • native balances across supported EVM chains…
  15. Evalanche v1.8.7

    GitHub releaseSource verified

    Evalanche v1.8.7 This release hardens live execution and canonical-chain DeFi routing, with the fixes validated against funded wallets and a full green test/build pass. Highlights · Polymarket live execution fixes: · pmbuy now uses the SDK-compatible buy-order nonce path again… Show all
    • Evalanche v1.8.7 This release hardens live execution and canonical-chain DeFi routing, with the fixes validated against funded wallets and a full green test/build pass. Highlights
    • Polymarket live execution fixes:
    • pmbuy now uses the SDK-compatible buy-order nonce path again, fixing live invalid nonce failures.
    • pmbuy surfaces venue rejections honestly, including geoblocking and min-order-size errors.
    • pmbalances now reports allowance consistently from the true source of truth, including allowanceSource and matching rawAllowance.
    • live funded pmbuy was verified…
  16. Evalanche v1.8.6

    GitHub releaseSource verified

    Summary v1.8.6 closes the main issues raised in the March 28 capability report by making DeFi chain resolution deterministic, strengthening venue-truth reporting for Polymarket, and expanding the verification payloads returned by Hyperliquid and LI.FI MCP execution tools.… Show all
    • Summary v1.8.6 closes the main issues raised in the March 28 capability report by making DeFi chain resolution deterministic, strengthening venue-truth reporting for Polymarket, and expanding the verification payloads returned by Hyperliquid and LI.FI MCP execution tools. Highlights Chain-aware DeFi routing
    • added interoperable address parsing for DeFi inputs such as 0x...@base
    • introduced an Evalanche-owned dapp registry abstraction with local canonical mappings
    • routed known vaults like yoUSD to Base automatically
    • routed Avalanche-native staking like sAVAX to Avalanche…
  17. Evalanche v1.8.0

    GitHub releaseSource verified

    Evalanche v1.8.0 Highlights · Hyperliquid is now a first-class trading venue in both the SDK and MCP surface. · LI.FI execution flows now return stable verification envelopes instead of raw transaction-only responses. · Yield and vault quote/info paths were repaired, especially… Show all
    • Evalanche v1.8.0 Highlights
    • Hyperliquid is now a first-class trading venue in both the SDK and MCP surface.
    • LI.FI execution flows now return stable verification envelopes instead of raw transaction-only responses.
    • Yield and vault quote/info paths were repaired, especially around asset/share decimal handling and honest error mapping.
    • A release-grade live smoke checklist now documents the required Polymarket, Hyperliquid, LI.FI, and vault verification flow before ship. Included work Hyperliquid execution surface
    • added market orders, limit orders, cancellation…
  18. Evalanche v1.7.9

    GitHub releaseSource verified

    Evalanche 1.7.9 Summary This release fixes a Polymarket collateral unit mismatch that could make pmpreflight report a wallet as funded even when the venue balance was only a few cents in raw microUSDC. Highlights · normalized Polymarket collateral balance and allowance reads… Show all
    • Evalanche 1.7.9 Summary This release fixes a Polymarket collateral unit mismatch that could make pmpreflight report a wallet as funded even when the venue balance was only a few cents in raw microUSDC. Highlights
    • normalized Polymarket collateral balance and allowance reads from raw 6-decimal USDC units into human USDC before buy preflight checks
    • added raw collateral fields to the pmbalances response so agents can inspect both display and venue-native values
    • pm_buy now fails deterministically in preflight for underfunded microUSDC wallets instead of reaching the CLOB…
  19. Evalanche v1.7.8

    GitHub releaseSource verified

    Evalanche 1.7.8 Summary This release turns the Polymarket MCP surface into a more reliable execution layer by adding deterministic preflight checks, venue-first verification, and structured reconciliation tools. Highlights · added pmpreflight for buy, sell, and limit-sell… Show all
    • Evalanche 1.7.8 Summary This release turns the Polymarket MCP surface into a more reliable execution layer by adding deterministic preflight checks, venue-first verification, and structured reconciliation tools. Highlights
    • added pmpreflight for buy, sell, and limit-sell execution checks before order submission
    • added venue inspection and reconciliation tools: pmbalances, pmorder, pmopenorders, pmtrades, and pmreconcile
    • pmmarket and pmorderbook now return structured inspection results instead of brittle upstream exceptions
    • pmpositions now returns a…
  20. Evalanche v1.7.7

    GitHub releaseSource verified

    Evalanche 1.7.7 Summary This release hardens Polymarket sell execution so agents do not silently route into unsafe dust-floor fills. Highlights · pmsell now performs a slippage check against visible bid-side liquidity before execution · immediate sells are submitted as protected… Show all
    • Evalanche 1.7.7 Summary This release hardens Polymarket sell execution so agents do not silently route into unsafe dust-floor fills. Highlights
    • pmsell now performs a slippage check against visible bid-side liquidity before execution
    • immediate sells are submitted as protected FAK limit orders instead of unbounded market sells
    • Polymarket CLOB auth fallback now uses fresh nonces per derive/create attempt
    • pmlimitsell now respects postOnly: false instead of always forcing a resting order
    • regression tests were added for auth nonce handling, protected sells, and…
  21. Evalanche v1.7.6

    GitHub releaseSource verified

    Evalanche 1.7.6 Summary This release hardens the Polymarket integration and documents the agent-facing surface more clearly. Highlights · Polymarket market discovery now prefers live CLOB market reads and falls back to Gamma when needed · the SDK supports direct BUY and SELL… Show all
    • Evalanche 1.7.6 Summary This release hardens the Polymarket integration and documents the agent-facing surface more clearly. Highlights
    • Polymarket market discovery now prefers live CLOB market reads and falls back to Gamma when needed
    • the SDK supports direct BUY and SELL orders through placeOrder() and exposes a placeMarketSellOrder() helper for target-USDC sell flows
    • MCP now exposes pm_sell alongside the existing Polymarket read and buy tools
    • the README and skill docs now describe the Polymarket SDK flow, MCP tools, and current limitations for agents using the…
  22. Evalanche v1.7.5

    GitHub releaseSource verified

    Evalanche 1.7.5 Summary This release expands the routing and perp abstractions while tightening project planning into a single active roadmap. Highlights · LI.FI route selection now supports strategy-driven configuration such as minimumslippage, minimumexecutiontime… Show all
    • Evalanche 1.7.5 Summary This release expands the routing and perp abstractions while tightening project planning into a single active roadmap. Highlights
    • LI.FI route selection now supports strategy-driven configuration such as minimumslippage, minimumexecutiontime, fastestroute, and minimumcompletiontime
    • MCP and SDK LI.FI flows now expose routing controls like explicit route order, preset, max price impact, and simulation skipping
    • perpetuals were refactored around shared venue-neutral interfaces instead of dYdX-only shared types
    • Hyperliquid was added as a…
  23. Evalanche v1.7.2

    GitHub releaseSource verified

    Evalanche 1.7.2 Summary This patch release validates the corrected tag-driven release workflow after the 1.7.1 ClawHub publish failure. Highlights · the ClawHub release step now publishes the evalanche skill with an explicit slug instead of inferring skill from the folder name… Show all
    • Evalanche 1.7.2 Summary This patch release validates the corrected tag-driven release workflow after the 1.7.1 ClawHub publish failure. Highlights
    • the ClawHub release step now publishes the evalanche skill with an explicit slug instead of inferring skill from the folder name
    • the release pipeline remains tag-driven and continues to create the GitHub Release and publish to npm automatically
    • this release exists mainly to verify the final ClawHub leg of the automation Validation
    • local MCP version assertion updated to 1.7.2
    • targeted MCP server test remains green…
  24. Evalanche v1.7.1

    GitHub releaseSource verified

    Evalanche 1.7.1 Summary This patch release adds a tag-driven release pipeline so future Evalanche releases can publish more consistently from a single source of truth. Highlights · pushed vX.Y.Z tags now trigger the release workflow directly · the workflow validates… Show all
    • Evalanche 1.7.1 Summary This patch release adds a tag-driven release pipeline so future Evalanche releases can publish more consistently from a single source of truth. Highlights
    • pushed vX.Y.Z tags now trigger the release workflow directly
    • the workflow validates package.json, requires a matching RELEASENOTESX.Y.Z.md, and runs tests, typecheck, and build before publishing
    • GitHub Releases are now created automatically from the matching release-notes file
    • npm publish remains trusted-publishing based
    • ClawHub skill publication is now part of the automated release flow…

Research notes

Written by HEY researchers and reviewed before publishing. Commentary with sources — not the project's own claims, and not evidence of shipping.

Know something about evalanche? Sign in with GitHub to submit a research note. Notes are reviewed before they appear here.

Research coverage

HEY can answer 8 of the 11 research questions that apply.

8 of 11 applicable dimensions measuredShow each dimension

Identity

  • IdentityMeasuredRead 1mo ago.

Building

  • Building activityMeasuredRead 46m ago.
  • RepositoriesMeasured
  • ReleasesMeasuredRead 10h ago.
  • TimelineMeasured

Official site

  • Official docsNo sourceHEY read its website and found no link to docs.
  • API descriptionNot enough yetHEY has not read its website’s published files yet.
  • Official site changesNot enough yetHEY has no first reading of its website to compare against yet.

Code and packages

  • Repository detailsMeasuredRead 1d ago.
  • Published packagesMeasuredRead 37m ago.
  • Package advisoriesMeasuredRead 1d ago.

Not applicable here: Contract creation, Contract activity, Verified source, Contract interface, Current market, Market history, Supply distribution, Locks, Market checks, Protocol economics.

A count of what HEY has read, never a score: projects are not compared or ordered by it. Unknown is never zero. The same states: coverage API.

Sources