← all claims
143_10248_0xC5ead1E4E5C6d56E87e02317f3fB3731cB0b6Ef7_1
unknownEvidence document could not be read: HTTP 429.
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
what the chain says
- bytes match the hash
- not checked
- committed hash
- 0xce505f2e49653c6e95d0c16d7352347878a1663aca6a6cd85ce369c60ca6f187
- found on chain
- not looked for
- checked at
- 2026-09-19 12:28:42Z
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
- #10248
- left by
- 0xC5ea…6Ef7
- score
- 90
- revoked
- no
- tags
- moolam · verification
- endpoint
- none
- recorded in
- 0x7ced2375…33ae380ablock 102,997,141
- 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:48Zunknowndeclaredevidence document could not be read: HTTP 429scheduled
- 2026-09-19 12:28:42Zunknowndeclaredevidence document could not be read: HTTP 429scheduled
re-derive this
$1 = 143_10248_0xC5ead1E4E5C6d56E87e02317f3fB3731cB0b6Ef7_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