taikoxyz/taiko-shadow
skills/taiko-shadow/SKILL.md
Use when performing private or anonymous ETH transfers on Taiko. Covers deposit creation, target address funding, ZK proof generation, and on-chain claiming via REST API or CLI.
$ install --global
skillsauthnpx skillsauth add taikoxyz/taiko-ai taiko-shadowInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
Security Scan Results
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
3
Scanners Passed
9
Scanners in report
Clean
TrivyContainer and dependency vulnerability scanner
95%
Clean
SemgrepStatic code analysis for vulnerabilities
95%
Clean
mcp-scan (Snyk)Model Context Protocol security validation
95%
Skipped
Snyk (dep)Open source security scanning
50%
Skipped
Socket.devSupply chain security analysis
50%
Skipped
VirusTotalMulti-engine malware detection
50%
Skipped
CrowdStrikeAdvanced threat intelligence
50%
Skipped
OSV-ScannerOpen Source Vulnerability database check
50%
Skipped
OWASP Dep-Check
50%
Last scanned: Apr 15, 2026, 3:06 AM141.8s5 files scanned
SKILL.md
- name:
- taiko-shadow
- description:
- Use when performing private or anonymous ETH transfers on Taiko. Covers deposit creation, target address funding, ZK proof generation, and on-chain claiming via REST API or CLI.
Shadow — Private ETH Transfer on Taiko
Shadow is a privacy-preserving ETH claim system on Taiko L2. An agent deposits ETH to a deterministically-derived "target address" on L1 Ethereum, then claims on Taiko L2 using a ZK proof — without linking depositor and recipient.
Network Selection: If the user has not specified "hoodi" or "mainnet", always ask which network to use before proceeding.
No pool required. Unlike mixers, Shadow uses ZK proofs per deposit — a single user can privately transfer ETH without waiting for others to participate.
Lifecycle
Create deposit → Fund target address (L1) → Generate ZK proof → Claim on L2
Constraints: 1–5 notes per deposit, total ≤ 8 ETH, 0.1% protocol fee per claim.
Quick Decision
| Situation | Use |
|-----------|-----|
| Default / automated pipeline | Server (REST API) |
| No Docker server available | CLI (shadowcli.mjs) |
| Scripted proving only | start.sh --prove FILE (see server reference) |
References
- Server & REST API — start.sh flags, 4-stage workflow, full API table
- CLI — shadowcli.mjs subcommands, mine-deposit flags
- Deposit Schema — v2 JSON schema, derivation formulas
- Contracts — deployed addresses, circuit ID, cast queries
Common Errors
| Error | Fix |
|-------|-----|
| insufficient balance: X < Y | Fund target on L1, wait for checkpoint, retry |
| nullifier already consumed | Note already claimed — skip, check others |
| Please install docker first | Start Docker daemon |
| RPC chainId mismatch | Use L1 RPC matching deposit's chainId |
| DEPOSIT schema validation failed | See deposit schema |
| Server not responding | Re-run start.sh |
MCP Tools for Lifecycle Verification
| Step | Tool | Purpose |
|------|------|---------|
| Before deposit | get_balance | Verify source address has enough ETH on L1 |
| After funding | get_transaction_info | Confirm L1 funding tx is confirmed |
| During prove | get_bridge_message_status | Track cross-chain relay status |
| Before new deposit | get_pending_messages | Check for stuck prior deposits |
| Before claim | get_gas_price | Estimate L2 claim tx cost |
CLI Quick Reference
taiko bridge status <TX_HASH> --json # check bridge relay for L1 funding tx
taiko bridge history <ADDRESS> --json # list all bridge deposits for an address
Deposit Lifecycle Tracking
Use TaskCreate / TaskUpdate to persist deposit_id across session interruptions:
- Create task at deposit creation, include
deposit_idandtargetAddressin description - Update task after each step (fund, prove, claim)
- On resume:
TaskList→ findin_progressshadow deposits → extractdeposit_id
Related Skills
- Network RPC endpoints: taiko/references/networks.md
- Bridge relay context: taiko/references/bridge-interface.md
Security
- Deposit file = secret — never commit or log it; loss = unrecoverable ETH
- The target address has no known private key; ETH can only leave via claim
- Shadow provides privacy but does not guarantee full anonymity
Related Skills
taikoxyz/taiko
development
VerifiedTrustedCommunity
Deploy, test, and interact with smart contracts on Taiko networks (Type-1 ZK-EVM rollup on Ethereum). Use when "Taiko", "Hoodi", "L2 deployment", "bridge", "forge", or "Taikoscan" is mentioned. For x402 payment APIs use the taiko-x402 skill instead.
1SKILL.mdUpdated Apr 15, 2026
taikoxyz/taiko-x402
tools
VerifiedTrustedCommunity
Build and integrate x402 HTTP payment flows on Taiko using Taiko-operated facilitators. Use when adding per-request USDC payment gating to APIs deployed on Taiko (seller), building AI agents or clients that autonomously pay for x402 services (buyer), or configuring Taiko facilitators. Triggers: "x402", "HTTP payment", "pay per request", "monetize API", "USDC payment", "402 Payment Required", "facilitator.taiko.xyz", "paid API", "AI agent payments", "payment middleware".
1SKILL.mdUpdated Apr 15, 2026
taikoxyz/taiko-node
tools
VerifiedTrustedCommunity
Set up, run, and manage Taiko nodes on Hoodi testnet or mainnet using Docker or from source. Use when "run node", "node operator", "simple-taiko-node", "taiko-geth", "taiko-client", or "sync" is mentioned.
1SKILL.mdUpdated Apr 15, 2026
openclaw/taskflow
tools
VerifiedTrustedCommunity
Use when work should span one or more detached tasks but still behave like one job with a single owner context. TaskFlow is the durable flow substrate under authoring layers like Lobster, ACPX, plugins, or plain code. Keep conditional logic in the caller; use TaskFlow for flow identity, child-task linkage, waiting state, revision-checked mutations, and user-facing emergence.
357,764SKILL.mdUpdated Apr 10, 2026