-
Notifications
You must be signed in to change notification settings - Fork 1.2k
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
[safesnap] - Point to chainid.org than adding new network from safesnap #3059
Comments
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
keep this |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
Hey @ChaituVR , what's the situation here? |
@ChaituVR could you shed some light? |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
We decided to keep the rpc for safesnap networks and remove others |
Continued from #2819
As suggested by @mktcode better to point users to chainid.org than to maintain the RPC nodes from our side
(we are depricating RPC nodes from snapshot.js package snapshot-labs/snapshot.js#657)
The text was updated successfully, but these errors were encountered: