Requirements
- Target platform
- OpenClaw
- Install method
- Manual import
- Extraction
- Extract archive
- Prerequisites
- OpenClaw
- Primary doc
- SKILL.md
Use when you need to query Etherscan API V2 for onchain activity, contract metadata, ABI/source retrieval, proxy implementation discovery, and transaction/lo...
Use when you need to query Etherscan API V2 for onchain activity, contract metadata, ABI/source retrieval, proxy implementation discovery, and transaction/lo...
Hand the extracted package to your coding agent with a concrete install brief instead of figuring it out manually.
I downloaded a skill package from Yavira. Read SKILL.md from the extracted folder and install it by following the included instructions. Tell me what you changed and call out any manual steps you could not complete.
I downloaded an updated skill package from Yavira. Read SKILL.md from the extracted folder, compare it with my current installation, and upgrade it while preserving any custom configuration unless the package docs explicitly say otherwise. Summarize what changed and any follow-up checks I should run.
Use this skill to fetch onchain data from Etherscan-compatible explorers using the unified V2 API. Core model: One base URL: https://api.etherscan.io/v2/api One API key Switch chains via chainid Explorer URLs relevant to this workspace: Ethereum mainnet: https://etherscan.io/ Ethereum hoodi: https://hoodi.etherscan.io/ Taiko mainnet: https://taikoscan.io/ Taiko hoodi: https://hoodi.taikoscan.io/ Read first: references/network-map.md references/endpoint-cheatsheet.md references/rate-limits.md references/explorer-url-patterns.md
Collect these before querying: ETHERSCAN_API_KEY Target chainid Address / tx hash / block range Endpoint intent (activity, logs, source, ABI, status)
Pick chainid from references/network-map.md. Choose endpoint by intent from references/endpoint-cheatsheet.md. Build request on https://api.etherscan.io/v2/api with required params. Parse status, message, result. If contract endpoint returns proxy metadata (Proxy == "1"), follow Implementation. For large history, paginate (page, offset) and/or narrow block ranges.
GoalModule / ActionAddress normal tx historyaccount / txlistAddress internal tx historyaccount / txlistinternalERC20 transfer historyaccount / tokentxEvent logslogs / getLogsContract ABIcontract / getabiContract source + proxy fieldscontract / getsourcecodeContract deployer + creation txcontract / getcontractcreationTx execution statustransaction / getstatusTx receipt statustransaction / gettxreceiptstatus
Set key once: export ETHERSCAN_API_KEY="<your_key>" Get ABI (Taiko mainnet example): curl -s "https://api.etherscan.io/v2/api?chainid=167000&module=contract&action=getabi&address=<contract>&apikey=$ETHERSCAN_API_KEY" Get source + proxy metadata (Taiko hoodi example): curl -s "https://api.etherscan.io/v2/api?chainid=167013&module=contract&action=getsourcecode&address=<contract>&apikey=$ETHERSCAN_API_KEY" Get address activity in block window: curl -s "https://api.etherscan.io/v2/api?chainid=1&module=account&action=txlist&address=<address>&startblock=<from>&endblock=<to>&page=1&offset=100&sort=desc&apikey=$ETHERSCAN_API_KEY" Get logs for a contract in block window: curl -s "https://api.etherscan.io/v2/api?chainid=560048&module=logs&action=getLogs&address=<contract>&fromBlock=<from>&toBlock=<to>&page=1&offset=1000&apikey=$ETHERSCAN_API_KEY"
When getsourcecode returns: Proxy: "1" non-empty Implementation then: Keep runtime call target as proxy address. Fetch ABI/source from implementation address. Decode selectors against implementation ABI. Re-check implementation before privileged write analysis.
Never skip these checks: Always set correct chainid; wrong chain silently yields wrong context. Respect plan limits and add client-side throttling/retries. Treat status: "0" as non-success even with HTTP 200. For analytics windows, lock startblock/endblock explicitly. For logs, remember offset max is 1000 per query and paginate. Keep retries idempotent and resume scans from stored cursors/block checkpoints.
Return: exact URL/query used (without exposing secret key) chain (chainid + explorer) endpoint (module/action) parsed status/result summary proxy follow-up decisions (Proxy, Implementation) when contract-related
Code helpers, APIs, CLIs, browser automation, testing, and developer operations.
Largest current source with strong distribution and engagement signals.