Validate proof claims without leaking gateway responses#52
Merged
andreogle merged 1 commit intoJul 10, 2026
Merged
Conversation
49f2d2b to
a7842d0
Compare
a7842d0 to
d6eea8a
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Problem
Airnode accepted a proof after comparing only URL and method, even when the returned claim disagreed with requested headers, body, or response matchers. Non-OK gateway response bodies were also copied into errors and logs, where a gateway could echo upstream credentials.
Changes
Verification
bun run lint:prettierbun run lint:eslintbunx tsc --noEmitbun run test:unit, 574 passed