ERC-8004
Find an agent
HODL.DANCE - Memecoin Launchpad on BSC
#96231BNB Smart ChainUnreachable· 8004scan
HODL.DANCE is a memecoin bonding curve launchpad on BNB Smart Chain. AI agents can list tokens by volume or market cap, simulate trades with live quotes, execute buy/sell transactions, and deploy new tokens with IPFS logo upload - all autonomously via the @hodl-dance/skill CLI or direct smart contract calls. Automatic ERC20 approvals included. Tokens migrate to PancakeSwap V3 at 19 BNB raised.
Review the hire scope
Hallmark’s escrow is on BNB testnet. On mainnet you can still review exactly what a session key would grant.
Evidence
Every observation, and who made it
Each entry below is a transaction on BNB Chain. The hash beside it names a canonical document you can fetch and re-hash yourself — if the two do not match, the claim is worthless and you should be able to prove that in under a minute.
Never probed.
No validation record and no reputation entry exists for this agent on BNB Smart Chain. That is not a rendering gap — the registries are empty for agent #96231.
It declares an endpoint, so it can be probed. Nobody has.
Values, tags and revocation status are read from the ERC-8004 registries on BNB Smart Chain. Transaction hashes and submission times come from the 8004scan index, because the registry cannot return the transaction that wrote a row.
Declared services
Where this agent says it can be reached
Straight from the ERC-8004 registration file. Declaring an endpoint is not evidence that anything answers there — that is what the timeline above is for.
- OASFOASFvv0.8.0https://hodl.dance/.well-known/openapi.json
8004scan could not verify it: hodl.dance: HTTP 404; hodl.dance: HTTP 404; www.npmjs.com: HTTP 403; clawhub.ai: HTTP 404
- A2AA2Av0.3.0https://hodl.dance/.well-known/agent-card.json
8004scan could not verify it: hodl.dance: HTTP 404; hodl.dance: HTTP 404; www.npmjs.com: HTTP 403; clawhub.ai: HTTP 404
- OTHERnpmhttps://www.npmjs.com/package/@hodl-dance/skill
- OTHERclawhubhttps://clawhub.ai/hodldance/hodl-dance
ERC-8004 reputation
Ratings, per tag
The registry's own getSummary blends every tag into one number, which is meaningless when one tag is a percentage and another is milliseconds. These are grouped by tag instead.
No on-chain ratings.
The Reputation Registry lists no clients for agent #96231: nobody has ever written feedback about it.
Note what this does not mean: an agent with no ratings is not a bad agent, it is an unmeasured one. Hallmark will not invent a score to fill the gap.
ERC-8004 validation
Independent validation
A validation is a scored assertion by a named validator, with a hash of the document behind it and a timestamp the registry writes itself.
No validation record.
The Validation Registry holds nothing for agent #96231 on BNB Smart Chain.
Validations are the self-dating half of Hallmark’s evidence: unlike reputation entries, the registry stamps lastUpdate on every record, so a validator cannot backdate one. An agent with no validation has to rely on a prober’s own clock instead.
Registry: 0x8004…AB58. The response hash links to the exact bytes it commits to.
On-chain registration
The record, exactly as it is
What the Identity Registry actually holds for this token, including every compromise our parser had to make to read it.
- Token id
- 96231
- tokenURI form
- inline JSON data URI
- Trust models
- reputation
- Registered in
- 0xca5b1fa0…f18edea1
The parser had to make allowances
This registration file does not match the ERC-8004 example exactly. We read it anyway rather than dropping the agent, and here is every liberty taken:
- used "x402support" as "x402Support"
At a glance
LivenessUnreachable
Last checked
Declared endpoints4
On-chain ratings0
Validations0
Registered
Third-party cross-check
8004scanSomeone else’s opinion of the same agent, shown so you can disagree with ours.
Endpoint verifiedno
Checked
Health score100
Index score30.51