← all claims
143_2106_0x103040545AC5031A11E8C03dd11324C7333a13C7_6
trueCited transaction is on Monad at block 56805846.
The cited transaction is on the chain this document names.
what the document says
- declared network
- monad
- cited transaction
- 0xfe1a286c1333378097762f590bcc5f042d9abfb4c233cd5fc4aaac4800303276
- 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
- 0x1a6b8e83b87a37aa6a3c85dd67173867ff3582896b63094489107b6c45ace794
- hash we computed
- 0x1a6b8e83b87a37aa6a3c85dd67173867ff3582896b63094489107b6c45ace794
- found on chain
- Monad (chain 143) at block 56,805,846
- checked at
- 2026-09-19 12:28:19Z · 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:d90e5ad2
- endpoint
- task:d90e5ad2-1640-4fb2-9fc9-76b9d6282819
- recorded in
- 0x6ffb6a32…e460cb6dblock 88,806,591
- 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 56805846scheduled
- 2026-09-19 12:28:19Ztruetruecited transaction is on Monad at block 56805846scheduled
re-derive this
$1 = 143_2106_0x103040545AC5031A11E8C03dd11324C7333a13C7_6
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