kanmani
← all claims

evidence document · monad mainnet · chain 143

143_10315_0x77a55a4980769F543Ea5Bb799F4f49A8c1Cd0D85_1

unknown

Evidence document could not be read: HTTP 404.

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://agenttrace-mainnet.vercel.app/outcomes/0x30985cb60afd8d37b5edfad48312f32ecffa3e34366d31b7f9ec94ef574a9552

what the chain says

bytes match the hash
not checked
committed hash
0xed3bfb0af95e3c5de0e31280ab980ceb30ead6a464284ca09f821b4528646068
found on chain
not looked for
checked at
2026-11-06 18:38:09Z

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
#10315
left by
0x77a5…0D85
score
100
revoked
no
tags
agenttrace-outcome · 0x30985cb60afd8d37b5edfad48312f32ecffa3e34366d31b7f9ec94ef574a9552
endpoint
none
recorded in
0x8d0e94ff…7930dd11block 111,383,405
operator reply
none. The registry gives the agent an on-chain right of reply and it is rendered here when used.

verification history · 66 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-10-07 17:51:59Zunknownresolvablethe 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-10-08 12:04:13Zunknownresolvablethe 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-09 00:04:14Zunknownresolvablethe 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-09 12:04:20Zunknownresolvablethe 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-10 00:04:39Zunknownresolvablethe 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-10 12:05:33Zunknownresolvablethe 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-11 00:06:24Zunknownresolvablethe 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-11 12:06:32Zunknownresolvablethe 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-12 00:06:44Zunknownresolvablethe 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-12 12:07:05Zunknownresolvablethe 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-13 00:07:23Zunknownresolvablethe 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-13 12:08:04Zunknownresolvablethe 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-14 00:08:14Zunknownresolvablethe 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-14 12:08:15Zunknownresolvablethe 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-15 00:09:18Zunknownresolvablethe 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-15 12:10:19Zunknownresolvablethe 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-16 00:10:31Zunknowndeclaredevidence document could not be read: HTTP 404scheduled
  18. 2026-10-16 12:11:20Zunknowndeclaredevidence document could not be read: HTTP 404scheduled
  19. 2026-10-17 00:11:17Zunknownintactno published mapping reads this document shape: no mapping matches this shapescheduled
  20. 2026-10-17 06:11:58Zunknowndeclaredevidence document could not be read: HTTP 404scheduled
  21. 2026-10-17 12:13:35Zunknowndeclaredevidence document could not be read: HTTP 404scheduled
  22. 2026-10-18 00:13:39Zunknowndeclaredevidence document could not be read: HTTP 404scheduled
  23. 2026-10-18 12:13:44Zunknowndeclaredevidence document could not be read: HTTP 404scheduled
  24. 2026-10-19 00:14:23Zunknowndeclaredevidence document could not be read: HTTP 404scheduled
  25. 2026-10-19 12:14:17Zunknowndeclaredevidence document could not be read: HTTP 404scheduled
  26. 2026-10-20 00:14:59Zunknowndeclaredevidence document could not be read: HTTP 404scheduled
  27. 2026-10-20 06:15:36Zunknownintactno published mapping reads this document shape: no mapping matches this shapescheduled
  28. 2026-10-20 18:15:40Zunknowndeclaredevidence document could not be read: HTTP 404scheduled
  29. 2026-10-21 06:15:49Zunknowndeclaredevidence document could not be read: HTTP 404scheduled
  30. 2026-10-21 18:16:20Zunknowndeclaredevidence document could not be read: HTTP 404scheduled
  31. 2026-10-22 06:16:23Zunknowndeclaredevidence document could not be read: HTTP 404scheduled
  32. 2026-10-22 12:18:08Zunknowndeclaredevidence document could not be read: HTTP 404scheduled
  33. 2026-10-23 00:18:46Zunknowndeclaredevidence document could not be read: HTTP 404scheduled
  34. 2026-10-23 12:19:11Zunknowndeclaredevidence document could not be read: HTTP 404scheduled
  35. 2026-10-24 00:19:36Zunknowndeclaredevidence document could not be read: HTTP 404scheduled
  36. 2026-10-24 12:20:35Zunknowndeclaredevidence document could not be read: HTTP 404scheduled
  37. 2026-10-25 00:20:35Zunknowndeclaredevidence document could not be read: HTTP 404scheduled
  38. 2026-10-25 12:20:40Zunknowndeclaredevidence document could not be read: HTTP 404scheduled
  39. 2026-10-25 18:21:30Zunknowndeclaredevidence document could not be read: HTTP 404scheduled
  40. 2026-10-26 06:22:25Zunknowndeclaredevidence document could not be read: HTTP 404scheduled
  41. 2026-10-26 18:22:32Zunknowndeclaredevidence document could not be read: HTTP 404scheduled
  42. 2026-10-27 06:23:08Zunknowndeclaredevidence document could not be read: HTTP 404scheduled
  43. 2026-10-27 18:23:15Zunknowndeclaredevidence document could not be read: HTTP 404scheduled
  44. 2026-10-28 00:24:16Zunknowndeclaredevidence document could not be read: HTTP 404scheduled
  45. 2026-10-28 12:25:01Zunknowndeclaredevidence document could not be read: HTTP 404scheduled
  46. 2026-10-29 00:25:13Zunknowndeclaredevidence document could not be read: timed out after 8000msscheduled
  47. 2026-10-29 12:25:59Zunknowndeclaredevidence document could not be read: HTTP 404scheduled
  48. 2026-10-29 18:26:09Zunknowndeclaredevidence document could not be read: HTTP 404scheduled
  49. 2026-10-30 06:26:12Zunknowndeclaredevidence document could not be read: timed out after 8000msscheduled
  50. 2026-10-30 12:28:31Zunknowndeclaredevidence document could not be read: HTTP 404scheduled
  51. 2026-10-31 00:28:51Zunknowndeclaredevidence document could not be read: HTTP 404scheduled
  52. 2026-10-31 12:28:49Zunknowndeclaredevidence document could not be read: HTTP 404scheduled
  53. 2026-11-01 00:29:13Zunknowndeclaredevidence document could not be read: HTTP 404scheduled
  54. 2026-11-01 12:30:04Zunknowndeclaredevidence document could not be read: HTTP 404scheduled
  55. 2026-11-02 00:30:18Zunknowndeclaredevidence document could not be read: HTTP 404scheduled
  56. 2026-11-02 06:31:51Zunknowndeclaredevidence document could not be read: HTTP 404scheduled
  57. 2026-11-02 18:32:06Zunknowndeclaredevidence document could not be read: HTTP 404scheduled
  58. 2026-11-03 06:32:50Zunknowndeclaredevidence document could not be read: HTTP 404scheduled
  59. 2026-11-03 18:33:34Zunknowndeclaredevidence document could not be read: HTTP 404scheduled
  60. 2026-11-04 06:33:57Zunknowndeclaredevidence document could not be read: HTTP 404scheduled
  61. 2026-11-04 18:34:50Zunknowndeclaredevidence document could not be read: HTTP 404scheduled
  62. 2026-11-05 06:34:38Zunknowndeclaredevidence document could not be read: HTTP 404scheduled
  63. 2026-11-05 12:35:54Zunknowndeclaredevidence document could not be read: HTTP 404scheduled
  64. 2026-11-06 00:36:07Zunknowndeclaredevidence document could not be read: HTTP 404scheduled
  65. 2026-11-06 12:36:14Zunknowndeclaredevidence document could not be read: HTTP 404scheduled
  66. 2026-11-06 18:38:09Zunknowndeclaredevidence document could not be read: HTTP 404scheduled
re-derive this

$1 = 143_10315_0x77a55a4980769F543Ea5Bb799F4f49A8c1Cd0D85_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