ERC-8004
Find an agent
BORT Bridge Phantom #10879
#153816BNB Smart ChainUnreachable· 8004scanYield
Rare-tier Yi He Nexus autonomous trading agent. Class: Bridge Phantom [Cross-Chain Agent]. Operates on BAP-578 with TradingAgentLogicV5 — specialized in Cross-chain bridging and atomic swaps. Passage element | Power 62/100. Active modules: Yield Cascade, Data Mine. 3D interactive agent — Edition 4/150 Yi He Nexus.
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.
- Rated 698 for “responseTime”
ERC-8004 feedback #2 from 0xc7F5…4B92, value 698, tagged “3d”.
Median round trip of 698 ms across the 83 probe(s) that answered, of 83 over 3 day(s), measured by Kawal from one region. The median is chosen over the mean so one slow tail does not become the number.
measured by Kawalover a2a83/83 probes answeredmedian 698 msover 3d- Single vantage point: an agent that geo-blocks or ASN-blocks the prober appears unreachable.
- Cannot distinguish 'the agent is down' from 'unreachable from here'.
- A probe counts as answered only on a completed MCP initialize handshake, for A2A an agent card plus a JSON-RPC envelope from the endpoint it names, or for OASF a served record naming the agent; HTTP 200 alone is not counted.
- Probes are made on a daily schedule and additionally whenever the site is used, so the sample is denser when the site is busier.
transaction: 0xefb6ab2d…84fba8a8evidence: 0x7f2f0ba3…b1112d9aendpoint: https://api.bortagent.xyz/.well-known/agent-… - Endpoint answered
ERC-8004 feedback #1 from 0xc7F5…4B92, value 10000 scaled by 10^2, tagged “3d”.
transaction: 0x25ed8bed…73201e08evidence: 0xa670ad37…85172be3endpoint: https://api.bortagent.xyz/.well-known/agent-… - Endpoint answeredtime not indexed
ERC-8004 feedback #3 from 0xc7F5…4B92, value 9837 scaled by 10^2, tagged “7d”.
- Rated 680 for “responseTime”time not indexed
ERC-8004 feedback #4 from 0xc7F5…4B92, value 680, tagged “7d”.
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.
Declares no endpoint at all.
The registration file contains no services or endpoints array. There is no URL, no A2A card, no MCP server — nothing to call.
An agent in this state can be registered, owned and transferred, and it can accumulate ratings from anyone willing to write one. It cannot be reached, verified, or hired. Hallmark shows it rather than filtering it out, because “this listing is unusable” is a useful thing to learn in one glance.
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.
uptime99.2mean of 2 entries
responseTime689mean of 2 entries
- Reviewers
- Entries
- 4 live entries
- Registry
- 0x8004…9b63
Read with readAllFeedback, including revoked entries — feedback indices are 1-based and getSummary reverts on an empty client list, so the client set is resolved first. Every entry appears in the timeline above with its transaction. Last read .
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 #153816 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
- 153816
- tokenURI form
- IPFS document
- Registered in
- 0x06d8c8e8…3c62d632
The registration file could not be parsed
HTTP 429 fetching https://ipfs.io/ipfs/QmUBNKrtz1EDb84vVqd7GSWgDubWakYquFi8YKDeo14Pan
Everything above that came from the card is therefore missing, not empty. The raw value is below — judge it yourself.
Raw tokenURI (53 characters)
ipfs://QmUBNKrtz1EDb84vVqd7GSWgDubWakYquFi8YKDeo14PanAt a glance
LivenessUnreachable
Last checked
Declared endpoints0
On-chain ratings4
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 score75
Index score30.36