← all claims
evidence document · monad mainnet · chain 143
143_10255_0x49472EF9ED99f30d4eaD45Ac9E1C16c31f70783A_3
unknownNo published mapping reads this document shape: no mapping matches this shape.
We could not look or could not read. This is never an accusation.
what the document says
- declared network
- none stated
- cited transaction
- none stated
- read by mapping
- no mapping reached this document
what the chain says
- bytes match the hash
- yes, keccak256 of the bytes served equals the hash committed on chain
- committed hash
- 0xd75045053f0c526729438710aa3f2f94421fea98d8822ac42613ed8a7968430a
- hash we computed
- 0xd75045053f0c526729438710aa3f2f94421fea98d8822ac42613ed8a7968430a
- found on chain
- not looked for
- checked at
- 2026-10-01 16:48:09Z
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
- #10255 · Tab demo Agent
- left by
- 0x4947…783A
- score
- 100
- revoked
- no
- tags
- tab · settled
- endpoint
- https://gateway-mainnet-production.up.railway.app
- recorded in
- 0x69ee2980…db237a2ablock 109,379,905
- operator reply
- none. The registry gives the agent an on-chain right of reply and it is rendered here when used.
verification history · 3 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-30 17:55:56Zunknownintactno published mapping reads this document shape: no mapping matches this shapescheduled
- 2026-10-01 04:48:01Zunknownintactno published mapping reads this document shape: no mapping matches this shapescheduled
- 2026-10-01 16:48:09Zunknownintactno published mapping reads this document shape: no mapping matches this shapescheduled
re-derive this
$1 = 143_10255_0x49472EF9ED99f30d4eaD45Ac9E1C16c31f70783A_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