← all claims
143_10169_0x103040545AC5031A11E8C03dd11324C7333a13C7_1
trueCited transaction is on Monad at block 97452789.
The cited transaction is on the chain this document names.
what the document says
- declared network
- monad
- cited transaction
- 0xba0f1146d798b81f3ba73db6b1e763b34d91ae500dad6164af1f66f483f0a015
- read by mapping
- execution-market.v1
what the chain says
- bytes match the hash
- yes, keccak256 of the bytes served equals the hash committed on chain
- committed hash
- 0x4cf76ebf0236ae9edd4085660dea0313536e7e45926e98f2db2d8192188f2e60
- hash we computed
- 0x4cf76ebf0236ae9edd4085660dea0313536e7e45926e98f2db2d8192188f2e60
- found on chain
- Monad (chain 143) at block 97,452,789
- checked at
- 2026-09-19 12:28:25Z · block 106,177,107
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
- #10169
- left by
- 0x1030…13C7
- score
- 78
- revoked
- no
- tags
- agent_rating:knowledge_access · task:ba56b89f
- endpoint
- task:ba56b89f-e8b7-4ca1-9272-4f27815647fc
- recorded in
- 0xd8f8e2ed…21eecab3block 97,453,094
- 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:30Ztruetruecited transaction is on Monad at block 97452789scheduled
- 2026-09-19 12:28:25Ztruetruecited transaction is on Monad at block 97452789scheduled
re-derive this
$1 = 143_10169_0x103040545AC5031A11E8C03dd11324C7333a13C7_1
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