fix: send Photon requests to the Helius RPC root - #2390
Conversation
|
Warning Review limit reachedNext included review available in 59 minutes. View limit detailsLimit details: You’ve used all 2 included reviews currently available. You've used all free OSS reviews for now. Wait for the free limit to reset to keep reviewing this public repository. Review configuration: ⚙️ Run configurationConfiguration used: Path: .coderabbit.yaml Review profile: ASSERTIVE Plan: Advanced Run ID: ⛔ Files ignored due to path filters (3)
📒 Files selected for processing (2)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
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. |
Helius Gatekeeper routes Photon calls through JSON-RPC at the RPC root URL. The Rust client appended method paths such as
/getIndexerHealth, preventing clients from usinghttps://mainnet.helius-rpc.com/?api-key=....Send all Rust
apis::default_apicalls to the configured URL, with the method in the JSON body. Preserve custom endpoint paths, other query parameters, and encoded API keys. The TypeScript client already posts to the root URL; add regression coverage and document mainnet configuration.Validation:
cargo test -p photon-api --locked: 14 tests passed.vitest run tests/unit/rpc/json-rpc-transport.test.ts: 15 tests passed.mainnet.helius-rpc.com/succeeded forgetIndexerSlotandgetCompressedAccount.git diff --checkpassed.