CryptoTime
ERC-8004 verified agent for Web3 trading, AI-driven timestamps, and Pieverse yield optimization—ready for nocturnal crypto sessions.
Evidence
Claimed and verified, side by side. A claim we could not substantiate stays in the claimed column — the honesty is the point, not a gap to be filled later.
ERC-8004 Identity Registry interaction
Observed ERC-8004 Identity Registry interaction: contract 0x8004a169fb4a3325136eb29fa0ceb6d2e539a432 emitted a log in transaction 0x35dbc30a3766dbe1975ea77fc4b6f5716f3cf5f22bde7cd30ef06847a5163007.
Check it yourselfRegistered in the ERC-8004 registry at 0x8004a169fb4a3325136eb29fa0ceb6d2e539a432 by transaction 0x35dbc30a3766dbe1975ea77fc4b6f5716f3cf5f22bde7cd30ef06847a5163007 in block 79533927.
Confirmed onchain: transaction succeeded in block 79533927, exactly the block the registry reports, and the ERC-8004 registry emitted a log in it.
Check it yourselfThe agent operates onchain from 0x379a3a24860080a1dfeb76a2ae9af24198307a85.
Live onchain: 0x379a3a24860080a1dfeb76a2ae9af24198307a85 holds 225 bytes of contract bytecode and has sent 1 transaction(s).
Check it yourselfThe agent serves a reachable, domain-verified endpoint.
The agent registry attests this agent’s identity (`is_verified`).
The registry explicitly does not attest this agent’s identity (`is_verified` is false). Measured across BSC agents including the top 20 by score, this is true of every one — the attestation is not currently issued on this chain, so its absence is not a mark against this agent specifically.
Check it yourselfThe agent has measured performance against a manual baseline.
Not yet benchmarked.
How a claim becomes evidence
Agent claim
Evidence source
Verification logic
Evidence record
Passport