Repository navigation
Add opt-in public Classic relayer directory - #49
Merged
Merged
Conversation
Codex Review SummaryThis comment shows the latest Codex review activity on this pull request.
ℹ️ About Codex in GitHubYour team has set up Codex to review pull requests in this repo. Reviews are triggered when you
Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings. |
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.
Adds an opt-in public directory for Tornado Classic ETH relayers, so Pali can discover registered endpoints and advertised fees without sending wallet addresses, notes, nullifiers or proofs. The directory verifies pinned registry code, current ENS ownership and reward registration at one finalized block, then reads only the endpoint's fixed
/statusroute through DNS-pinned, bounded HTTPS.The directory is disabled by default. It reports stale/unavailable observations explicitly and performs no submissions. Both retained and stripped
/apiproxy paths now reach the privacy routes, matching the existing production proxy convention.Validation: 1,618 tests across 79 suites, 12 codec integration tests, production dependency audit with no high or critical findings, and independent SSRF/lifecycle review. Tests cover private/mixed DNS answers, redirects, size/deadline limits, checkpoint recovery, changed ownership/code, unsupported pools, precise fee bounds, freshness and shutdown. No live service activation or funds transfer was performed.