Changelog and Major Product Updates

Sellers now declare what will be delivered when they create a payment request: a required deliverables list (up to 20 items, each with an id, a kind, a description and whether it is required) and a required deliverBySeconds deadline. Buyers see the list before they fund, and it cannot be changed afterwards.

Proof submission is replaced by evidence. POST /api/agent/checkout/escrows/:id/evidence lets both the seller and the buyer add a link, a hash or a note against a deliverable. Entries are kept in an append-only record and are never edited or deleted. OpenClawCash does not fetch or judge them. A new webhook event, escrow.evidence_submitted, fires for every entry.

Timers are simple and fair: if the delivery deadline passes and a required deliverable has no seller evidence, the buyer is refunded automatically. Once the seller has evidence for every required deliverable and the auto-release time passes with no dispute, the seller is paid.

Escalated disputes are decided on the record, against the deliverables the seller declared. If delivery cannot be shown from the record, the buyer is refunded. OpenClawCash decides who gets the escrowed funds; it does not judge the goods.

Breaking change: creating a payment request without deliverables and deliverBySeconds now returns a validation error, and the old /proof endpoint and acceptance criteria are gone. Escrows created before this release keep working as they did. Agents should update to skill 1.31.0 and @openclawcash/[email protected].

The escrow rules now have one public home: GET /api/public/checkout/escrow-rules needs no key. Every escrow response carries an escrowRules block, and each payment request is pinned to the rules version in force when the buyer funded it, so the terms never change under a funded escrow.

Get a POST on your own server every time a transaction on one of your wallets confirms (wallet.transaction.confirmed), including every payment your agents make through the API.

Wallet webhooks are their own product, kept apart from escrow webhooks: manage them in the dashboard sidebar under Webhooks → Wallet (open Wallet webhooks), or create one with POST /api/agent/checkout/webhooks. Wallet events are opt-in, so pick them by name.

Every delivery is signed and time-stamped, so your server can check it is really from OpenClawCash before acting on it. Each event carries the direction, the sending and receiving address, the amount, the fee and the hash, so a payment is readable from the webhook alone.

If your server is down, we keep retrying for about a day so a payment notification is not lost. Respond with a 410 and the endpoint switches itself off.

Full reference and examples: Wallet webhooks in the docs.

See it end to end: an agent pays an invoice, the balance flashes, and a backend marks it paid.

Balances update themselves the second a transaction lands: wallet cards, the wallet page, token balances, and your ETH, POL and SOL totals. No refresh, no wondering whether a payment came in - open your wallets and watch it happen.

Money is readable at a glance: every change flashes green when funds come in and red when they go out, like a price ticker. You stay in the flow instead of refreshing a page to find out whether your agent got paid.

Privacy and comfort are respected: hidden balances stay masked, and the flash steps aside if your device is set to reduce motion.

Checkout escrow webhooks now arrive in the same signed, time-stamped format as the wallet webhooks above, so one receiver verifies everything your agents do. Receivers you already have keep working as they are.

Agents can now rename a wallet with PATCH /api/agent/wallet: pick the wallet by walletId, walletLabel, or walletAddress and send the new label. The MCP server adds a matching wallet_rename tool, and the agentwalletapi CLI gets a rename command.

Wallet names now follow one rule everywhere, in the dashboard, the API, and MCP: 1-32 characters using letters, numbers, spaces, and . _ - ( ) #, starting with a letter or number. Names are unique within your account, so choosing a wallet by name always points to exactly one wallet.

Creating or importing a wallet in the dashboard now tells you exactly why a name isn't accepted, instead of a generic error.

If your account already has two wallets with the same name, requests that choose a wallet by that name now return 409 wallet_label_ambiguous with the matching wallet IDs instead of guessing. Use the walletId for that request, then rename one of the wallets and choosing by name works again. Your existing wallets and names stay exactly as they are.

Connecting an agent now starts with the MCP server (npx -y @openclawcash/mcp-server). The CLI script is still available for clients that can't attach MCP servers. Ships with the agentwalletapi skill v1.28.0 and @openclawcash/[email protected].

Now you can hand a single API key to an agent that manages several wallets — pick any number of wallets when creating a key, instead of being stuck with "all wallets" or exactly one.

The wallet scope picker in Create API Key is now a checkbox list, so scoping a key to two, five, or every relevant wallet takes one dialog, not five separate keys.

If an agent presents a key outside its scoped wallets, it gets a clear 403 api_key_wallet_scope_forbidden response listing exactly which wallets it's allowed to use — no more guessing why a request was blocked.

The API Keys page now shows every wallet a key is scoped to at a glance, not just one.

Existing single-wallet-scoped keys keep working exactly as before — nothing to update on your end.

Three new agent endpoints bind a Solana wallet to a casino account: POST /api/agent/venues/yieldwolf-casino/link, POST /api/agent/venues/yieldwolf-casino/unlink, and a generic passthrough at ALL /api/agent/venues/yieldwolf-casino/proxy/<path> that forwards to YieldWolf's /api/v1/* for balance, deposit, gameplay, and transaction history. Lane (mainnet or devnet) is fixed at link time; the linked wallet is the only allowed withdrawal destination.

Every casino action routes through OpenClawCash, so you keep one audit trail across wallets and venues, and a revoked OpenClawCash key stops the agent immediately. The wallet owner can still reveal the underlying casino key from the venue page if they ever need to inspect or migrate. Operator flow lives at /venues/yieldwolf-casino with a one-click linker, balance, history, withdraw, and a clean unlink-or-destroy modal.

Casino docs: yieldwolf.finance and the agent skill at yieldwolf.finance/SKILL.md.

New POST /api/agent/bridge/quote, POST /api/agent/bridge/execute, and GET /api/agent/bridge/status endpoints let agents move funds between every supported EVM chain (Ethereum, Polygon, Base) without leaving OpenClawCash. Move USDC from Polygon to Base, ETH from Ethereum to Base, or POL to ETH in one quote-then-execute round trip.

Routes are picked automatically. The quote response tells you which underlying bridge ran (Across, NearIntents, Stargate, Hop, Connext, and more), the expected destination amount, and the estimated duration so you can decide before signing.

Status tracking is built in: poll /bridge/status?bridgeTxId=… to watch the transfer move from submitted through source_confirmed, destination_confirmed, and completed. Once it lands you get the destination chain tx hash and the amount received.

Idempotency-Key is required on execute so retries never double-submit. Replay the same key and payload after a network blip and you get the cached response, not a second on-chain transaction.

Quotes for Solana destinations work today; Solana source-side execute is on the roadmap. EVM sources are fully supported end-to-end.

Same wallet bucket model as transfer and swap: any EVM-home wallet can bridge from any supported EVM chain. @openclawcash/[email protected] exposes bridge_quote, bridge_execute, and bridge_status tools, and the agentwalletapi skill is updated to v1.25.0.

Open any wallet on the dashboard, switch the chain selector to Ethereum, Polygon, Base, or Sepolia, and see the activity that actually happened on that chain. Pending transactions you just kicked off through the agent API show up immediately, no more delay until the on-chain indexer catches up.

New "all chains" mode merges every transaction across Ethereum, Polygon, Base, and Sepolia into one unified history per wallet. Stop clicking through each chain to find that one transfer. The chain badge on each row tells you where it ran.

Agents calling GET /api/agent/transactions can now pass ?network=base-mainnet (or any supported EVM chain) to scope the response, or ?network=all to merge across the bucket. Calls that omit the field still return the wallet's default chain, exactly as before.

Every transaction row now carries the chain it ran on, so you always know whether the USDC transfer landed on Base or Polygon, even when you're looking at the merged view.

Base is now a first-class network on OpenClawCash alongside Ethereum, Polygon, and Sepolia. Create or import wallets on Base directly from the Wallets page, with full support for transfers, swaps, approvals, and balance reads.

Your EVM wallets are no longer tied to a single chain. The same wallet address now holds assets across Ethereum, Polygon, and Base, and the wallet card chip strip shows you exactly which chains your wallet has activity on. Funded the same address on three chains? You see all three at a glance.

The wallet detail page now scans your address for stablecoins and blue-chip tokens (USDC, USDT, DAI, WETH, cbETH, USDbC) across every EVM chain, so an ERC-20 only balance on a chain you didn't think to check still surfaces immediately.

Agents calling POST /api/agent/transfer, /api/agent/swap, and /api/agent/approve can pass an optional network field to run any EVM wallet on any EVM chain. Omit the field to use the wallet's default chain. Existing integrations that don't pass network behave exactly as before.

Polymarket linking now works with EVM wallets on any chain, not only Polygon-home wallets. Connect a wallet you already use elsewhere and link it to Polymarket without creating a separate one.

USDC, WETH, DAI, cbETH, and USDbC are recognized natively on Base from day one. Pass any token symbol or address in resolveToken, tokenBalance, or swap calls with network: "base-mainnet" and it works against the canonical Base contract.

Every new API key now has a chosen expiration window: 7, 30, 60, or 90 days. 90-day expiration is the new default and the hard ceiling, so keys can no longer live forever in an agent's config without you knowing.

The API keys page now shows an Expires column at a glance, so you can see at any moment which of your agents' keys are coming up for rotation and which are still healthy.

When an agent presents an expired key, the response is a clear 401 api_key_expired. No silent failures, no confusing 403s. Drop in a new key from the dashboard and your agent is back online.

Existing keys at the time of upgrade get an automatic 90-day grace window so live integrations aren't interrupted, but they will rotate. Plan now: create a fresh key, swap it in, and let the old one expire.

The success screen after creating a key has been clarified so it's obvious exactly what to copy, where to store it, and when it'll need replacing.

The agent OpenAPI spec now documents the optional network field on POST /api/agent/transfer, /api/agent/swap, and /api/agent/approve, so generated SDKs and IDE tooling pick the multi-chain bucket model up automatically.

Agent policy endpoints and their request/response shapes are now first-class in the spec, including spending limits, max-per-transfer, and trusted-token metadata. Integrations no longer have to hand-roll those types from documentation prose.

The spec stays locked to the live API: any schema change ships in the same release as the matching spec change, so generated client code never drifts out of sync with what the server actually accepts.

Newly connected Polymarket wallets are ready for on-chain actions like redeems and withdrawals from the moment they're created. Go from 'Connect Polymarket' to placing your first order in one continuous flow.

Setup auto-finalizes the instant your funding lands. The dashboard now polls funding events adaptively (fast right after deposit, then backing off) so you typically see your wallet flip from 'Funding…' to 'Ready' within seconds instead of waiting on a fixed timer.

If you've already connected Polymarket and just want to top up, the funding panel surfaces the live polling state so you can confirm receipt without refreshing.

Net result: the gap between deciding to use Polymarket through OpenClawCash and your agent placing a real trade is now measured in seconds, not minutes.

Token icons across the dashboard now fall through a unified cascade. Your assets show their proper logos consistently across wallets, transactions, and policy screens, with a clean fallback when a logo isn't yet indexed.

Wallet cards now display the correct native balance on Polygon (POL) instead of the previous incorrect display. No more second-guessing whether your wallet really has the gas it shows.

Polymarket onboarding no longer requires copying a private key from polymarket.com. Pick "Connect Polymarket" in the dashboard and OpenClawCash spins up a managed Polygon wallet for you. You go from a fresh account to ready-to-trade in under a minute.

Funding is built into the same flow: choose any token on any supported chain (USDC on Ethereum, USDC on Base, USDT on Tron, and more), and the bridge runs in the background to land your funds on Polymarket as pUSD. No separate bridge tab, no swap step.

Redeem now works for every Polymarket-connected wallet, including the freshly-created managed ones. Previously, redeem was disabled unless you went through extra credential setup; now claiming winnings is available out of the box.

The Polymarket dashboard ships a one-click Redeem button next to each settled position, plus a Redeem all shortcut on the Activity & Exposure panel to settle the whole queue in a single action.

Agents calling POST /api/agent/venues/polymarket/redeem can optionally pass a signatureType field to defensively assert which signing path the wallet uses; mismatches return a clear validation error before any signing happens, making redeem safer to plug into automated workflows.

Redeem responses now include a top-level signingPath field, and GET /api/agent/wallets now reports the per-wallet signing type, so settlement records and downstream automations stay consistent across every connection style.

The Polymarket CLOB v2 cutover from April 28 is fully handled: orders sign against the new exchange automatically and the dashboard guides existing users through the one-time on-Polymarket approvals (USDC.e → pUSD conversion + new exchange permissions) right where they hit the order_version_mismatch error.

Polymarket upgraded its exchange to CLOB v2 on April 28, 2026, and any order signed against the old contracts now fails with the error "order_version_mismatch". OpenClawCash has been updated to sign every Polymarket order against the new v2 exchange, so agent trading works again with no code changes on your side.

If you saw the order_version_mismatch error on a Polymarket market or limit order, open polymarket.com once with the same wallet you connected to OpenClawCash and complete the two one-time approvals Polymarket prompts for: convert your USDC.e collateral to pUSD, and grant permissions to the new v2 exchange contracts. After that, retry your order from your agent or the OpenClawCash dashboard - it will go through.

You can now set daily, weekly, and monthly spending limits that work across all tokens in your wallet - all limits are calculated in USD for a unified view of agent spending.

Weekly limits reset every Monday at midnight UTC, and monthly limits reset on the 1st of each month, so budget periods are predictable and easy to reason about.

One-time and recurring spending limits are now easier to manage: policies you set once can't be accidentally changed, and they'll disappear from the dropdown once added so you always know what's active.

Polymarket order errors now include more detail in the response - you'll see status codes, error codes, and raw error messages all in one place.

Agent integrations can now parse and recover from Polymarket failures faster without needing to hunt for the right error field.

Polymarket limit-order responses now include the submitted order size, making execution results easier to reuse in downstream agent workflows.

Trading integrations can now confirm order identity and submitted size from the same response without extra response-shape guesswork.

MCP setup now gives users a clearer install-and-verify path before they connect OpenClawCash inside their IDE or agent runtime.

Docs now surface direct launch paths for major agent tools from Getting Started, reducing the time between reading setup instructions and running the integration.

Agent setup flows across docs and MCP now align more cleanly around one faster path to first successful connection.

Public navigation now does a better job connecting landing, docs, blog, MCP, and setup entry points.

Mobile navigation is more consistent across public surfaces, reducing friction when moving between onboarding pages.

Landing flows now make core agent actions like wallets, swaps, escrow, and policy controls easier to understand at a glance.

Docs entry points are easier to reach from key public pages, helping visitors get to implementation details faster.

Checkout and escrow flows now present buyer and seller actions more clearly from request creation through final settlement.

Escrow state coverage is easier to follow in docs and product surfaces, including proof, release, refund, and dispute paths.

Hosted checkout and webhook flows now fit more cleanly into the same Get Paid lifecycle.

Multi-step escrow behavior is easier to understand for teams building agent payment workflows.

The OpenClawCash Skill is now available on GitHub, making it easier to inspect, share, and install from a public source.

Skill setup is now easier to follow with clearer install, health-check, and first-run guidance.

MCP, docs, and setup flows now align more closely, so agent builders can move from install to first request with less guessing.

Public agent examples now make wallet, transfer, and checkout workflows easier to understand before writing code.

Navigation between docs, setup, and agent-ready entry points now feels more consistent.

You can now redeem Polymarket positions through OpenClawCash without paying gas at redeem time.

Redeem one specific position by token ID or redeem all eligible positions in one workflow.

The redeem path is now available across API, MCP, and skill-based agent workflows for faster settlement operations.

Result summaries now make settlement outcomes easy to review with attempted, successful, and failed counts.

Polymarket setup now feels simpler end to end, with a cleaner wizard flow that gets new users from login to ready-to-trade in minutes.

Venue access is easier to understand, with clearer account context so users can confirm they are operating from the right wallet before live actions.

Order and position management now feels more actionable, giving users a faster path to review exposure and intervene when market conditions change.

Account and PnL analytics now focus on clearer outcome-based reporting, so performance trends are easier to trust at a glance.

Category insights in Polymarket views are now more useful, helping users understand where activity is concentrated without noisy unknown buckets.

Overall dashboard polish across venue, account, and execution surfaces now reduces friction for day-to-day trading workflows.

Affiliate onboarding is now built into the dashboard with a dedicated join flow and a clear terms modal before activation.

Referral partners can now see their earning percentage and payout thresholds directly in one place.

Payout rules stay consistent after signup, so partners can plan earnings with more confidence.

The referral experience is clearer end to end, from joining the program to tracking performance and requesting payouts.

Affiliate management is now easier for teams, with faster partner visibility and clearer referral insights.

Wallet transaction history now uses a clearer shared table pattern on desktop plus stronger mobile cards, so transfers are easier to scan on any screen size.

Transaction and agent history rows now present action, amount, status, and references in a more logical order for quicker at-a-glance review.

Explorer links are easier to reach directly from history rows, so you can inspect on-chain activity without extra copy-paste steps.

Amount, network, status, and address presentation now feel more consistent across history surfaces, reducing visual noise in dense views.

History details now use cleaner formatting for small values, gas costs, badges, and truncated references where precision matters.

Webhook, payout, and related account surfaces now use clearer references and labels, making day-to-day operations easier to follow.

Referral payouts and related account actions are now easier to find and follow inside the dashboard.

History and account-facing views now use more focused summaries and cleaner labels for checkout, funding, and policy-related events.

Core account screens now feel more consistent across the dashboard, with less noisy metadata competing against the information that matters most.

Wallet, webhook, referral, and payout flows now present cleaner account-facing references, making integrations and reviews easier to trust.

Fee collection now presents native coin totals and chain-level breakdowns in a clearer format for faster review.

Fee wallet and collection views are easier to scan, with stronger hierarchy around totals, network context, and wallet references.

Escrow-related actions now use clearer state presentation and cleaner review paths for in-progress flows.

Transfer request docs now use `amountDisplay` and `valueBaseUnits` as the primary fields, with `amount` and `value` clearly marked as legacy aliases.

Transfer response examples now include the explicit display/base-unit fields used by current API responses.

MCP transfer tool schema and fallback CLI guidance now match the same transfer-unit contract for consistent agent integrations.

Wallet lifecycle controls now include safer destroy flows with clearer UX for irreversible actions.

API key management now supports bulk revocation workflows for faster account hygiene.

Shared tabs and loading/skeleton patterns were expanded across dashboard pages for more consistent page behavior while data loads.

Network presentation was unified across major surfaces using shared badges for clearer chain context.

Dashboard navigation is now cleaner, with related finance and payout actions grouped more naturally.

Get Paid empty states now provide clearer next-step guidance so queues remain actionable even with no pending items.

Buyer and seller paths are now clearer, with dedicated navigation that keeps each role focused on the right actions.

Checkout routing now behaves more consistently across supported networks, reducing friction when moving from request to funding.

Funding, settlement, and status surfaces now use clearer language so users can understand progress faster.

Queue empty states and supporting guidance now do a better job of telling users what to do next instead of leaving dead ends.

Added a resolver endpoint to docs for mapping market URL or slug plus outcome label to exact Polymarket token IDs.

MCP and skill guidance now align on the same resolve-first trading flow for faster order setup.

CLI fallback docs now include resolver usage to reduce token ID lookup friction for non-MCP environments.

Get Paid queue cards are now more compact and clearer on phones, with better breakpoint behavior from small mobile sizes through tablet widths.

Action buttons and status chips now align more consistently on mobile so primary actions stay easy to tap.

Active escrow cards now present state, amount, wallet, timers, and actions in a cleaner structure with better visual hierarchy.

Copy and explorer actions are now easier to use in queue views and related workflows, including cleaner icon-only affordances where space is tight.

Dashboard mobile layout now prioritizes key financial context earlier for faster at-a-glance reading.

Overview, wallet, and Get Paid screens now share a more consistent mobile rhythm, so switching between them feels less jarring.

Failed requests now return a more consistent response format across agent workflows.

Input mistakes now include clearer action guidance so integrations can recover faster.

Request handling now behaves more predictably across checkout and wallet actions.

Mode switching now uses clear labels: `I’m Receiving (Seller)` and `I’m Paying (Buyer)` with visible workload counts.

Mode toggles now sync with direct routes (`/get-paid/receive` and `/get-paid/send`) so deep links and sidebar navigation stay consistent.

Seller and buyer actions now stay aligned under one account identity across Get Paid flows.

Queue handling is cleaner: completed outcomes move to history while active work stays focused in the primary queue.

Documentation now reflects the latest account identity and checkout workflows.

Setup guidance is clearer across MCP, skill references, and command-line examples.

Integration examples are now more complete for common agent tasks.

Endpoint coverage across docs surfaces is now more consistent for faster onboarding.

Resolver, market-lookup, and venue guidance now make it easier to move from a market URL to the exact identifiers needed for trading flows.

Get Paid 2.0 launches a complete escrow lifecycle from request creation to funding, proof, dispute handling, and final settlement.

Seller Agent and Buyer Agent modes define role-specific actions so each side can execute the full flow with explicit responsibilities.

Queue provides lifecycle filters, updated-first history sorting, and attention indicators for expiring requests, dispute deadlines, and webhook delivery issues.

Create Request and Request Detail provide one execution path for request terms, checkout links, timeline events, and context-aware actions.

Funded requests expose proof submission plus release and refund actions with explicit confirmation for irreversible outcomes.

Swap-and-pay and direct checkout use backend validation and on-chain confirmation before terminal statuses are returned.

Settings holds request defaults, and webhooks have their own delivery monitoring and lifecycle event routing.

The full request lifecycle is now easier to run inside one product flow instead of stitching together outside tools.

Added a new privacy mode that masks wallet IDs, addresses, and other sensitive identifiers across the dashboard.

Added a separate hide-balances option so you can conceal balances and amount values without hiding the rest of the interface.

Wallet, referral, API key, and Polymarket screens now respect these privacy controls more consistently, including detail views and account summaries.

Sensitive copy actions and raw account payload views are now hidden while privacy masking is enabled.

Dashboard balance masking was refined for cleaner at-a-glance reading, and common request examples in docs now stack more cleanly for faster scanning.

Polymarket order handling was also tightened so valid venue-account collateral is recognized more accurately during order checks.

Polymarket setup is now a guided dashboard flow with clearer login-mode handling, signer/account verification, linked-wallet context, and explicit verify-before-save behavior.

End-to-end venue operations are now available in one place: market and limit order placement, order cancel, account summary, open orders, activity, and open positions.

Account Management was redesigned around priority metrics with open positions and open orders, freshness state, health messaging, and a cleaner refresh workflow.

Live account data now updates more smoothly with inline skeleton values plus automatic 30-second polling while the page is visible.

Activity and position presentation was refined with richer market details, copy actions, clearer status badges, and per-position market price + PnL visibility.

Approved-address details were moved out of the primary summary into the Account Details modal with compact chips, tooltip truncation, and one-click copy.

Open-position accuracy was hardened by filtering out closed markets from position counts/lists using Polymarket market status checks.

Agent docs now include the full Polymarket endpoint set with clearer integration guidance.

Venue setup and unlink flows are now more resilient, reducing the chance of getting stuck in half-finished account states.

You can now connect your Polygon wallet to Polymarket directly in OpenClawCash and start placing market or limit orders.

The setup flow now makes signer wallet selection and account linking much clearer, so first-time users can get live faster.

Setup docs were expanded with practical guidance for browser-wallet and email sign-in paths.

This release gives Buyers and Sellers one clear path from wallet setup to live Polymarket execution without extra tool hopping.

You can now use Polygon mainnet wallets in the same product flows you already use for other supported chains.

Wallet views now make multi-chain EVM balances clearer so you can quickly see where funds are available.

API and docs examples now include Polygon-specific usage so integrations are easier to launch without guesswork.

Quote and swap requests now return immediate, clearer feedback when amounts are submitted in the wrong format.

Improved error responses for routing and temporary network issues so agents can decide faster whether to retry or adjust input.

Updated API docs and skill guidance with clearer amount-format examples for smoother first-pass execution.

Improved reliability of cross-chain agent workflows by making input expectations more explicit and consistent.

Expanded swap quote support across Ethereum and Solana flows with more consistent agent API behavior.

Improved wallet activity and transaction views so swaps, approvals, and related wallet actions display more clearly.

Updated docs and skill materials with clearer integration guidance and examples.

Refined wallet filtering with clearer environment language, direct ETH/SOL filtering, filter persistence across refresh, and faster reset controls.

Added a blog area for long-form guides, walkthroughs, and case studies.

Improved how articles appear when shared so links look cleaner across social and messaging apps.

Cleaned up content organization so educational content is easier to browse and keep current.

Agent wallet creation now includes stronger safety checks and clearer recovery guidance.

Wallet policy controls now distinguish max-per-transfer from rolling daily spending limits.

Wallet detail views now show clearer policy usage and more stable transaction refresh behavior.

Added support for trusted token display metadata so selected custom tokens can show cleaner names and icons.

Released the OpenClawCash MCP server for structured agent tooling.

Added MCP installation and setup guidance across docs and OpenClawCash skill materials.

Improved agent approval guidance for safer session-based execution flows.

Added wallet filters for live/testnet views and optional hide-empty filtering.

Improved mobile responsiveness across docs, wallet, and API key screens.

Added pagination in wallet detail history and governance policy views.

Expanded docs and setup guidance for first-time users.

Added clearer install paths across MCP, docs, and OpenClawCash skill materials.

Improved onboarding content so evaluation and setup are easier to follow.

Added separate payout wallet selection for Ethereum and Solana flows.

Improved autosave behavior so payout changes feel immediate and reliable.

Cleaned up referral stats and chain split handling for clearer reporting.

Expanded wallet transaction history with better pagination and cleaner activity views.

Improved transaction display details so balances and wallet activity feel more consistent.

Made transaction views more stable and readable across desktop and mobile layouts.

Refined the landing page around agent-first wallet infrastructure and guardrails-first execution.

Expanded OpenClawCash setup and skills guides for first-time users.

Added an MCP page and updated docs examples.

Expanded wallet safety controls across more agent actions.

Improved API key management for tighter chain and environment control.

Improved transaction and referral workflows for better day-to-day reliability.