← all claims
143_4_0x443cBFF015457107Fe556DFcA8b8684F7Ee3cbC4_25
unknownThe bytes served now do not match the hash committed on chain, so this document cannot be checked against what its author committed to.
We could not look or could not read. This is never an accusation.
what the document says
- declared network
- none stated
- cited transaction
- none stated
- read by mapping
- no mapping reached this document
- evidence pointer
- https://grokandmon.com/mcp/v1
what the chain says
- bytes match the hash
- no. The bytes served now are not the bytes the author committed, so nothing read out of them can be attributed to them
- committed hash
- 0x292d63c68783d69bc2864a94c0f2dd0439302a9ba882adedcd43e7ee722a74ff
- hash we computed
- 0x2f076b62e4f2f71341a111866ef64fe6f8a2a87a61472b0cb1b4a1ab625548bb
- found on chain
- not looked for
- checked at
- 2026-09-19 12:28:16Z
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
- #4
- left by
- 0x443c…cbC4
- score
- 88
- revoked
- no
- tags
- dataFreshness · sensor-polling
- endpoint
- iot-horticulture
- recorded in
- 0x3c838b21…ba3de6a2block 54,021,169
- 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:21Zunknownresolvablethe bytes served now do not match the hash committed on chain, so this document cannot be checked against what its author committed toscheduled
- 2026-09-19 12:28:16Zunknownresolvablethe bytes served now do not match the hash committed on chain, so this document cannot be checked against what its author committed toscheduled
re-derive this
$1 = 143_4_0x443cBFF015457107Fe556DFcA8b8684F7Ee3cbC4_25
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