taikoxyz

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.

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.

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.

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".

Use when cutting a versioned raiko2 ZK/runtime source release from this repository, including git tag creation, publishing the runtime image, exporting guest digests, and creating a GitHub Release with release notes and manifest artifacts. TEE provider metadata is a separate optional flow. Use when the workflow must stop before deployment or register-image --apply.

Use when building and publishing a raiko2 runtime image from this repository with just release-image or xtask release-image. Use when Codex must keep the workflow limited to guest ELF refresh, image build/push, digest capture, and optional register-image checks, without any kubectl, GKE, or rollout steps.

Use when integrating a third-party remote proving service such as TDX, SGX, or another TEE-backed provider into raiko2, especially when the provider must implement the raiko2 remote prover protocol, pass black-box conformance, bootstrap or init correctly, and clear API regression on both proposal and aggregate proving.

Use when validating a Shasta proposal locally from a Taiko L2 block height; discovers the proposal tuple, runs preflight, and verifies the generated GuestInput with the native guest launcher.

Use when an operator or admin needs to read service-level usage and revenue metrics from Tack (requests, paid/free counts, revenue by protocol/endpoint, paying-wallet stats, active/created pin bytes). Also covers issuing, listing, and revoking the operator API keys these endpoints require.

Use when an agent or user needs to pin a CID, upload a file, retrieve content, gate retrieval behind a paywall, or manage existing pins on Tack (the IPFS pinning service at tack.inferenceroom.ai). Covers payment, wallet auth, and all user-facing endpoints.

Taiko network reference for AI agents — RPC endpoints, chain IDs, contract addresses, bridging, and Taiko-specific behavior. Use this skill whenever you need to deploy contracts to Taiko, bridge tokens between Ethereum and Taiko, read on-chain state from Taiko, submit transactions to Taiko L2, configure a wallet or dApp for Taiko, look up Taiko contract addresses, or interact with Taiko in any way. Also trigger when the user mentions Taiko, Taiko Alethia, Taiko Hoodi, based rollup development, or asks about EVM chain differences for chain ID 167000 or 167013.

How to make gasless transactions on Taiko using Servo — pay gas in USDC, no ETH needed. Use this skill whenever someone needs to transact on Taiko without ETH, create an ERC-4337 smart account on Taiko, use a paymaster, pay gas fees in USDC or stablecoins, build a UserOperation for Taiko, or integrate with the Servo bundler. Also trigger when building AI agents that need onchain capabilities on Taiko, when the user mentions "Servo", "servo paymaster", "agent-paymaster", gasless transactions on Taiko, or USDC gas payment. Even if the user just says "I need to do something onchain on Taiko" — this skill applies.