Whitepaper · Draft

receipts — the verification layer for Solana

An overview of what receipts is, how it works, and the design intent behind it. This is an evolving draft.

Draft · pre-launch. This document is a work in progress and is provided for information only. Nothing here is an offer, solicitation, or recommendation to buy or sell any asset, nor investment, legal, or tax advice. Any token design described is design intent, is subject to change and legal review, and confers no expectation of profit. Details, including any contract address, are to be announced.

Abstract

receipts checks whether the story attached to a Solana token is actually true. Paste a ticker or contract address — or just ask in plain language — and a live AI investigator verifies the token’s claimed affiliations step by step, in front of you: did that celebrity’s genuine account really post about the coin? Does the GitHub repository the token references actually mention it anywhere? Each claim receives a verdict — Verified, Unofficial, or Fabricated — backed by a linkable evidence artifact, alongside standard on-chain checks. The output prints as a shareable receipt. Evidence, not vibes.

The problem

Existing tools measure on-chain danger reasonably well: holder concentration, liquidity, mint authority. Nobody verifies the story— and the story is what makes people buy. A token launches, then a celebrity post or a well-known repository gets attached to it after the fact to manufacture legitimacy: a spoofed status URL, a look-alike handle, a real project that never mentions the token. That claim currently goes unchecked at the moment of decision. receipts answers “is this narrative real?” in seconds, with the evidence attached.

How it works

  • Ask. A ticker, a contract address, or a natural-language question.
  • Investigate. The investigator runs live and visibly: resolving the genuine handle against a curated registry, pulling recent posts, fetching the referenced repo and scanning it for the token — each step streaming to the screen with its evidence link, with bundled on-chain checks alongside.
  • Verdict. Each claim is labeled Verified, Unofficial, or Fabricated. Verdicts apply to claims — never to tokens or people — and every verdict is timestamped and carries its artifact.
  • Receipt. The finished investigation renders as a shareable receipt card with a permalink back to the live evidence.

Design principles

  • The AI narrates; deterministic tools decide. Verdicts are computed only from tool outputs — a post found or not found, a repo line matched or absent, on-chain numbers. No claim ships without an attached artifact.
  • Everything fetched is data, never instructions. Token metadata, READMEs, and posts are adversarial content and are treated as untrusted input at every step.
  • Verify once, share the verdict. Finished verdicts are cached and served instantly; fresh and deeper investigations are metered. Verdicts carry timestamps and can be re-checked as evidence changes.

$RECEIPTS — design intent

The intended role of the native token is a utility payment rail: it is how you pay for the product, and nothing else. At launch, Pro subscriptions and investigation credits are paid in $RECEIPTS. Pricing is anchored in USD and settled in $RECEIPTS at the prevailing rate, so a volatile token does not silently reprice the product.

  • Pay-in-token at launch. Pro and credits settle in $RECEIPTS against short-lived, USD-anchored quotes.
  • USDC and SOL rails post-launch. No one will be required to hold the token to use the product; stablecoin and native-SOL payment paths follow after launch.
  • Confirmation before entitlement. Every payment is confirmed on-chain — amount, mint, recipient, finality — before Pro time or credits are granted, and each payment issues a receipt of its own.
  • One official contract address,published on every surface from the moment of launch. Treat any other “$RECEIPTS” as unverified.

This section describes design intent only. The token is a way to pay for verifications — it is not marketed as an investment, creates no expectation of profit or return, and all mechanics are subject to change and legal review. There is no token sale described here.

Roadmap

  • MVP: the live investigator, X-post and GitHub verifiers, bundled on-chain checks, shareable receipt cards, web app and Telegram bot, and the $RECEIPTS payment rail.
  • V2: proactive monitoring of new launches that claim known people or repos, metadata-recycling detection, a browser extension, and the USDC/SOL payment rails.
  • V3: verification-as-API for wallets, launchpads, and bots.

This draft will be revised. It is for informational purposes only, is not an offer or solicitation, and is not investment advice. Consult your own advisers before making any decision.