菜单
Decode raw EVM transaction calldata into a human-readable function call. Resolves 4-byte selectors via openchain.xyz and best-effort decodes parameters. Zero dependencies, works from raw hex or a tx hash. Use when an agent needs to understand what an arbitrary `0x…` blob is actually doing.
默认使用会先检查来源的 Prompt；你也可以切换为直接命令，或下载本地副本。
决定是否安装前，请先阅读 SKILL.md，以及 SkillsMP 当前展示的配套文件。
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
直接命令不会经过审查 Prompt；运行前请先检查来源。
npx skills add https://github.com/0xAxiom/axiom-public --skill calldata-decoder命令会保持在同一行。复制前请横向滚动并检查完整内容。
想先保存到本地？可下载 SkillsMP 当前能够提供的文件。
Claim creator LP fees for Net Protocol / Banger memecoins on Robinhood Chain from locked Uniswap V3 position NFTs, then optionally use the claimed WETH to buy back the memecoin. Use when the user says "claim Robinhood fees", "claim Hoodie fees", "claim Netr/Banger LP fees", links a Robinhood Blockscout UNI-V3-POS NFT instance, or asks to buy back a Robinhood memecoin with claimed fees. Do NOT use for Base Clanker fee claims or Uniswap V4 positions.
Launch Net Protocol Netr memecoins on Robinhood Chain. Use when the user says "launch a Robinhood token", "deploy a memecoin through Net Protocol", "create a Netr token on Robinhood", "buy the token after launch", or needs Bankr-backed or private-key-backed deployment to chain 4663. Supports direct NET_PRIVATE_KEY signing, Bankr wallet API signing, encode-only transaction generation, gas bridging through Bankr, and post-launch verification.
Encode EVM function calls and constructor args from signature + values. Zero deps.
基于 SOC 职业分类
正在显示 SKILL.md
| name | calldata-decoder |
| description | Decode raw EVM transaction calldata into a human-readable function call. Resolves 4-byte selectors via openchain.xyz and best-effort decodes parameters. Zero dependencies, works from raw hex or a tx hash. Use when an agent needs to understand what an arbitrary `0x…` blob is actually doing. |
Turn raw EVM transaction input into a function call you can read. Zero deps.
0xa9059cbb….It uses Node 18+'s built-in fetch and the public openchain.xyz signature database.
decode.mjs# Raw calldata:
node decode.mjs 0xa9059cbb000000000000000000000000ab5801a7d398351b8be11c439e05c5b3259aec9b0000000000000000000000000000000000000000000000000de0b6b3a7640000
# From stdin:
cat calldata.hex | node decode.mjs
# Directly from a tx hash on any RPC:
node decode.mjs --tx 0x<hash> --rpc https://mainnet.base.org
# JSON output (machine-readable):
node decode.mjs --json 0xa9059cbb...
Environment variable RPC_URL is honored when --rpc is omitted. Default RPC is Base mainnet.
selector: 0xa9059cbb (64 bytes of params)
transfer(address,uint256)
[0] address = 0xab5801a7d398351b8be11c439e05c5b3259aec9b
[1] uint256 = 1000000000000000000
When multiple signatures share a selector (selector collisions are real), all candidates are listed. The agent picks based on context (the to address, surrounding logs, etc.).
When the selector isn't in the openchain database, the script prints the raw 32-byte parameter words so you still have something to work with.
address, bool, bytes1..32uint8..256, int8..256 (signed values handled with two's complement)string and dynamic bytes (decoded from the tail section)For perfect ABI decoding of complex nested types, hand off to viem/ethers. This skill is the fast 90% case.
0xa9059cbb… is opaque; transfer(0xab…, 1e18) is not. Every agent that touches transactions eventually needs to translate one to the other, and the answer should not require pulling in a 100kB ABI parser.