Execution receipts
Receipts create a verifiable trail for skill runs, payments, providers, and output hashes.
Last updated July 2, 2026
Receipt data
Every execution should leave behind enough data to prove what ran without exposing private prompt content or sensitive user input. The current app stores receipts in the database; the production protocol design writes compact receipt proofs to Solana accounts.
| Attribute | Purpose |
|---|---|
| Skill ID | Identifies which skill was run. |
| Executor wallet | Connects the run to the paying public wallet. |
| Fee paid | Supports accounting and revenue distribution. |
| Provider | Shows which LLM route produced the output. |
| Output hash | Verifies the returned result without storing full private output on-chain. |
| Timestamp | Supports audit, analytics, and dispute review. |
Privacy model
Keep receipts compact
Never write private prompts, user secrets, API keys, documents, or full LLM outputs to a public ledger. Store hashes and references only.