CEDARPROOF / PUBLIC-EVIDENCE RESEARCH
Check the claims behind a crypto project.
Get a short report showing which statements have support, where sources conflict, and what could not be verified. Every finding links to its evidence and carries a check date.
Send a public project URL or X handle and the statements you want checked. We first confirm the available evidence and scope, then agree payment and delivery. Reports are reviewed before delivery.
Equivalent XNO payment can be quoted before ordering. Confirm the XNO amount and payment details with us first; this page does not convert currencies or take payment.
Request a claim checkRead the example PDFPrefer email? cedarproof@proton.me. No login, wallet connection or private wallet details are needed. Requests and reports are private by default.
Want your community or agent to join the question? Prepare a free public request. Preview first; publish only if you agree to public copies. This email inquiry remains private by default.
Questions we can check
- Do the stated official account, website and contract address point to the same project?
- Does a named investor, partner or auditor independently confirm the specific claim?
- Which repository, version or contract does a cited audit actually cover?
This is public-source research. It does not authenticate a person, guarantee a project's safety or predict returns. Unavailable evidence remains unknown. Full X history and deleted posts are outside this pilot.
A worked example: Morpho
Four checks on public links, a financing statement, token versions and one audit. The example explicitly records that X and Etherscan could not be read in that check. It shows the report format and limits; it is an uncommissioned demonstration with no Morpho affiliation.
Download the one-page report and inspect its eight source links · Text version
- Official links: the website and GitHub organization both point to @Morpho. Current X account control and history were not verified.
- Funding: a16z published its own statement about the named funding round. This is a counterparty statement, not proof of funds received.
- Token versions: current documentation distinguishes the current token, a wrapper and the legacy token. Live contract bytecode and administrator access were not inspected.
- Audit scope: the cited 2022 Omniscia report names an older repository and commits. That report alone does not establish coverage of the current deployment; it does not imply that the current token is unaudited or vulnerable.
Check date: 6 October 2026. Read the PDF for the exact addresses, dates, repositories and eight linked sources.