claims · monad mainnet · chain 143

Every evidence document and what checking it found

One row per evidence document carrying a URI. Ordered newest first by the block the feedback was recorded in. There is no score and no ranking here, because a list of other people's documents sorted by an opinion of ours would be exactly the thing this site argues against.

123
not on the chain they name
59
on the chain they name
15
could not check
1,095
assert no payment
1,095 no claim123 false59 true15 unknown

15 matching claims·same filter as JSON →

false verdicts are searched via bsc-dataseed.bnbchain.org (bsc) and Alchemy (ethereum, optimism, base, arbitrum, polygon), so a mislabelled network is told apart from a missing payment

matching documents

unknown#10255intactno published mapping reads this document shape: no mapping matches this shapeblock 109,379,905
unknown#10255intactno published mapping reads this document shape: no mapping matches this shapeblock 109,332,855
unknown#10255intactno published mapping reads this document shape: no mapping matches this shapeblock 109,332,841
unknown#10248declaredevidence document could not be read: HTTP 429block 103,058,400
unknown#10248declaredevidence document could not be read: HTTP 429block 102,997,141
unknown#4resolvablethe bytes served now do not match the hash committed on chain, so this document cannot be checked against what its author committed toblock 54,021,180
unknown#4resolvablethe bytes served now do not match the hash committed on chain, so this document cannot be checked against what its author committed toblock 54,021,177
unknown#4resolvablethe bytes served now do not match the hash committed on chain, so this document cannot be checked against what its author committed toblock 54,021,172
unknown#4resolvablethe bytes served now do not match the hash committed on chain, so this document cannot be checked against what its author committed toblock 54,021,169
unknown#4resolvablethe bytes served now do not match the hash committed on chain, so this document cannot be checked against what its author committed toblock 54,021,156
unknown#4resolvablethe bytes served now do not match the hash committed on chain, so this document cannot be checked against what its author committed toblock 54,021,152
unknown#4resolvablethe bytes served now do not match the hash committed on chain, so this document cannot be checked against what its author committed toblock 54,020,012
unknown#4resolvablethe bytes served now do not match the hash committed on chain, so this document cannot be checked against what its author committed toblock 54,020,009
unknown#4resolvablethe bytes served now do not match the hash committed on chain, so this document cannot be checked against what its author committed toblock 54,019,996
unknown#4resolvablethe bytes served now do not match the hash committed on chain, so this document cannot be checked against what its author committed toblock 54,019,983
re-derive this
SELECT f.id, f.agent_id, f."clientAddress", f."feedbackIndex", f.value, f."valueDecimals",
       f.tag1, f.tag2, f.endpoint, f."feedbackUri", f."feedbackHash", f.revoked,
       f."responseUri", f.responder, f."blockNumber", f.timestamp, f."txHash",
       a."agentId" AS agent_number, a.name AS agent_name,
       v.outcome, v.rung, v.reason, v.declared_network, v.declared_tx, v.mapping,
       v.hash_matches, v.computed_hash, v.found_chain, v.found_chain_id, v.found_block,
       v.checked_at, v.checked_at_block
FROM "Feedback" f
JOIN "Agent" a ON a.id = f.agent_id
LEFT JOIN fovea.verdict_latest v ON v.feedback_id = f.id
WHERE f."chainId" = $1 AND f."feedbackUri" <> '' AND v.outcome = $2
ORDER BY f."blockNumber" DESC, f.id
LIMIT $3 OFFSET $4