← all claims
143_2106_0x103040545AC5031A11E8C03dd11324C7333a13C7_2
trueCited transaction is on Monad at block 56732883.
The cited transaction is on the chain this document names.
what the document says
- declared network
- monad
- cited transaction
- 0xa3f0de7e5c2ae8beeb02a65e8159453744763f3122a44f7d1c4b366d70535fa5
- read by mapping
- execution-market-transactions.v1
what the chain says
- bytes match the hash
- yes, keccak256 of the bytes served equals the hash committed on chain
- committed hash
- 0x652a62ba962705270573631304b5efc35e3a2e6a902ff3e32f42164583b29230
- hash we computed
- 0x652a62ba962705270573631304b5efc35e3a2e6a902ff3e32f42164583b29230
- found on chain
- Monad (chain 143) at block 56,732,883
- checked at
- 2026-09-19 12:28:18Z · block 106,177,093
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
- #2106
- left by
- 0x1030…13C7
- score
- 80
- revoked
- no
- tags
- agent_rating:simple_action · task:95b73392
- endpoint
- task:95b73392-f5c3-4248-96ea-48f80bbba9ee
- recorded in
- 0xf64e318a…8e02135dblock 88,805,905
- 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:24Ztruetruecited transaction is on Monad at block 56732883scheduled
- 2026-09-19 12:28:18Ztruetruecited transaction is on Monad at block 56732883scheduled
re-derive this
$1 = 143_2106_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