← all claims
143_2106_0x103040545AC5031A11E8C03dd11324C7333a13C7_8
trueCited transaction is on Monad at block 56876280.
The cited transaction is on the chain this document names.
what the document says
- declared network
- monad
- cited transaction
- 0x96332268675061144b6440d94cc45e726cfb7bbdb2cd6df8624f0cb7a3ba8913
- 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
- 0x3672bf591d0b432787930923fc7260488ac1a431542c78bcfdad3fd83284af25
- hash we computed
- 0x3672bf591d0b432787930923fc7260488ac1a431542c78bcfdad3fd83284af25
- found on chain
- Monad (chain 143) at block 56,876,280
- checked at
- 2026-09-19 12:28:20Z · 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:a911e6b9
- endpoint
- task:a911e6b9-23da-4a20-8483-b84dd7c9b4b0
- recorded in
- 0x4ec5b8c2…b06aa7ecblock 88,807,691
- 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:25Ztruetruecited transaction is on Monad at block 56876280scheduled
- 2026-09-19 12:28:20Ztruetruecited transaction is on Monad at block 56876280scheduled
re-derive this
$1 = 143_2106_0x103040545AC5031A11E8C03dd11324C7333a13C7_8
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