Add Azul RPC for Base (chainId 8453)#2800
Open
RusseII wants to merge 1 commit into
Open
Conversation
This was referenced May 30, 2026
Add Azul to Base section (provider + public endpoint)
arddluma/awesome-list-rpc-nodes-providers#1467
Open
|
hey @RusseII, would love to have you submit Azul RPC to RouteMesh's RPC directory. you can do so directly here: https://routeme.sh/add-chain-node |
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.
Link the service provider's website (the company/protocol/individual providing the RPC):
https://baseazul.dev
Provide a link to your privacy policy:
https://baseazul.dev/privacy
If the RPC has none of the above and you still think it should be added, please explain why:
N/A
Adding Azul — a free, no-signup public RPC for Base mainnet (chainId 8453).
https://rpc.baseazul.devnone(no IP logs, no request bodies, no wallet correlation, no cookies, no third-party trackers on the RPC path)Access-Control-Allow-Origin: *mainnet.base.orgverified at submission time (delta 0 blocks)Two-line diff: privacy statement added to
privacyStatement, RPC entry appended at the end of the8453.rpcsarray per the template.