Openclast 钱包:为 AI 代理提供的安全区块链交易 - Openclaw 技能
作者:互联网
2026-04-03
什么是 Openclast 钱包代理技能?
Openclast 钱包技能为 AI 代理安全处理区块链操作提供了一个强大的框架。它与 Openclaw 技能集成,旨在促进跨多个网络(包括 Ethereum、Base 和 Polygon)的安全钱包设置、实时余额查询和交易管理。通过强制执行审批流程并利用操作系统级钥匙串安全机制,它确保代理能够在不泄露私钥或违反安全最佳实践的情况下与去中心化协议进行交互。
下载入口:https://github.com/openclaw/skills/tree/main/skills/fabriziogianni7/openclast-wallet
安装与下载
1. ClawHub CLI
从源直接安装技能的最快方式。
npx clawhub@latest install openclast-wallet
2. 手动安装
将技能文件夹复制到以下位置之一
全局模式~/.openclaw/skills/
工作区
/skills/
优先级:工作区 > 本地 > 内置
3. 提示词安装
将此提示词复制到 OpenClaw 即可自动安装。
请帮我使用 Clawhub 安装 openclast-wallet。如果尚未安装 Clawhub,请先安装(npm i -g clawhub)。
Openclast 钱包代理技能 应用场景
- 为 AI 代理工作流设置本地钱包配置。
- 在多个 EVM 兼容链上查询代币余额和交易状态。
- 执行安全的 ERC20 转账和合约交互,且必须经过用户确认。
- 自动化支出限制并将交互限制在已验证的合约地址。
- 使用 CLI 初始化钱包环境以生成配置文件。
- 将用户请求(例如“Sepolia 上的余额”)映射到特定的链 ID 和接收者地址。
- 为任何发送或合约调用操作创建待处理交易状态。
- 在广播之前,通过配置的通知渠道请求用户明确批准。
- 执行交易并在确认后提供区块浏览器链接。
Openclast 钱包代理技能 配置指南
要开始使用此技能,请在项目中安装它并初始化配置:
openclast-wallet install-skill
openclast-wallet setup
您也可以从现有配置文件初始化:
openclast-wallet setup --config ./wallet-config.json
Openclast 钱包代理技能 数据架构与分类体系
该技能使用 wallet-config.json 文件管理操作参数,同时将敏感密钥保存在系统钥匙串中以确保最大安全性。
| 键 | 描述 |
|---|---|
wallets.defaults.spending.mode |
定义交易模式是“notify”(通知,默认)还是“auto”(自动)。 |
wallets.defaults.spending.limitPerTx |
单笔交易允许的最大金额。 |
wallets.chains. |
RPC 端点和区块浏览器 URL 的配置。 |
wallets.interactWithUnverifiedContracts |
布尔值,用于限制仅与已验证的合约进行交互。 |
name: openclast-wallet
description: Guides the agent in Openclast/Openclaw wallet usage, approvals, and safety rules. Use when users ask about wallet setup, balances, transactions, approvals, or key export.
Openclast Wallet Agent Guide
Quick start
- Use the CLI to bootstrap:
openclast-wallet setupcreateswallet-config.jsonin the current folder.openclast-wallet setup --config ./wallet-config.jsoninitializes the wallet from that file.
- Prefer
wallet-config.jsonin the project root and customize chains and limits before use. - Keep
wallet-config.jsonseparate fromopenclaw.json(Openclaw config does not accept a top-levelwalletskey).
Approval flow (mandatory)
All send/approve/contract operations create a pending transaction that requires explicit approval. Always:
- Create the pending tx (send/erc20/contract call).
- Ask the user to approve.
- Only after approval, broadcast and confirm.
If the user asks to “just send,” still require approval unless config is explicitly set to auto mode.
Key export warning (mandatory)
Never expose private keys by default. If the user asks for export:
- Require explicit confirmation.
- Warn that key export is dangerous and should be protected.
- Use environment gates if available (e.g.,
MOLTBOT_ALLOW_WALLET_EXPORT=1) and explicit CLI confirmation.
If export is not supported in this host, say so and offer safer alternatives.
Common tasks
Balance and tokens
- Use the correct chainId for the chain the user mentions.
- If a chain is not configured, read-only balance may still be possible via well-known public RPCs.
Sending
- Validate chainId and recipient.
- Respect per-tx and daily limits from config.
- Always provide a block explorer link when a tx is confirmed.
Chain name → chainId
- Ethereum / Mainnet:
1 - Sepolia:
11155111 - Polygon:
137 - Base:
8453 - Arbitrum One:
42161
When the user says “balance on Sepolia” or “send on Ethereum,” always map to a chainId and proceed.
Safety defaults
- Default mode is notify/approval, not auto-send.
- Restrict unverified contracts when possible.
- Store private keys only in OS keychain (macOS) and never in config.
Config rules (apply when present)
wallets.defaults.spending.mode:"notify"(default) or"auto"(sends without approval).wallets.defaults.spending.limitPerTx,dailyLimit,allowedChains,allowedRecipients,notifyChannels: enforced for send/ERC20/contract calls.wallets.notify.primaryChannel: where pending approvals are notified.wallets.interactWithUnverifiedContracts: iffalse, only allowverifiedTokenAddressesandverifiedContractAddresses.
Block explorer links (mandatory)
After approval and broadcast, always include a tx link. Use:
/tx/for transactions/address/for addresses
Base URL comes from wallets.chains. when configured, otherwise fallback well-known explorers.
Agent tool expectations
If host tooling is available, prefer these tools:
wallet_send,wallet_balance,wallet_txStatus,wallet_approvewallet_erc20_approve,wallet_erc20_transfer,wallet_contract_call
If the host provides CLI instead, use the host wallet CLI for create/address/send/approve and recover/import flows.
Files and CLI
- Starter config:
wallet-config.json - Install skill in project:
openclast-wallet install-skill
相关推荐
专题
+ 收藏
+ 收藏
+ 收藏
+ 收藏
+ 收藏
+ 收藏
最新数据
相关文章
Qwen3.6全面评测:从代码生成到多模态识别的实战体验
✨小白极速上手|OpenClaw小龙虾AI智能体 Windows一键搭建指南 含步骤总览+故障速修
不懂技术怎么做网站?三种建站方式客观对比
物理AI与具身智能,让AI走出屏幕,拥抱物理世界
2026年最火开源AI工具OpenClaw:从零部署到第三方API实战配置
AI编程平民化趋势:从昂贵工具到普惠服务的转变
AI 教育平台的核心功能
AI范式迁移,从“数据驱动”到“认知自主”的跨越
AI开发新选择:阿里云百炼多模型自由切换实践分享
Agent 构建变轻、Agent 架构变薄,什么正在变厚?
AI精选
