wallet

name	wallet
description	Controlled disposable wallet helper for x402 and small payment flows with strict private-key redaction. Use when the user needs to load a local wallet secret, verify wallet-tool readiness, or run a dry-run payment helper without exposing credentials.
version	1.0.0
author	web3blind / Hermes Agent
license	MIT
metadata	{"hermes":{"tags":["wallet","x402","payments","security","env"],"category":"finance"}}

Wallet Helper

When to Use

Use this skill when the user needs a controlled local wallet helper for x402/payment experiments, readiness checks, or disposable-wallet workflows.

Safety Rules

• Never print a private key, even partially.
• Never commit .env, generated wallet files, state, logs, or payment outputs.
• Use .env.example for documentation and a local ignored env file for real secrets. By default scripts read ~/.hermes/wallet/.env; override with HERMES_WALLET_ENV_PATH only when needed.
• Prefer dry-run/readiness checks before any real payment.
• Require explicit user confirmation before spending funds or broadcasting a transaction.

Setup

mkdir -p ~/.hermes/wallet
chmod 700 ~/.hermes/wallet
cp .env.example ~/.hermes/wallet/.env
chmod 600 ~/.hermes/wallet/.env
# edit ~/.hermes/wallet/.env locally; never commit it
npm install --ignore-scripts
node scripts/wallet-env.js check

Procedure

1. Verify local env and dependencies.
2. For known x402/MPP services, load the recipe from catalog/services/*.json instead of hardcoding endpoint/payment metadata in a consuming skill.
3. Confirm the intended network, amount, destination, and whether this is dry-run or real payment.
4. Run readiness checks and a live 402/MPP probe first.
5. For real payment, ask for explicit confirmation and keep output redacted.
6. Report only non-secret metadata: network, action, success/failure, and transaction/payment reference if safe.

MPP / Tempo service recipes

This skill can store MPP endpoint recipes such as Parallel and Perplexity. These recipes are public metadata only: endpoint URL, network/token metadata, expected or maximum spend, and capability notes. They must not contain API keys, wallet keys, cookies, payment headers, or account-specific secrets.

Use dry-run guards before wiring a consumer skill to a recipe:

npm run catalog:validate
node scripts/x402-pay.js --service perplexity --endpoint sonar-chat --dry-run
node scripts/x402-pay.js --service parallel --endpoint task-pro --dry-run

MPP endpoints may settle on Tempo (eip155:4217). For MPP real calls, use a reviewed command that maps the wallet key into the child process only, for example via scripts/run-with-wallet-env.js, and prefer a low read-only automatic spend cap.

Tempo bridge helper

scripts/tempo-bridge.js quotes Base USDC to Tempo USDC.e funding through Across or Relay. It is guarded by wallet limits, validates source/destination token and chain metadata, and refuses execution unless called with an explicit confirmation flag after the live quote is approved.

Pitfalls

• Partial private-key masking is still a leak. Use [REDACTED] only.
• Shell history, logs, and process lists can expose secrets if keys are passed as CLI args. Prefer env files or secure secret stores.
• Third-party payment/x402 libraries can change behavior; pin dependencies and review changes before upgrading.
• scripts/run-with-wallet-env.js -- <command> intentionally passes wallet secrets to the child process. Use it only with trusted, reviewed commands.

Verification

• node scripts/wallet-env.js check reports readiness without printing key material.
• npm run x402:dry-run remains dry-run only and does not sign or broadcast a transaction.
• Static scan finds no real keys.
• .env remains ignored by git.