Pass solana_rpc_url explicitly to chain providers#503
Merged
Conversation
LandynDev
force-pushed
the
m3-d8-explicit-rpc
branch
from
5bb846d to
5380193
Compare
LandynDev
force-pushed
the
m3-d8-explicit-rpc
branch
from
69c3547 to
62658f9
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
1 participant
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.
Compute
solana_rpc_urlonce and pass it explicitly into bothcreate_chain_providerscalls so the SOL chain providers (source-leg verification) andsolana_clientshare one rpc-url source of truth instead of an implicitSOLANA_RPC_URLenv fallback. Same URL — no behavior change. Stacks on D4 (retarget tom3after D4 merges).