Reading a receipt
What each proof signal means
Comment Protocol keeps six signals separate on purpose. They are not interchangeable, and none of them is a general statement that a person or a comment is trustworthy. Each one below names who asserts it, what it means, and what it does not.
- Site karma
A running count of votes this account's comments received on this site.
Does not mean It is local to this site and is not portable, staked, or verified by anyone outside it.
- Indexed protocol reputation
A discussion-context score computed from indexed protocol activity.
Does not mean It is off-chain until explicitly synced and proven on-chain, so it can be recomputed and is not a settlement record.
- On-chain profile fields
Profile or reputation fields the protocol has actually written on-chain.
Does not mean Only shown when the API returns the on-chain fields. Absent fields mean nothing was written, not that a write failed.
- IPFS content proof
The comment body is content-addressed, so its CID changes if the text changes.
Does not mean A CID is not pinning. `cid` and `pinned` are separate facts, and an unpinned CID may not resolve on a public gateway.
- Solana commitment proof
The comment's leaf is included in a batch committed in a Solana transaction.
Does not mean Commitment is not verification. A committed batch whose proof check has not passed is still pending, and the receipt says so.
- Human verification
A specific external source attested a specific check at a specific time.
Does not mean It is source-specific and expires. Human Passport Stamps are EVM-native, so a Solana author needs a first-party linked-wallet binding before they apply. There is no permanent universal 'human' bit.
Why there is no single verified badge
Collapsing these into one checkmark would be easier to read and would be a lie. A comment can be signature-verified but not yet committed, committed but not yet proof-checked, or content-addressed without being pinned. The receipt on each comment reports the state it can actually observe, which is why it says “Proof checked; commitment pending” rather than rounding up.
Which network these commitments are on
On-chain commitments are made to Solana mainnet-beta. Every explorer link on a receipt points at that cluster, so a signature you open resolves on the same network it was written to.
Checking one yourself
Every identifier on a proof receipt — the content identifier, the batch id, the transaction signature — is copyable, and the ones that resolve publicly are linked. Nothing here asks you to take the product’s word for it.
No signed comment is publicly visible yet, so there is no live receipt to link to right now. The discussions on Discover are labelled application records: they are indexed by this site and carry no signature, content identifier, or commitment. This paragraph is generated from the database, so it will be replaced by a link to a real receipt as soon as one exists.