← all claims
143_2106_0x103040545AC5031A11E8C03dd11324C7333a13C7_10
trueCited transaction is on Monad at block 56696863.
The cited transaction is on the chain this document names.
what the document says
- declared network
- monad
- cited transaction
- 0x00700af53410089ead5953f581a60ee825b2e4ad95062db52486ccd3fbcdc7fa
- 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
- 0x2dd2073ac978b03b02b7c7931fb702e0bb68da8dede410bfe1d73974e0501ffb
- hash we computed
- 0x2dd2073ac978b03b02b7c7931fb702e0bb68da8dede410bfe1d73974e0501ffb
- found on chain
- Monad (chain 143) at block 56,696,863
- checked at
- 2026-09-19 12:28:21Z · 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:1b7e2b51
- endpoint
- task:1b7e2b51-b7dd-4db7-85c3-693ecd3fffb7
- recorded in
- 0x1297acf9…c5f8f549block 88,807,749
- 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:26Ztruetruecited transaction is on Monad at block 56696863scheduled
- 2026-09-19 12:28:21Ztruetruecited transaction is on Monad at block 56696863scheduled
re-derive this
$1 = 143_2106_0x103040545AC5031A11E8C03dd11324C7333a13C7_10
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