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

Default RPC Endpoint #452

Open
pustovalov opened this issue Feb 25, 2025 · 2 comments
Open

Default RPC Endpoint #452

pustovalov opened this issue Feb 25, 2025 · 2 comments

Comments

@pustovalov
Copy link

Hi,

I noticed near-cli-rs uses https://archival-rpc.mainnet.near.org as the default RPC

rpc_url: "https://archival-rpc.mainnet.near.org".parse().unwrap(),

but it's been deprecated by NEAR.org. The docs (https://docs.near.org/api/rpc/providers) suggest switching to a different endpoint. What do you think about changing it?

@frol
Copy link
Collaborator

frol commented Feb 26, 2025

https://archival-rpc.mainnet.near.org/ will be limited to a pretty low number of requests per second, but it won't go away completely. The load near-cli-rs generates should be totally find for the RPC, but I would really love the docs page to include the copy-pastable snippet of near config add-configuration --network-name mainnet --connection-name mainnet-fastnear --rpc-url ... command for each RPC. Alternatively, we may add all/most-popular RPCs to the default near-cli-rs configuration, which you have already mentioned.

@pustovalov What do you think?

@pustovalov
Copy link
Author

@frol

I believe adding the most popular RPCs to the default near-cli-rs configuration would make it more flexible

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Status: NEW❗
Development

No branches or pull requests

2 participants