feat: add orbitflare to rpc section#1159
Open
0xsouravm wants to merge 2 commits intosolana-foundation:mainfrom
Open
feat: add orbitflare to rpc section#11590xsouravm wants to merge 2 commits intosolana-foundation:mainfrom
0xsouravm wants to merge 2 commits intosolana-foundation:mainfrom
Conversation
|
@0xsouravm is attempting to deploy a commit to the Solana Foundation Team on Vercel. A member of the Team first needs to authorize it. |
GuiBibeau
reviewed
Feb 14, 2026
Contributor
GuiBibeau
left a comment
GuiBibeau
left a comment
There was a problem hiding this comment.
remove the non english changes, we'll generate the translactions from our automated flows
| "description": "RPC requests are an application's gateway to the Solana cluster. The requests are serviced by aptly named RPC Nodes, which are typically dedicated to the task rather than participating in consensus." | ||
| }, | ||
| "content": "# RPC Infrastructure\n\n**Overview:** RPC requests are an application's gateway to the Solana cluster. The requests are serviced by aptly named RPC Nodes, which are typically dedicated to the task rather than participating in consensus. Nevertheless, from an application user's perspective, poor RPC performance is no different from poor cluster performance. To give your users a great experience and show off Solana's speed and low-latency, it is important to have RPC infrastructure that is up to the task.\n\n**Development:** Developers are encouraged to use a local cluster during development, especially in the early stages and for testing. Local clusters are more flexible than the public offerings, granting the freedom to run unoptimized early iterations. The easiest way to run a local cluster is with the [solana-test-validator](https://docs.solana.com/developing/test-validator) binary, included in the Solana CLI Tools suite. Once the application reaches a stable state, deploying on a public cluster becomes more appropriate.\n\nLike all code optimization tasks, when it comes to RPC requests, less is more. Avoid making frequent, repetitive calls for the same data. Avoid building clients that make RPC requests directly. \"Backend-less dApps\" are a myth; you are just pummelling someone else's infrastructure. Cache expensive calls (especially getProgramAccount, getSignaturesForAddress2, and getConfirmedBlock) in an app-optimized way and serve your users from the cache. Taking the time to optimize your code before going live can save you a lot of headaches from poor user experience reports, and can significantly reduce your infrastructure spend.\n\n## Free Services\n\nSeveral providers offer free RPC access to the public Solana clusters. These services are good for real-world testing, early demos, and small, private beta programs. Keep in mind that you get exactly what you are paying for. Free services typically do not autoscale, are rate-limited, offer no SLA, and are not afraid to ban abusers. When an application is ready to be opened to the public, it is time to invest in private RPC access.\n\n**Some free RPC providers:**\n\n**Testnet**\n\n- [https://api.testnet.solana.com](https://api.testnet.solana.com/)\n\n**Devnet**\n\n- [https://api.devnet.solana.com](https://api.devnet.solana.com/)\n- [https://rpc.ankr.com/solana_devnet](https://rpc.ankr.com/solana_devnet)\n- [Helius](https://www.helius.dev/solana-rpc-nodes)\n- [QuickNode](https://www.quicknode.com/chains/sol)\n- [Chainstack](https://chainstack.com/build-better-with-solana/)\n\n**Mainnet-beta**\n\n- [https://api.mainnet-beta.solana.com](https://api.mainnet-beta.solana.com/)\n- [Syndica](https://syndica.io/)\n- [Blockdaemon](https://www.blockdaemon.com/protocols/solana)\n- [https://rpc.ankr.com/solana](https://rpc.ankr.com/solana)\n- [GetBlock](https://getblock.io/nodes/sol/)\n- [Helius](https://www.helius.dev/solana-rpc-nodes)\n- [QuickNode](https://www.quicknode.com/chains/sol)\n- [InstantNodes](https://instantnodes.io/)\n- [Chainstack](https://chainstack.com/build-better-with-solana/)\n\n## Private Services\n\nDue to the variability in RPC requirements between applications, generalized public RPC infrastructure rarely fits the bill. To ensure users get a good experience, public facing applications need to secure their own private RPC access. This will allow you to autoscale based on user demand, relax rate limits according to your application, and have peace of mind that other applications' users won't crowd yours out. Several organizations offer high-availability, on-demand RPC services; see below. If none of the providers are a good fit and you're up to the task of running your own RPC service, please reach out to the Solana Foundation for guidance.\n\n- [QuickNode](https://www.quicknode.com/chains/sol) (shared)\n- [Triton/RPC Pool](https://triton.one/) (shared and dedicated)\n- [Chainflow](https://chainflow.io/contact/) (dedicated)\n- [Chainstack](https://chainstack.com/build-better-with-solana/) (shared and dedicated)\n- [GenesysGo](https://genesysgo.com/) (dedicated)\n- [Figment](https://datahub.figment.io/sign_up?service=solana) (shared)\n- [Foundation Server Program](https://solana.org/delegation-program) - bare metal at a discount to run-your-own\n- [Syndica](https://syndica.io/)\n- [Alchemy](https://www.alchemy.com/solana) (shared)\n- [Blockdaemon](https://blockdaemon.com/marketplace/solana/)\n- [Ankr](https://www.ankr.com/)\n- [GetBlock](https://getblock.io/nodes/sol/)\n- [Helius](https://helius.dev/solana-rpc-nodes)\n- [NOWNodes](https://nownodes.io/nodes/solana-sol) (shared and dedicated)\n- [InstantNodes](https://instantnodes.io/) (hybrids)" | ||
| "content": "# RPC Infrastructure\n\n**Overview:** RPC requests are an application's gateway to the Solana cluster. The requests are serviced by aptly named RPC Nodes, which are typically dedicated to the task rather than participating in consensus. Nevertheless, from an application user's perspective, poor RPC performance is no different from poor cluster performance. To give your users a great experience and show off Solana's speed and low-latency, it is important to have RPC infrastructure that is up to the task.\n\n**Development:** Developers are encouraged to use a local cluster during development, especially in the early stages and for testing. Local clusters are more flexible than the public offerings, granting the freedom to run unoptimized early iterations. The easiest way to run a local cluster is with the [solana-test-validator](https://docs.solana.com/developing/test-validator) binary, included in the Solana CLI Tools suite. Once the application reaches a stable state, deploying on a public cluster becomes more appropriate.\n\nLike all code optimization tasks, when it comes to RPC requests, less is more. Avoid making frequent, repetitive calls for the same data. Avoid building clients that make RPC requests directly. \"Backend-less dApps\" are a myth; you are just pummelling someone else's infrastructure. Cache expensive calls (especially getProgramAccount, getSignaturesForAddress2, and getConfirmedBlock) in an app-optimized way and serve your users from the cache. Taking the time to optimize your code before going live can save you a lot of headaches from poor user experience reports, and can significantly reduce your infrastructure spend.\n\n## Free Services\n\nSeveral providers offer free RPC access to the public Solana clusters. These services are good for real-world testing, early demos, and small, private beta programs. Keep in mind that you get exactly what you are paying for. Free services typically do not autoscale, are rate-limited, offer no SLA, and are not afraid to ban abusers. When an application is ready to be opened to the public, it is time to invest in private RPC access.\n\n**Some free RPC providers:**\n\n**Testnet**\n\n- [https://api.testnet.solana.com](https://api.testnet.solana.com/)\n\n**Devnet**\n\n- [https://api.devnet.solana.com](https://api.devnet.solana.com/)\n- [https://rpc.ankr.com/solana_devnet](https://rpc.ankr.com/solana_devnet)\n- [Helius](https://www.helius.dev/solana-rpc-nodes)\n- [OrbitFlare](https://orbitflare.com/)\n- [QuickNode](https://www.quicknode.com/chains/sol)\n- [Chainstack](https://chainstack.com/build-better-with-solana/)\n\n**Mainnet-beta**\n\n- [https://api.mainnet-beta.solana.com](https://api.mainnet-beta.solana.com/)\n- [Syndica](https://syndica.io/)\n- [Blockdaemon](https://www.blockdaemon.com/protocols/solana)\n- [https://rpc.ankr.com/solana](https://rpc.ankr.com/solana)\n- [GetBlock](https://getblock.io/nodes/sol/)\n- [Helius](https://www.helius.dev/solana-rpc-nodes)\n- [OrbitFlare](https://orbitflare.com/)\n- [QuickNode](https://www.quicknode.com/chains/sol)\n- [InstantNodes](https://instantnodes.io/)\n- [Chainstack](https://chainstack.com/build-better-with-solana/)\n\n## Private Services\n\nDue to the variability in RPC requirements between applications, generalized public RPC infrastructure rarely fits the bill. To ensure users get a good experience, public facing applications need to secure their own private RPC access. This will allow you to autoscale based on user demand, relax rate limits according to your application, and have peace of mind that other applications' users won't crowd yours out. Several organizations offer high-availability, on-demand RPC services; see below. If none of the providers are a good fit and you're up to the task of running your own RPC service, please reach out to the Solana Foundation for guidance.\n\n- [QuickNode](https://www.quicknode.com/chains/sol) (shared)\n- [Triton/RPC Pool](https://triton.one/) (shared and dedicated)\n- [Chainflow](https://chainflow.io/contact/) (dedicated)\n- [Chainstack](https://chainstack.com/build-better-with-solana/) (shared and dedicated)\n- [GenesysGo](https://genesysgo.com/) (dedicated)\n- [Figment](https://datahub.figment.io/sign_up?service=solana) (shared)\n- [Foundation Server Program](https://solana.org/delegation-program) - bare metal at a discount to run-your-own\n- [Syndica](https://syndica.io/)\n- [Alchemy](https://www.alchemy.com/solana) (shared)\n- [Blockdaemon](https://blockdaemon.com/marketplace/solana/)\n- [Ankr](https://www.ankr.com/)\n- [GetBlock](https://getblock.io/nodes/sol/)\n- [Helius](https://helius.dev/solana-rpc-nodes)\n- [OrbitFlare](https://orbitflare.com/) (shared and dedicated)\n- [NOWNodes](https://nownodes.io/nodes/solana-sol) (shared and dedicated)\n- [InstantNodes](https://instantnodes.io/) (hybrids)" |
Contributor
There was a problem hiding this comment.
please only set it in the english file. The other files are automatically generated from translation systems.
Contributor
|
Content looking good. Asking @h4rkl for a review as i don't know the process to add new providers to that list |
GuiBibeau
approved these changes
Feb 14, 2026
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
2 participants
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.
Summary of Changes
Added OrbitFlare service to the RPC section of solana.com