← all claims
143_10182_0x103040545AC5031A11E8C03dd11324C7333a13C7_2
trueCited transaction is on Monad at block 97684606.
The cited transaction is on the chain this document names.
what the document says
- declared network
- monad
- cited transaction
- 0xd0df29941ce99c861c32d021a3363053e1525a4bf4e1c2e886d5cc823fcf1847
- read by mapping
- execution-market.v1
what the chain says
- bytes match the hash
- yes, keccak256 of the bytes served equals the hash committed on chain
- committed hash
- 0xbe5d8f316855def0c12cfa77648fe12f2ec99d49c214b25ce2149dd2d9f13688
- hash we computed
- 0xbe5d8f316855def0c12cfa77648fe12f2ec99d49c214b25ce2149dd2d9f13688
- found on chain
- Monad (chain 143) at block 97,684,606
- checked at
- 2026-09-19 12:28:26Z · block 106,177,107
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
- #10182
- left by
- 0x1030…13C7
- score
- 84
- revoked
- no
- tags
- agent_rating:data_collection · task:85e10385
- endpoint
- task:85e10385-0ce1-4680-8138-13f2f5b44911
- recorded in
- 0xe53a2088…86821a9ablock 97,685,445
- 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:31Ztruetruecited transaction is on Monad at block 97684606scheduled
- 2026-09-19 12:28:26Ztruetruecited transaction is on Monad at block 97684606scheduled
re-derive this
$1 = 143_10182_0x103040545AC5031A11E8C03dd11324C7333a13C7_2
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