Off-chain Adapter
Status: conceptual, last checked 2026-11-02. No supported off-chain adapter exists.
An off-chain adapter would run a signed program through an approved service instead of a smart contract. Examples are provisioning an API key after payment or running a bounded job for an agent. It suits work that a blockchain can’t do or that isn’t worth an on-chain transaction.
How the trust model changes
| Property | On-chain adapter | Off-chain adapter |
|---|---|---|
| Who enforces the rules | Network validators | The service operator |
| Can a third party recheck execution | Yes, from chain data | Only from evidence the service signs |
| Duplicate protection | Partly from the network | Entirely the service’s job |
| What verification can prove | The state transition happened | The operator claims it happened |
The authorization can still be checked independently. The execution generally can’t, unless the action leaves its own external evidence. An off-chain receipt is a signed claim and should be labeled that way.
Requirements
Any off-chain adapter would need to:
- Verify the SPORE and SPAWN commitment before taking any action.
- Separate public read-only services from services holding privileged keys.
- Record an idempotency key durably before starting a side effect.
- Wait for adequate settlement before an irreversible action.
- Sign receipts with a published key, and state which operator produced them.
Cloudflare Workers and similar platforms would be places to run this. They hold no protocol authority.
Explore invoicing: Programmable Invoicing