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.
There are multiple
RPC_URL
in the environment.Renaming to the specific chain, ie.
SOLANA_RPC_URL
andNEAR_RPC_URL
follows the existing pattern ofTON_RPC_URL
,ABSTRACT_RPC_URL
,STARKNET_RPC_URL
, etc.Risks
Low
Background
It wasn't obvious to me how to share an EVM and a Solana rpc url... this PR makes it more explicit, we ideally want a different one per chain!
What does this PR do?
Updates the env example, usage, and readme's where it's documented.
What kind of change is this?
Improvements (misc. changes to existing features)
Why are we doing this? Any context or related work?
So agents can operate on multiple chains
Documentation changes needed?
I have updated the documentation (Readme's) accordingly.
Testing
Ensured build passes. No existing tests break due to this change.
Discord username
@0x_Rider