← all claims
143_7_0xAd7757D4505F8302E7B6d4Be43E56b34Bdb431cf_3
no claimConversation rating, no payment asserted, so there is no payment claim to check.
The document read fine and asserts no payment, so there is nothing to be right or wrong about.
what the document says
- declared network
- none stated
- cited transaction
- none stated
- read by mapping
- conversation-score.v1
- evidence pointer
- data: URI, decoded in process with no network call
data:application/json,{"score":100,"conversation_success":true,"responseTime":6563,"conversationLogId":"abe0375f-e868-4a24-b78a-f2f8ea817237"}
what the chain says
- bytes match the hash
- yes, keccak256 of the bytes served equals the hash committed on chain
- committed hash
- 0x84b88fe77cb5ad6328d2b96d96bb7626a8cb9e87230b8d05ef095069b2d9449f
- hash we computed
- 0x84b88fe77cb5ad6328d2b96d96bb7626a8cb9e87230b8d05ef095069b2d9449f
- found on chain
- not looked for
- checked at
- 2026-09-19 12:28:16Z
A verdict is a measurement at a time, so both the wall clock and the block are recorded. Without the block, "not found" is unfalsifiable: a reader cannot tell whether we looked before the transaction existed.
the feedback itself
As the Reputation Registry recorded it.
- about agent
- #7
- left by
- 0xAd77…31cf
- score
- 100
- revoked
- no
- tags
- conversation_success · transparent
- endpoint
- none
- recorded in
- 0xfb711358…31f81d90block 54,734,655
- operator reply
- none. The registry gives the agent an on-chain right of reply and it is rendered here when used.
verification history · 2 checks
Append only. A re-check writes a new row and never edits an old one, so a document somebody repairs reads as a change with both timestamps rather than as a number quietly improving.
- 2026-09-19 11:47:22Zno claimparsedconversation rating, no payment asserted, so there is no payment claim to checkscheduled
- 2026-09-19 12:28:16Zno claimparsedconversation rating, no payment asserted, so there is no payment claim to checkscheduled
re-derive this
$1 = 143_7_0xAd7757D4505F8302E7B6d4Be43E56b34Bdb431cf_3
SELECT id, rung, outcome, reason, checked_at, checked_at_block, automatic,
mapping, found_chain, found_block
FROM fovea.verdict
WHERE feedback_id = $1
ORDER BY checked_at ASC, id ASC