Ordiscan
WarnAudited by ClawScan on May 10, 2026.
Overview
The skill appears purpose-aligned, but it handles a raw crypto private key and can authorize USDC payments for Bitcoin inscriptions without strong built-in spending or confirmation safeguards.
Install only if you are comfortable giving the agent access to a funded Ethereum wallet for USDC payments. Prefer a dedicated low-balance wallet, verify the Ordiscan price and Bitcoin recipient before every paid request, and do not allow inscriptions of content you have not reviewed.
Findings (4)
Artifact-based informational review of SKILL.md, metadata, install specs, static scan signals, and capability signals. ClawScan does not execute the skill or run runtime probes.
If the agent or workflow is misused, the wallet key can authorize real USDC payments; the key may also control more wallet authority than just this Ordiscan use case.
The skill instructs the agent to use a raw Ethereum private key, including extracting it from a local wallet file, so it can sign USDC payment authorizations.
Requires `node` and the `X402_PRIVATE_KEY` environment variable (an Ethereum private key with USDC on Base). If `X402_PRIVATE_KEY` is not already set, check if `~/.evm-wallet.json` exists ... read the private key from it
Use a dedicated low-balance wallet for this skill, set the private key only when needed, and avoid letting the agent read a shared wallet file unless you are comfortable with that access.
A mistaken, unexpected, or malicious payment header could cause the agent to authorize a larger or wrong-recipient USDC payment if the user does not manually review the price and destination.
The helper signs the amount and payee from the caller-supplied Payment-Required header. The code checks balance, but does not enforce a maximum payment amount, Ordiscan resource allowlist, or human confirmation before producing a usable payment signature.
const accept = paymentRequired.accepts?.[0]; ... const amount = BigInt(accept.amount); ... to: accept.payTo, value: amount
Require explicit user confirmation after displaying the price, recipient, and endpoint; add a hard maximum amount for the signing-script path; and validate that payment headers are for the intended Ordiscan API resource.
Wrong content, wrong MIME type, or a wrong recipient address could result in an on-chain inscription that is difficult to undo and may cost funds.
The stated workflow can broadcast Bitcoin inscription transactions based on the agent-prepared content and recipient address.
`POST /v1/inscribe` creates a Bitcoin inscription. The server builds and broadcasts the commit + reveal transactions.
Review the exact content, MIME type, recipient Bitcoin address, fee, and USDC price before allowing the final paid request.
A changed or compromised dependency version could affect wallet-signing behavior during installation.
The local signing helper depends on an npm package using a caret version range, so future installs may resolve to newer versions not represented by the reviewed artifact.
"dependencies": { "viem": "^2.0.0" }Pin dependencies with a lockfile and review installed package versions before using the skill with a funded wallet.