RECEIPTS API

Publication policy

What we publish, and on what evidence

RECEIPTS joins public posts to public on-chain transactions. This page states exactly what we will and will not say about a person, what proof each claim rests on, and how to have an entry corrected or removed.

1. What the data is

Two public inputs, joined by us:

  1. Public posts. Messages a person published themselves in a public channel or account. We store the text, timestamp and a link to the original.
  2. Public blockchain transactions. Trades recorded on a public ledger by a wallet address.

The join between the two — that a given wallet belongs to a given person — is not public data. It is an attribution, and it is the part that can be wrong. Everything below follows from that.

2. Attribution tiers

what we may say depends on this
self-verifiedThe person published or cryptographically signed the address themselves. Their own post, or a signed verification on a social protocol. We may state the link plainly.
corroboratedIndependently confirmed: the wallet repeatedly trades what they post, around the moment they post it, and/or two or more independent sources agree. We may state the link, and we show the method.
third-partyA label from someone else, with no confirmation of our own. We may show the address and name the source — we do not publish behavioural findings about the person on this basis.
unverifiedNot published at all. It stays in the pipeline, unlisted.

A behavioural finding — anything about what a person did or did not do relative to what they said — is published only at self-verified or corroborated.

3. How we word findings

We describe what was observed and the limits of the observation. We do not characterise motive, and we do not use language that imputes dishonesty.

we write"No matching on-chain buy was found for the attributed wallet between 14:02 and 14:02 +7d."
we do not write"He never touched the token he shilled."
we write"The attributed wallet already held the token at the time of the post."
we do not write"He front-ran his own audience."

Every published finding shows the wallet used, how it was attributed, the observation window, and links to both the original post and the on-chain record, so a reader can check it without trusting us.

4. What we do not publish

  1. Private individuals. Only people who publish market calls to a public audience.
  2. Identity beyond the wallet link. No legal names, locations, employers, contact details or any other personal information.
  3. Unverified attributions. See tier 3 above.
  4. Advice. Nothing here is a recommendation to buy, sell or hold anything.

5. Right of reply, correction and removal

If you are named here and believe an entry is wrong:

  1. Tell us. Write to receipts@lab.pro with the entry and what is wrong with it.
  2. We answer within 5 working days.
  3. If the wallet is not yours, we remove every finding based on it — we do not require you to prove a negative; a credible objection is enough to unpublish while we re-check.
  4. If the finding is disputed but the attribution stands, we publish your statement next to it, unedited.
  5. Deletion. You may ask us to stop processing your data. We will do so unless we have an overriding legal basis, and we will explain if we cannot.

We would rather be corrected than be confidently wrong in public.

6. If you use the API

  1. You may not present this data as investment advice, a recommendation, or a signal to trade.
  2. Where you display a finding, you display its attribution source and observation window with it.
  3. You may not resell or redistribute the raw dataset without a written agreement.
  4. You handle the personal data in it lawfully in your own jurisdiction, and you honour deletion requests we pass on to you.
  5. Misuse ends the key.