← all claims
143_2106_0x103040545AC5031A11E8C03dd11324C7333a13C7_7
trueCited transaction is on Monad at block 56773907.
The cited transaction is on the chain this document names.
what the document says
- declared network
- monad
- cited transaction
- 0xb414eaa62539a19ace0b77bcbecbf7939795ea4d47b692d46eb4c3cc4c1255c3
- 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
- 0xd83866813e4d1dc13f867643e983f1eb3e781fb64ae970e090a1975156a21176
- hash we computed
- 0xd83866813e4d1dc13f867643e983f1eb3e781fb64ae970e090a1975156a21176
- found on chain
- Monad (chain 143) at block 56,773,907
- 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:dc0d00f6
- endpoint
- task:dc0d00f6-6ea9-4d1a-9368-e38c64416562
- recorded in
- 0x5643561d…a8257142block 88,806,979
- 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 56773907scheduled
- 2026-09-19 12:28:20Ztruetruecited transaction is on Monad at block 56773907scheduled
re-derive this
$1 = 143_2106_0x103040545AC5031A11E8C03dd11324C7333a13C7_7
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