kanmani
← all claims

evidence document · monad mainnet · chain 143

143_4_0x443cBFF015457107Fe556DFcA8b8684F7Ee3cbC4_19

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
0x16febfd639dda35fe7749b3be7d5b4a803d1ed4303405b814e2090ad38e102e2
hash we computed
0x46a57747ad99f27bab30cab3beb6884854b3079191715a6b3c05e61bbc042648
found on chain
not looked for
checked at
2026-11-06 18:37:07Z

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
9500 (2 decimals)
revoked
no
tags
uptime · weekly-avg
endpoint
a2a-protocol
recorded in
0xeb351455…decc7737block 54,019,983
operator reply
none. The registry gives the agent an on-chain right of reply and it is rendered here when used.

verification history · 84 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:21Zunknownresolvablethe 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
  3. 2026-10-01 04:46:50Zunknownresolvablethe bytes served now do not match the hash committed on chain, so this document cannot be checked against what its author committed toscheduled
  4. 2026-10-01 10:46:57Zunknownresolvablethe bytes served now do not match the hash committed on chain, so this document cannot be checked against what its author committed toscheduled
  5. 2026-10-01 16:48:10Zunknownresolvablethe bytes served now do not match the hash committed on chain, so this document cannot be checked against what its author committed toscheduled
  6. 2026-10-02 04:48:18Zunknownresolvablethe bytes served now do not match the hash committed on chain, so this document cannot be checked against what its author committed toscheduled
  7. 2026-10-02 16:48:18Zunknownresolvablethe bytes served now do not match the hash committed on chain, so this document cannot be checked against what its author committed toscheduled
  8. 2026-10-02 22:50:00Zunknownresolvablethe bytes served now do not match the hash committed on chain, so this document cannot be checked against what its author committed toscheduled
  9. 2026-10-03 10:50:16Zunknownresolvablethe bytes served now do not match the hash committed on chain, so this document cannot be checked against what its author committed toscheduled
  10. 2026-10-03 16:51:21Zunknownresolvablethe bytes served now do not match the hash committed on chain, so this document cannot be checked against what its author committed toscheduled
  11. 2026-10-04 04:51:32Zunknownresolvablethe bytes served now do not match the hash committed on chain, so this document cannot be checked against what its author committed toscheduled
  12. 2026-10-04 16:52:18Zunknownresolvablethe bytes served now do not match the hash committed on chain, so this document cannot be checked against what its author committed toscheduled
  13. 2026-10-05 04:52:08Zunknownresolvablethe bytes served now do not match the hash committed on chain, so this document cannot be checked against what its author committed toscheduled
  14. 2026-10-05 10:53:40Zunknownresolvablethe bytes served now do not match the hash committed on chain, so this document cannot be checked against what its author committed toscheduled
  15. 2026-10-05 22:54:07Zunknownresolvablethe bytes served now do not match the hash committed on chain, so this document cannot be checked against what its author committed toscheduled
  16. 2026-10-06 10:55:06Zunknownresolvablethe bytes served now do not match the hash committed on chain, so this document cannot be checked against what its author committed toscheduled
  17. 2026-10-06 22:55:29Zunknownresolvablethe bytes served now do not match the hash committed on chain, so this document cannot be checked against what its author committed toscheduled
  18. 2026-10-07 10:56:01Zunknownresolvablethe bytes served now do not match the hash committed on chain, so this document cannot be checked against what its author committed toscheduled
  19. 2026-10-07 16:57:01Zunknownresolvablethe bytes served now do not match the hash committed on chain, so this document cannot be checked against what its author committed toscheduled
  20. 2026-10-08 12:03:13Zunknownresolvablethe bytes served now do not match the hash committed on chain, so this document cannot be checked against what its author committed toscheduled
  21. 2026-10-09 00:03:12Zunknownresolvablethe bytes served now do not match the hash committed on chain, so this document cannot be checked against what its author committed toscheduled
  22. 2026-10-09 12:03:28Zunknownresolvablethe bytes served now do not match the hash committed on chain, so this document cannot be checked against what its author committed toscheduled
  23. 2026-10-10 00:03:34Zunknownresolvablethe bytes served now do not match the hash committed on chain, so this document cannot be checked against what its author committed toscheduled
  24. 2026-10-10 12:04:31Zunknownresolvablethe bytes served now do not match the hash committed on chain, so this document cannot be checked against what its author committed toscheduled
  25. 2026-10-11 00:05:29Zunknownresolvablethe bytes served now do not match the hash committed on chain, so this document cannot be checked against what its author committed toscheduled
  26. 2026-10-11 12:05:31Zunknownresolvablethe bytes served now do not match the hash committed on chain, so this document cannot be checked against what its author committed toscheduled
  27. 2026-10-12 00:05:32Zunknownresolvablethe bytes served now do not match the hash committed on chain, so this document cannot be checked against what its author committed toscheduled
  28. 2026-10-12 12:06:12Zunknownresolvablethe bytes served now do not match the hash committed on chain, so this document cannot be checked against what its author committed toscheduled
  29. 2026-10-13 00:06:19Zunknownresolvablethe bytes served now do not match the hash committed on chain, so this document cannot be checked against what its author committed toscheduled
  30. 2026-10-13 12:07:15Zunknownresolvablethe bytes served now do not match the hash committed on chain, so this document cannot be checked against what its author committed toscheduled
  31. 2026-10-14 00:07:16Zunknownresolvablethe bytes served now do not match the hash committed on chain, so this document cannot be checked against what its author committed toscheduled
  32. 2026-10-14 06:07:56Zunknownresolvablethe bytes served now do not match the hash committed on chain, so this document cannot be checked against what its author committed toscheduled
  33. 2026-10-14 18:08:19Zunknownresolvablethe bytes served now do not match the hash committed on chain, so this document cannot be checked against what its author committed toscheduled
  34. 2026-10-15 00:10:07Zunknownresolvablethe bytes served now do not match the hash committed on chain, so this document cannot be checked against what its author committed toscheduled
  35. 2026-10-15 12:11:25Zunknownresolvablethe bytes served now do not match the hash committed on chain, so this document cannot be checked against what its author committed toscheduled
  36. 2026-10-16 00:11:24Zunknownresolvablethe bytes served now do not match the hash committed on chain, so this document cannot be checked against what its author committed toscheduled
  37. 2026-10-16 12:12:04Zunknownresolvablethe bytes served now do not match the hash committed on chain, so this document cannot be checked against what its author committed toscheduled
  38. 2026-10-17 00:12:12Zunknownresolvablethe bytes served now do not match the hash committed on chain, so this document cannot be checked against what its author committed toscheduled
  39. 2026-10-17 12:12:29Zunknownresolvablethe bytes served now do not match the hash committed on chain, so this document cannot be checked against what its author committed toscheduled
  40. 2026-10-17 18:13:24Zunknownresolvablethe bytes served now do not match the hash committed on chain, so this document cannot be checked against what its author committed toscheduled
  41. 2026-10-18 06:13:41Zunknownresolvablethe bytes served now do not match the hash committed on chain, so this document cannot be checked against what its author committed toscheduled
  42. 2026-10-18 18:14:13Zunknownresolvablethe bytes served now do not match the hash committed on chain, so this document cannot be checked against what its author committed toscheduled
  43. 2026-10-19 06:14:14Zunknownresolvablethe bytes served now do not match the hash committed on chain, so this document cannot be checked against what its author committed toscheduled
  44. 2026-10-19 18:14:15Zunknownresolvablethe bytes served now do not match the hash committed on chain, so this document cannot be checked against what its author committed toscheduled
  45. 2026-10-20 00:15:43Zunknownresolvablethe bytes served now do not match the hash committed on chain, so this document cannot be checked against what its author committed toscheduled
  46. 2026-10-20 12:15:48Zunknownresolvablethe bytes served now do not match the hash committed on chain, so this document cannot be checked against what its author committed toscheduled
  47. 2026-10-21 00:15:56Zunknownresolvablethe bytes served now do not match the hash committed on chain, so this document cannot be checked against what its author committed toscheduled
  48. 2026-10-21 12:15:48Zunknownresolvablethe bytes served now do not match the hash committed on chain, so this document cannot be checked against what its author committed toscheduled
  49. 2026-10-22 00:16:16Zunknownresolvablethe bytes served now do not match the hash committed on chain, so this document cannot be checked against what its author committed toscheduled
  50. 2026-10-22 12:17:13Zunknownresolvablethe bytes served now do not match the hash committed on chain, so this document cannot be checked against what its author committed toscheduled
  51. 2026-10-23 00:17:40Zunknownresolvablethe bytes served now do not match the hash committed on chain, so this document cannot be checked against what its author committed toscheduled
  52. 2026-10-23 12:18:05Zunknownresolvablethe bytes served now do not match the hash committed on chain, so this document cannot be checked against what its author committed toscheduled
  53. 2026-10-24 00:18:27Zunknownresolvablethe bytes served now do not match the hash committed on chain, so this document cannot be checked against what its author committed toscheduled
  54. 2026-10-24 06:19:06Zunknownresolvablethe bytes served now do not match the hash committed on chain, so this document cannot be checked against what its author committed toscheduled
  55. 2026-10-24 12:21:23Zunknownresolvablethe bytes served now do not match the hash committed on chain, so this document cannot be checked against what its author committed toscheduled
  56. 2026-10-25 00:21:23Zunknownresolvablethe bytes served now do not match the hash committed on chain, so this document cannot be checked against what its author committed toscheduled
  57. 2026-10-25 12:21:29Zunknownresolvablethe bytes served now do not match the hash committed on chain, so this document cannot be checked against what its author committed toscheduled
  58. 2026-10-26 00:21:29Zunknownresolvablethe bytes served now do not match the hash committed on chain, so this document cannot be checked against what its author committed toscheduled
  59. 2026-10-26 06:23:05Zunknownresolvablethe bytes served now do not match the hash committed on chain, so this document cannot be checked against what its author committed toscheduled
  60. 2026-10-26 18:23:23Zunknownresolvablethe bytes served now do not match the hash committed on chain, so this document cannot be checked against what its author committed toscheduled
  61. 2026-10-27 06:23:58Zunknownresolvablethe bytes served now do not match the hash committed on chain, so this document cannot be checked against what its author committed toscheduled
  62. 2026-10-27 18:24:00Zunknownresolvablethe bytes served now do not match the hash committed on chain, so this document cannot be checked against what its author committed toscheduled
  63. 2026-10-28 06:24:19Zunknownresolvablethe bytes served now do not match the hash committed on chain, so this document cannot be checked against what its author committed toscheduled
  64. 2026-10-28 12:25:47Zunknownresolvablethe bytes served now do not match the hash committed on chain, so this document cannot be checked against what its author committed toscheduled
  65. 2026-10-29 00:26:18Zunknownresolvablethe bytes served now do not match the hash committed on chain, so this document cannot be checked against what its author committed toscheduled
  66. 2026-10-29 12:26:53Zunknownresolvablethe bytes served now do not match the hash committed on chain, so this document cannot be checked against what its author committed toscheduled
  67. 2026-10-30 00:26:57Zunknownresolvablethe bytes served now do not match the hash committed on chain, so this document cannot be checked against what its author committed toscheduled
  68. 2026-10-30 12:27:33Zunknownresolvablethe bytes served now do not match the hash committed on chain, so this document cannot be checked against what its author committed toscheduled
  69. 2026-10-31 00:27:45Zunknownresolvablethe bytes served now do not match the hash committed on chain, so this document cannot be checked against what its author committed toscheduled
  70. 2026-10-31 12:27:45Zunknownresolvablethe bytes served now do not match the hash committed on chain, so this document cannot be checked against what its author committed toscheduled
  71. 2026-11-01 00:27:58Zunknownresolvablethe bytes served now do not match the hash committed on chain, so this document cannot be checked against what its author committed toscheduled
  72. 2026-11-01 06:28:34Zunknownresolvablethe bytes served now do not match the hash committed on chain, so this document cannot be checked against what its author committed toscheduled
  73. 2026-11-01 12:30:47Zunknownresolvablethe bytes served now do not match the hash committed on chain, so this document cannot be checked against what its author committed toscheduled
  74. 2026-11-02 00:30:56Zunknownresolvablethe bytes served now do not match the hash committed on chain, so this document cannot be checked against what its author committed toscheduled
  75. 2026-11-02 06:32:33Zunknownresolvablethe bytes served now do not match the hash committed on chain, so this document cannot be checked against what its author committed toscheduled
  76. 2026-11-02 18:32:54Zunknownresolvablethe bytes served now do not match the hash committed on chain, so this document cannot be checked against what its author committed toscheduled
  77. 2026-11-03 06:33:28Zunknownresolvablethe bytes served now do not match the hash committed on chain, so this document cannot be checked against what its author committed toscheduled
  78. 2026-11-03 18:34:21Zunknownresolvablethe bytes served now do not match the hash committed on chain, so this document cannot be checked against what its author committed toscheduled
  79. 2026-11-04 06:34:43Zunknownresolvablethe bytes served now do not match the hash committed on chain, so this document cannot be checked against what its author committed toscheduled
  80. 2026-11-04 18:35:43Zunknownresolvablethe bytes served now do not match the hash committed on chain, so this document cannot be checked against what its author committed toscheduled
  81. 2026-11-05 06:35:22Zunknownresolvablethe bytes served now do not match the hash committed on chain, so this document cannot be checked against what its author committed toscheduled
  82. 2026-11-05 18:35:29Zunknownresolvablethe bytes served now do not match the hash committed on chain, so this document cannot be checked against what its author committed toscheduled
  83. 2026-11-06 06:36:21Zunknownresolvablethe bytes served now do not match the hash committed on chain, so this document cannot be checked against what its author committed toscheduled
  84. 2026-11-06 18:37:07Zunknownresolvablethe 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_19


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