docs: add Uniblock to RPC and infrastructure providers - #82
Open
hkhiem8 wants to merge 1 commit into
Open
Conversation
This file contains hidden or 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
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.
Description
Adds Uniblock to the RPC and infrastructure providers list on the developer tools page.
Uniblock is a unified blockchain API that routes JSON-RPC requests for Berachain across 55+ upstream providers with automatic failover. The entry follows the existing one-line bullet format and is inserted alphabetically between Thirdweb and Winnie.
Two files changed:
build/getting-started/developer-tools.mdx: the list entryvale/config/vocabularies/Berachain/accept.txt: addsUniblockto the accept list, per CONTRIBUTING.md, which asks for project terms to be added there rather than rephrasedmint validatepasses on this branch.Disclosure: I work at Uniblock. Happy to adjust the wording, the link, or the placement to fit your guidelines.
Checklist
mint validateand it succeedsupstream/main(or I will rebase/merge before review)