feat: add extra rpc endpoint #7
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
gh0stdotexe
approved these changes
May 23, 2024
There was a problem hiding this comment.
Looks good, thanks @Juan-LukeKlopper - i know our API/RPC endpoints are not currently active, I've already dm'd @Brendan-Whispernode about this to see what's up.
Will merge for now so you can move on to other things, thanks!
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
hey Ghost! this PR will add the extra RPC endpoint, in my local testing it isn't giving any errors so please take a look at the berachain governance tab, if it loads up more than once I think it is safe to assume it is using both endpoints since the community endpoint runs into the rate limit really fast (one to two governance page loads from what I've seen)