kanmanimonad mainnet · 143
← all claims

143_4_0x443cBFF015457107Fe556DFcA8b8684F7Ee3cbC4_27

unknown

The 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/.well-known/agent-card.json

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
0xb46b58f71b48662a6ed285841392e3b313d374e6e6ee4872bea5f3ab866f19a6
hash we computed
0x46a57747ad99f27bab30cab3beb6884854b3079191715a6b3c05e61bbc042648
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
85
revoked
no
tags
skillReliability · cultivation-alpha
endpoint
a2a-protocol
recorded in
0x0128db46…f4e318d1block 54,021,177
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.

  1. 2026-09-19 11:47:22Zunknownresolvablethe bytes served now do not match the hash committed on chain, so this document cannot be checked against what its author committed toscheduled
  2. 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_27


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