Skip to content

Reclaim proof integration#1

Merged
andreogle merged 4 commits into
mainfrom
feature/reclaim-proof-integration
Apr 6, 2026
Merged

Reclaim proof integration#1
andreogle merged 4 commits into
mainfrom
feature/reclaim-proof-integration

Conversation

@andreogle

Copy link
Copy Markdown
Owner

No description provided.

When proof mode is enabled (proof: { type: reclaim, gatewayUrl: ... }),
Airnode requests a TLS proof from the ChainAPI proof gateway after each
API call. The proof is attached to the response alongside the existing
EIP-191 signature. Proof failures are non-fatal — the response is still
returned without the proof field.

- Add reclaim proof schema to settings (none | { type: reclaim, gatewayUrl })
- Add src/proof.ts — lightweight HTTP client for the proof gateway
- Thread settings through PipelineDependencies for proof access
- Attach proof to SignedResponseBody and RawResponseBody when available
…eway

The Reclaim attestor requires at least one responseMatch to validate and
extract data from the API response. Added responseMatches as an optional
endpoint-level config field and wired it through to the prove request.
Also fixed the prove URL to include resolved query and path parameters.
- Add TLS proofs concept page (book/docs/concepts/proofs.md)
- Add reclaim-proof example config (examples/configs/reclaim-proof/)
- Fix raw response hash docs: stableStringify, not JSON.stringify
- Fix stale NFT auth references, wrong verifyAndFulfill case, OIS terminology
- Document responseMatches field in endpoint config
- Update settings.md with reclaim proof configuration
- Add proof field to all response format examples
- Update pipeline from 13 to 14 steps (TLS proof step)
- Update roadmap: TLS proofs (Reclaim) now delivered in Phase 4
- Use full gateway URL in proof.ts (no hardcoded path)
- Remove chainapi.com references from test fixtures
@andreogle andreogle self-assigned this Apr 6, 2026
@andreogle
andreogle merged commit 048fb69 into main Apr 6, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant