You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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?
The text was updated successfully, but these errors were encountered:
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.
Hi,
I noticed near-cli-rs uses https://archival-rpc.mainnet.near.org as the default RPC
near-cli-rs/src/config/mod.rs
Line 26 in 511cd61
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?
The text was updated successfully, but these errors were encountered: