@agentlayer.tech/wallet 0.1.32 → 0.1.34

package/.openclaw/extensions/agent-wallet/dist/index.js

@@ -897,47 +897,6 @@ const solanaToolDefinitions = [
       additionalProperties: false,
     },
   },
-  {
-    name: "get_bags_claimable_positions",
-    description: "Get claimable Bags fee-share positions for a Solana wallet on mainnet.",
-    parameters: {
-      type: "object",
-      properties: {
-        wallet: {
-          type: "string",
-          description: "Optional wallet address override.",
-        },
-      },
-      additionalProperties: false,
-    },
-  },
-  {
-    name: "get_bags_fee_analytics",
-    description: "Get Bags fee analytics for a launched token, with optional claim event history.",
-    parameters: {
-      type: "object",
-      properties: {
-        token_mint: {
-          type: "string",
-          description: "Launched token mint address.",
-        },
-        include_claim_events: {
-          type: "boolean",
-          description: "If true, also fetch claim event history.",
-        },
-        mode: {
-          type: "string",
-          enum: ["offset", "time"],
-        },
-        limit: { type: "integer" },
-        offset: { type: "integer" },
-        from_ts: { type: "integer" },
-        to_ts: { type: "integer" },
-      },
-      required: ["token_mint"],
-      additionalProperties: false,
-    },
-  },
   {
     name: "get_flash_trade_markets",
     description: "List Flash Trade perpetual markets currently available on Solana mainnet.",
@@ -1144,22 +1103,6 @@ const solanaToolDefinitions = [
       additionalProperties: false,
     },
   },
-  {
-    name: "claim_bags_fees",
-    description: "Preview, prepare, or execute a Bags fee-share claim for the connected wallet on mainnet. Preview or prepare first. After the user explicitly confirms the shown summary in chat, call execute; the OpenClaw plugin handles the internal execution authorization automatically.",
-    optional: true,
-    parameters: {
-      type: "object",
-      properties: {
-        token_mint: { type: "string" },
-        mode: { type: "string", enum: ["preview", "prepare", "execute"] },
-        purpose: { type: "string" },
-        user_intent: { type: "boolean" },
-      },
-      required: ["token_mint", "mode", "purpose"],
-      additionalProperties: false,
-    },
-  },
   {
     name: "launch_bags_token",
     description: "Preview, prepare, or execute a Bags token launch with fee-share config on mainnet. Preview or prepare first. After the user explicitly confirms the shown summary in chat, call execute; the OpenClaw plugin handles the internal execution authorization automatically.",
@@ -1748,7 +1691,7 @@ const evmToolDefinitions = [
   },
   {
     name: "get_evm_swap_quote",
-    description: "Get a read-only Velora quote for an ERC-20 to ERC-20 swap on supported EVM mainnet networks. This does not approve or execute a swap.",
+    description: "Get a read-only Velora quote for an ERC-20 or native ETH swap on supported EVM mainnet networks. This does not approve or execute a swap.",
     parameters: {
       type: "object",
       properties: {
@@ -1763,7 +1706,7 @@ const evmToolDefinitions = [
   },
   {
     name: "swap_evm_tokens",
-    description: "Preview, prepare, or execute an ERC-20 to ERC-20 swap through Velora on supported EVM mainnet networks. Preview or prepare first. After the user explicitly confirms the shown summary in chat, call execute; the OpenClaw plugin handles the internal execution authorization automatically.",
+    description: "Preview, prepare, or execute an ERC-20 or native ETH swap through Velora on supported EVM mainnet networks. Preview or prepare first. After the user explicitly confirms the shown summary in chat, call execute; the OpenClaw plugin handles the internal execution authorization automatically.",
     optional: true,
     parameters: {
       type: "object",

package/.openclaw/extensions/agent-wallet/index.ts

@@ -897,47 +897,6 @@ const solanaToolDefinitions = [
       additionalProperties: false,
     },
   },
-  {
-    name: "get_bags_claimable_positions",
-    description: "Get claimable Bags fee-share positions for a Solana wallet on mainnet.",
-    parameters: {
-      type: "object",
-      properties: {
-        wallet: {
-          type: "string",
-          description: "Optional wallet address override.",
-        },
-      },
-      additionalProperties: false,
-    },
-  },
-  {
-    name: "get_bags_fee_analytics",
-    description: "Get Bags fee analytics for a launched token, with optional claim event history.",
-    parameters: {
-      type: "object",
-      properties: {
-        token_mint: {
-          type: "string",
-          description: "Launched token mint address.",
-        },
-        include_claim_events: {
-          type: "boolean",
-          description: "If true, also fetch claim event history.",
-        },
-        mode: {
-          type: "string",
-          enum: ["offset", "time"],
-        },
-        limit: { type: "integer" },
-        offset: { type: "integer" },
-        from_ts: { type: "integer" },
-        to_ts: { type: "integer" },
-      },
-      required: ["token_mint"],
-      additionalProperties: false,
-    },
-  },
   {
     name: "get_flash_trade_markets",
     description: "List Flash Trade perpetual markets currently available on Solana mainnet.",
@@ -1144,22 +1103,6 @@ const solanaToolDefinitions = [
       additionalProperties: false,
     },
   },
-  {
-    name: "claim_bags_fees",
-    description: "Preview, prepare, or execute a Bags fee-share claim for the connected wallet on mainnet. Preview or prepare first. After the user explicitly confirms the shown summary in chat, call execute; the OpenClaw plugin handles the internal execution authorization automatically.",
-    optional: true,
-    parameters: {
-      type: "object",
-      properties: {
-        token_mint: { type: "string" },
-        mode: { type: "string", enum: ["preview", "prepare", "execute"] },
-        purpose: { type: "string" },
-        user_intent: { type: "boolean" },
-      },
-      required: ["token_mint", "mode", "purpose"],
-      additionalProperties: false,
-    },
-  },
   {
     name: "launch_bags_token",
     description: "Preview, prepare, or execute a Bags token launch with fee-share config on mainnet. Preview or prepare first. After the user explicitly confirms the shown summary in chat, call execute; the OpenClaw plugin handles the internal execution authorization automatically.",
@@ -1748,7 +1691,7 @@ const evmToolDefinitions = [
   },
   {
     name: "get_evm_swap_quote",
-    description: "Get a read-only Velora quote for an ERC-20 to ERC-20 swap on supported EVM mainnet networks. This does not approve or execute a swap.",
+    description: "Get a read-only Velora quote for an ERC-20 or native ETH swap on supported EVM mainnet networks. This does not approve or execute a swap.",
     parameters: {
       type: "object",
       properties: {
@@ -1763,7 +1706,7 @@ const evmToolDefinitions = [
   },
   {
     name: "swap_evm_tokens",
-    description: "Preview, prepare, or execute an ERC-20 to ERC-20 swap through Velora on supported EVM mainnet networks. Preview or prepare first. After the user explicitly confirms the shown summary in chat, call execute; the OpenClaw plugin handles the internal execution authorization automatically.",
+    description: "Preview, prepare, or execute an ERC-20 or native ETH swap through Velora on supported EVM mainnet networks. Preview or prepare first. After the user explicitly confirms the shown summary in chat, call execute; the OpenClaw plugin handles the internal execution authorization automatically.",
     optional: true,
     parameters: {
       type: "object",

package/.openclaw/extensions/agent-wallet/openclaw.plugin.json

@@ -2,16 +2,13 @@
   "id": "agent-wallet",
   "name": "Agent Wallet",
   "description": "Official OpenClaw plugin bridge for the agent-wallet backends, including Solana, local BTC, and local EVM.",
-  "version": "0.1.0",
+  "version": "0.1.34",
   "contracts": {
     "tools": [
-      "claim_bags_fees",
       "close_empty_token_accounts",
       "flash_trade_close_position",
       "flash_trade_open_position",
       "get_active_wallet_backend",
-      "get_bags_claimable_positions",
-      "get_bags_fee_analytics",
       "get_btc_fee_rates",
       "get_btc_max_spendable",
       "get_btc_transfer_history",

package/.openclaw/extensions/agent-wallet/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@agentlayertech/agent-wallet-plugin",
-  "version": "0.1.32",
+  "version": "0.1.34",
   "description": "OpenClaw plugin bridge for the AgentLayer wallet runtime.",
   "type": "module",
   "license": "SEE LICENSE IN ../../../LICENSE",

package/CHANGELOG.md

@@ -2,6 +2,72 @@
 
 ## Unreleased
 
+## v0.1.34 - 2026-06-02
+
+- Added native ETH support to EVM (Velora) swaps in the wallet runtime.
+
+- Single source of truth for the project version across every framework.
+  - Added a canonical root `VERSION` file. All other manifests (npm
+    `package.json`, `pyproject.toml`, Python `__version__`, the OpenClaw
+    extension, and the Codex / Claude Code / Hermes / wdk plugin manifests) are
+    now derived targets, stamped from `VERSION` via `scripts/sync_version.mjs`
+    (`npm run version:sync`). This realigned 7 manifests that had drifted to an
+    old `0.1.0`.
+  - `scripts/check_release_version.mjs` now verifies all 11 manifests against
+    `VERSION` (and against the `v*` tag on release), so version drift cannot be
+    merged or published. Shared logic lives in `scripts/version_targets.mjs`.
+  - `npm run release:local -- <version>` bumps, stamps, verifies, and reinstalls
+    the runtime into every local framework (OpenClaw, Codex, Claude Code) from
+    the working tree — the same files that ship to npm/ClawHub. `--dry-run`
+    previews the steps without changing anything.
+  - `wallet status` / `wallet doctor` gained a `runtime_in_sync` signal flagging
+    when the installed runtime lags the repo/CLI version (informational; never
+    flips doctor's overall ok).
+
+- Added a background "update available" check so agents (and the humans behind
+  them) learn when a newer agent-wallet version is published.
+  - `agent_wallet/update_check.py` compares the installed `__version__` against
+    the latest version on the npm registry. The network call runs in a daemon
+    thread and only refreshes a cache (`OPENCLAW_HOME/agent-wallet-runtime/
+    update-check.json`) at most once/day for the *next* start — it never blocks
+    server startup, and any failure is silently ignored (fail-open).
+  - The MCP server (`server.py`) appends a one-time notice to its `instructions`
+    when a newer version is cached. Because instructions are read once per
+    session, the agent sees it at most once per usage cycle, and a per-version
+    daily throttle prevents repeats across sessions.
+  - `wallet status` now includes an `update_available` block and `wallet doctor`
+    adds an informational `update_available` check (with a ready `fix` command);
+    neither flips doctor's overall `ok`.
+  - Opt out entirely with `AGENT_WALLET_DISABLE_UPDATE_CHECK=1`.
+  - `agent_wallet/__init__.py` now carries `__version__`, and
+    `scripts/check_release_version.mjs` enforces that it stays in sync with
+    `package.json` / `pyproject.toml` on release.
+
+## v0.1.33 - 2026-06-01
+
+- Hardened runtime resolution end-to-end so a broken or stale runtime can no
+  longer surface as an opaque MCP `-32000`.
+  - `run_mcp.sh` (Codex + Claude Code) now self-checks the resolved `server.py`
+    with `py_compile` and emits a structured, actionable JSON error (with a
+    `fix` command) when the server is missing or fails to parse, instead of
+    silently handing a broken file to Python. JSON errors are emitted safely so
+    arbitrary paths cannot produce invalid JSON.
+  - `doctor` / `doctor --deep` now validate the live `current` runtime — symlink
+    integrity, venv python, `server.py` parse, a real MCP `initialize` handshake
+    (under `--deep`), and per-editor resolution — and attach a `fix` command to
+    every failing check (output is a structured `checks[]` array).
+  - `install` / `update` now verify the newly-activated release via an MCP
+    handshake and auto-rollback `current → previous` on failure, with guidance
+    classified as `broken_release` (our side — you stay safe on the previous
+    version) vs `local_env` (fixable locally). A first install with no previous
+    version leaves no broken runtime active and does not park the broken release
+    under `previous`.
+  - `codex install` / `claude-code install` pin the resolved `OPENCLAW_HOME`
+    into the editor `.mcp.json` env (bundle and, for Claude Code, existing
+    version-keyed cache copies), eliminating launcher/installer home divergence.
+    The venv python is intentionally not pinned so it stays correct across
+    runtime upgrades.
+
 ## v0.1.32 - 2026-06-01
 
 - Fixed a `SyntaxError` in `codex/plugins/agent-wallet/server.py` introduced by

package/README.md

@@ -218,13 +218,10 @@ Flash Trade integration adds a managed perpetuals surface on Solana mainnet:
 - `flash_trade_open_position` - preview, prepare, or execute a perp position open.
 - `flash_trade_close_position` - preview, prepare, or execute a perp position close.
 
-### Bags launch and fee-share
+### Bags launch
 
-Bags-backed tools cover token launch and post-launch fee analytics:
+Bags-backed tools currently cover token launch:
 
-- `get_bags_claimable_positions` - inspect claimable Bags fee-share positions for a Solana wallet.
-- `get_bags_fee_analytics` - fetch analytics and optional claim history for a launched token.
-- `claim_bags_fees` - preview, prepare, or execute a Bags fee-share claim.
 - `launch_bags_token` - preview, prepare, or execute a Bags token launch with fee-share configuration.
 
 ### EVM DeFi integrations

package/RELEASING.md

@@ -29,54 +29,74 @@ example `v0.1.10`.
 The same tag workflow also creates a GitHub Release on the repository's
 Releases page after npm publish succeeds.
 
-The tag version must match both source version files:
+## Version Single Source of Truth
+
+The canonical version lives in **one** file at the repo root:
 
 ```text
-package.json
-agent-wallet/pyproject.toml
+VERSION
 ```
 
-If those versions do not match the tag, the workflow fails before publishing.
-The same `v*` tag can also trigger the ClawHub plugin publish workflow, so keep
-the root installer versions aligned with the ClawHub plugin package versions
-when you want one GitHub release to ship both surfaces together.
+Every other manifest (npm `package.json`, `agent-wallet/pyproject.toml`, the
+Python `__version__`, the OpenClaw extension, and the Codex / Claude Code /
+Hermes / wdk plugin manifests) is a *derived* target. Do not edit them by hand —
+stamp them from `VERSION`:
 
-## Stable Release
+```bash
+npm run version:sync          # stamp VERSION into all manifests
+# or bump + stamp in one step:
+node scripts/sync_version.mjs 0.1.34
+```
 
-Use a stable release when users should get it from the default install command.
+`npm run check:release-version` verifies that `VERSION`, every derived manifest,
+and (on a tag) the `v*` tag all agree. It runs on every PR/push, so drift cannot
+be merged. The `v*` tag also triggers the ClawHub plugin publish workflow; since
+all manifests are stamped from `VERSION`, one tag ships every surface in lockstep.
 
-Example: publish `0.1.10` as npm `latest`.
+### Local release (install into all frameworks)
 
-1. Update `package.json`:
+To make your own OpenClaw / Codex / Claude Code editors run a freshly bumped
+version from the working tree (bump → stamp → verify → reinstall everywhere):
 
-```json
-"version": "0.1.10"
+```bash
+npm run release:local -- 0.1.34            # do it
+npm run release:local -- 0.1.34 --dry-run  # preview the steps, change nothing
 ```
 
-2. Update `agent-wallet/pyproject.toml`:
+`wallet doctor` and `wallet status` report `runtime_in_sync`, flagging when the
+installed runtime lags the repo version (i.e. you bumped but forgot to reinstall).
 
-```toml
-version = "0.1.10"
+## Stable Release
+
+Use a stable release when users should get it from the default install command.
+
+Example: publish `0.1.10` as npm `latest`.
+
+1. Bump the canonical version and stamp every manifest:
+
+```bash
+node scripts/sync_version.mjs 0.1.10
 ```
 
-3. Run local checks:
+2. Run local checks:
 
 ```bash
 npm run check
 GITHUB_REF_NAME=v0.1.10 npm run check:release-version
 python3 agent-wallet/tests/smoke_npm_installer.py
 python3 agent-wallet/tests/smoke_install_agent_wallet.py
+python3 agent-wallet/tests/smoke_version_consistency.py
 npm --cache /tmp/npm-cache pack --dry-run
 ```
 
-4. Commit the version change:
+3. Commit the version change (VERSION + all stamped manifests):
 
 ```bash
-git add package.json agent-wallet/pyproject.toml
+git add -A
 git commit -m "Release npm installer 0.1.10"
 ```
 
-5. Create and push the release tag:
+4. Create and push the release tag:
 
 ```bash
 git tag -a v0.1.10 -m "v0.1.10"
@@ -84,7 +104,7 @@ git push origin main
 git push origin v0.1.10
 ```
 
-6. Check npm after GitHub Actions finishes:
+5. Check npm after GitHub Actions finishes:
 
 ```bash
 npm view @agentlayer.tech/wallet dist-tags
@@ -104,16 +124,16 @@ The GitHub Releases page should also contain a new release named `v0.1.10`.
 Use a beta release when you want to test npm publishing without changing the
 default user install command.
 
-Example: publish `0.1.11-beta.1` as npm `beta`.
+Beta is the "earlier than users" channel: it publishes a real artifact to the
+npm `beta` dist-tag (and a GitHub prerelease) without moving `latest`, so you can
+test exactly what users would get before promoting it.
 
-1. Set both version files to the beta version:
+Example: publish `0.1.11-beta.1` as npm `beta`.
 
-```json
-"version": "0.1.11-beta.1"
-```
+1. Bump + stamp the beta version:
 
-```toml
-version = "0.1.11-beta.1"
+```bash
+node scripts/sync_version.mjs 0.1.11-beta.1
 ```
 
 2. Run checks:
@@ -127,7 +147,7 @@ npm --cache /tmp/npm-cache pack --dry-run
 3. Commit, tag, and push:
 
 ```bash
-git add package.json agent-wallet/pyproject.toml
+git add -A
 git commit -m "Release npm installer 0.1.11-beta.1"
 git tag -a v0.1.11-beta.1 -m "v0.1.11-beta.1"
 git push origin main
@@ -144,6 +164,13 @@ npx @agentlayer.tech/wallet@beta doctor
 The GitHub Releases page should contain a new prerelease named
 `v0.1.11-beta.1`.
 
+### Promote a beta to stable
+
+Once a beta checks out, ship the same version as a stable `latest` release by
+following the **Stable Release** steps with the promoted version number (e.g.
+`0.1.11`). The update notice that runtimes show to agents reads the `latest`
+dist-tag, so users are only nudged toward promoted releases, never betas.
+
 ## What Ships
 
 The npm package is intentionally limited to the wallet installer runtime:

package/VERSION

@@ -0,0 +1 @@
+0.1.34

package/agent-wallet/.env.example

@@ -43,7 +43,6 @@ SOLANA_AGENT_KEYPAIR_PATH=
 JUPITER_API_BASE_URL=https://lite-api.jup.ag/swap/v1
 JUPITER_ULTRA_API_BASE_URL=https://lite-api.jup.ag/ultra/v1
 JUPITER_PRICE_API_BASE_URL=https://lite-api.jup.ag/price/v3
-JUPITER_PORTFOLIO_API_BASE_URL=https://api.jup.ag/portfolio/v1
 JUPITER_API_KEY=
 
 # LI.FI cross-chain routing. API key is optional for basic read-only quote/status calls.

package/agent-wallet/README.md

@@ -106,12 +106,6 @@ Current safe tools:
 - `x402_preview_request`
 - `x402_pay_request`
 
-Temporarily disabled but kept in the codebase for later re-enable:
-
-- `get_jupiter_portfolio_platforms`
-- `get_jupiter_portfolio`
-- `get_jupiter_staked_jup`
-
 The signing tool still requires explicit `user_confirmed=true`.
 Transfer, native staking, swap, and Aave position-management tools support `preview`, `prepare`, and `execute` modes. The safe operational path is still preview-first. `prepare` now returns an execution plan only and never exposes signed transaction bytes to the agent. `execute` works only when the backend has a signer and `sign_only=false`.
 
@@ -491,8 +485,6 @@ Operational notes:
 
 - Jupiter `Earn` can use the hosted or self-hosted provider gateway for shared onboarding-friendly access.
 - Ordinary Jupiter swap routing remains direct and does not go through the provider gateway.
-- Jupiter `Portfolio` implementation remains in the backend, but the agent-facing tools are temporarily disabled.
-- The Jupiter config fields and provider code are intentionally kept so these surfaces can be restored later without rebuilding the integration from scratch.
 
 ## Flash Trade coverage
 

package/agent-wallet/agent_wallet/__init__.py

@@ -1,11 +1,16 @@
 """OpenClaw agent wallet package."""
 
+# Keep in sync with package.json, pyproject.toml, and the npm installer version.
+# scripts/check_release_version.mjs enforces this on release.
+__version__ = "0.1.34"
+
 __all__ = [
     "config",
     "exceptions",
     "models",
     "openclaw_runtime",
     "providers",
+    "update_check",
     "validation",
     "wallet_layer",
 ]

package/agent-wallet/agent_wallet/config.py

@@ -48,7 +48,6 @@ class Settings(BaseSettings):
     jupiter_swap_v2_api_base_url: str = "https://api.jup.ag/swap/v2"
     jupiter_ultra_api_base_url: str = "https://lite-api.jup.ag/ultra/v1"
     jupiter_price_api_base_url: str = "https://lite-api.jup.ag/price/v3"
-    jupiter_portfolio_api_base_url: str = "https://api.jup.ag/portfolio/v1"
     jupiter_api_key: str = ""
     lifi_api_base_url: str = "https://li.quest/v1"
     lifi_api_key: str = ""