Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

chore: more specific rpc urls #1945

Merged
merged 3 commits into from
Jan 7, 2025

Conversation

0xRider
Copy link
Contributor

@0xRider 0xRider commented Jan 7, 2025

There are multiple RPC_URL in the environment.

Renaming to the specific chain, ie. SOLANA_RPC_URL and NEAR_RPC_URL follows the existing pattern of TON_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

@shakkernerd shakkernerd merged commit 7e0d7ea into elizaOS:develop Jan 7, 2025
5 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants