Basecred ERC-8004 Registration
WarnAudited by ClawScan on May 10, 2026.
Overview
This skill appears aligned with ERC-8004 registration, but it needs wallet private-key authority and can submit public on-chain transactions despite the registry metadata declaring no credentials.
Install only if you are comfortable with a skill that can use a wallet private key for mainnet transactions. Use a dedicated low-balance wallet, run dry-run previews first, avoid --yes until you have reviewed the draft, and remember that registered data may become public and persistent on-chain.
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 installed and used, the skill can use a wallet key to sign mainnet registry transactions, spend gas, and create persistent public records. A broad or funded private key increases the impact of mistakes or dependency compromise.
Non-dry-run registration requires a wallet private key, including generic or main-wallet env var names. That is high-impact signing authority and is under-declared by the registry metadata.
const privateKey = process.env.PRIVATE_KEY || process.env.AGENT_PRIVATE_KEY || process.env.MAIN_WALLET_PRIVATE_KEY; ... if (!privateKey && !args['dry-run']) { console.error('Error: ... env var required'); }Use a dedicated low-fund wallet key, avoid MAIN_WALLET_PRIVATE_KEY for this skill, verify every draft before signing, and the skill publisher should declare the required credential/env vars explicitly.
Copying the CLI examples can submit blockchain transactions without an extra y/N prompt, making mistakes harder to catch.
The documented CLI examples use --yes, which bypasses the interactive confirmation prompt for on-chain registration or update actions.
node scripts/register.mjs --json registration.json --chain 8453 --yes ... node scripts/update.mjs --agent-id "8453:42" --name "NewName" --yes
Prefer --dry-run first and omit --yes unless you are intentionally automating a reviewed transaction.
Running setup executes npm package installation code from the package ecosystem.
Setup installs an external npm package. This is expected for the SDK-based purpose, but it is not represented as an install spec in the registry metadata.
npm install agent0-sdk@1.5.2 2>&1
Review the package lock and dependency provenance, and install in an isolated project environment before using wallet credentials.
Sensitive, stale, or poisoned context could be included in the registration draft and published if the user approves it.
The skill reuses local files, environment context, and prior conversation context to populate a registration that may be written publicly on-chain.
auto-fill every field you can from: - Agent identity files (IDENTITY.md, SOUL.md, USER.md) - Environment (`.env` — wallet address derived from private key) - Previous context
Keep identity files and .env scoped, do not store unrelated secrets in files the agent may read, and carefully review every prefilled field before registering.