56 verdikta

verdikta-bounties-onboarding Skill

Verdikta Bounties 在 Base 上的热钱包操作器。可将 Ethereum 密钥创建/导入加密 keystore(密码永不存储,由 VERDIKTA_WALLET_PASSWORD 通过密钥库或提示提供),保存 API key,上传公开赏金/工作数据,调用经审核的 Verdikta API 和 Base RPC,并在所有者支出策略内签署不可逆的主网/测试网交易。请只用余额较低的新钱包。当所有者在聊天中以如 'Approve <hash prefix>, payout <X> ETH, window <N>h' 的格式批准时,会生成 verdikta-discover 工单草稿:并绑定该确切的 d

安装方式:把技能目录放入 ~/.claude/skills/(Claude Code)或在 claude.ai 设置中启用;也可复制右侧安装命令一键添加。

查看源码

技能指令原文(SKILL.md)

Verdikta authorized bounty execution

For deciding whether to hire a specialist, outsource research, or buy a bounded digital deliverable, use the separate verdikta-discover skill first. It needs no wallet, API key, upload or spend and returns a DRAFT_NOT_QUOTED assessment. This skill is the separately authorized financial path.

Authority and custody

These scripts use an existing encrypted hot wallet and API identity. Keep low balances; never paste a private key, password or API key into model context or logs. Wallet creation/import, bot registration and funding are separate explicitly authorized operations, never prerequisites for discovery. Existing hosted-agent custody/policy arrangements remain separate; do not migrate them to these scripts.

The model expresses intent. Deterministic code validates the exact transaction and enforces limits before signing. --yes or --confirm-spend acknowledges the displayed review; neither bypasses validation. Never pass --yes or --confirm-spend without owner approval of that specific action and its exact terms. These flags acknowledge approval; they do not grant it. Never bypass a failed guard with a manual transaction, alternate RPC/contract, or duplicate bounty. Bounty transactions go only to the reviewed escrow; the one other destination is the owner address recorded at onboarding, for withdrawals.

Onboard an authorized operator

For discovery alone use verdikta-discover. For an owner-approved wallet setup, run node onboard.js interactively from scripts/. The wizard selects Base or Base Sepolia, records the owner's withdrawal address, creates/imports an encrypted low-balance wallet, waits for ETH funding, registers an API identity, and prints the command for a read-only job listing. A human enters secrets in their own terminal, where they are not echoed; never put them in chat or model logs. The skill never stores the wallet password: supply VERDIKTA_WALLET_PASSWORD at run time from a secret store, or point VERDIKTA_WALLET_PASSWORD_FILE at a mode-600 file you keep outside the skill (see wallet password).

For separate steps, environment configuration and endpoint reference, read operator setup. The available helpers are wallet_init.js, funding_instructions.js, funding_check.js, bot_register.js, preflight.js and the read-only bounty_worker_min.js. Wallet creation/import, registration and funding each require owner authorization. Current evaluation fees are ETH; no LINK purchase or swap is needed.

Existing installations must read the 1.6.0 migration notes (the stored password must be moved out of .env; scripts refuse to run until it is) and the 1.5.0 notes before running transaction scripts.

Install and configure commission mode

Copy this complete skill directory from a reviewed repository revision. Work orders also require the sibling verdikta-discover directory and its locked dependencies from the same reviewed revision. That means commissioning a work-order draft (approve_work_order.js, or create_bounty.js with a workOrderDraft) and submitting to a work-order bounty (a description with the Service: