chore: point mainnet Pyth JSON-RPC default at Triton endpoint - #168
Merged
Conversation
OctoSauce
approved these changes
Jul 25, 2026
rg-alpha
approved these changes
Jul 25, 2026
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
4 participants
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.
Mysten shuts off JSON-RPC on fullnode.mainnet.sui.io on 2026-07-26. The internal Pyth SuiJsonRpcClient for mainnet now uses the Triton endpoint. Testnet/devnet defaults are unchanged.
Note: the Triton endpoint is Origin-gated (403 without an allowed browser Origin), so this works from allowed alphafi/alphalend domains; server-side consumers (e.g. the liquidator) hit 403 on the Pyth path since this URL is not configurable.