In short
Every reward the Oracle signs is published on Verifiable payouts as an attestation: EIP-712 typed data with its signature. Each payout also carries a verified-account receipt naming the network, the public @handle and how ownership was proven. Anyone can recompute the hash and check the signer in the browser.
On this page
What is published for each payout?
Two signed records:
- The attestation: the typed data the smart contract checks before paying (creator, pool, amount, metrics, a hash of the post), signed by the Oracle and bound to one chain and one pool.
- The verified-account receipt: the social network, the public @handle, the proof method (official sign-in or bio code) and the metrics source, plus the claim’s on-chain
claimIdanddataHash.
The receipt links the payout to a verified account without any change to the smart contract.
How do you verify a payout?
- Open Verifiable payouts or a pool page’s “Payouts to verified accounts”.
- Press Verify on a row: your browser recovers the signer from the signature and checks it is the pool’s Oracle. The check does not trust the site’s own “verified” flag.
- Follow the explorer link (BscScan, or testnet.bscscan.com during the alpha) to the RewardClaimed event, matched by
dataHash. - On the pool contract,
usedClaims(claimId)= true proves this exact claim was paid once.
If any field (creator, amount, dataHash) were altered, the signature would no longer match.
What does a valid receipt prove, and what not?
| Proves | Does not prove |
|---|---|
| The Oracle key signed exactly this payout | That the post’s content matched the brief |
| Which proven account the payout belongs to | That every view was human (that is the fraud checks’ job) |
| That the claim was paid on-chain, once | Anything about posts that were never paid |
Can tools and AI agents verify receipts?
Yes. The public MCP server exposes list_receipts, verify_receipt, list_attestations and verify_attestation. Quest prizes in crypto also come with a receipt, see the verifiable draw.
Key takeaways
- Every Oracle-signed payout is public EIP-712 data with its signature.
- A receipt names the network, @handle and proof method of the account paid.
- Verification runs in your browser against the signature, not against SaTT’s word.
usedClaims(claimId)on the pool contract proves the claim was paid once.
Frequently asked questions
Are creator e-mails or private data in receipts?
No. A receipt contains only the network, the public @handle (as a hash and as text), the proof method, the metrics source and on-chain identifiers.
Do dollar payouts have receipts too?
Receipts are tied to Oracle-signed on-chain claims in the crypto edition. Dollar rewards are credited to the balance and shown in the account’s activity.
What does “Signed by another key than the Oracle” mean?
The signature is valid but its signer is not the pool’s Oracle. Such an attestation would not be accepted by the pool contract.