What is Solana deadnet and when should you use it?

Quick recommendation: which Solana cluster should you use?

If you came across the term "deadnet" while searching for Solana development resources, the first thing to know is that deadnet is not an official Solana cluster. It is a community label for a network environment that is no longer maintained, has been shut down, or is simply unreliable for testing. When you need a stable environment for building and testing, you should use Solana devnet or testnet instead.

For most development workflows, Solana devnet is the right choice. It is publicly accessible, has a faucet for free SOL, and is designed for developers to test programs and dApps. If you are stress-testing network upgrades or validator performance, testnet is more appropriate. For production applications, you need mainnet.

To get started quickly, you can use a public RPC endpoint from a provider like OnFinality. For example, the OnFinality public endpoint for Solana mainnet is https://solana.api.onfinality.io/public. For devnet, you can find the endpoint on the Solana Devnet network page.

What does "deadnet" actually mean?

The term "deadnet" is not an official Solana term. It appears in community discussions and sometimes in code comments to describe a network that is no longer operational. This could refer to:

• A deprecated testnet that has been replaced by a newer one.
• A local validator that was shut down.
• A public RPC endpoint that has been discontinued or is no longer maintained.

Because Solana has multiple clusters—mainnet, testnet, and devnet—each with different purposes, confusion can arise when a particular endpoint stops working. Developers might call it "deadnet" when they encounter a non-responsive RPC URL.

Solana clusters at a glance

Solana operates several distinct clusters, each serving a specific role. The table below summarizes the key differences:

Note that public endpoints like api.mainnet.solana.com are rate-limited and may not be suitable for production workloads. For reliable access, consider using a dedicated RPC provider.

Why "deadnet" appears in search results

When you search for "deadnet solana," you might see results about Solana's recovery from the FTX collapse, where some people joked that Solana was "dead." That is a different context. In technical discussions, "deadnet" usually refers to a network that is no longer active.

For example, Solana has had multiple testnets over the years. When a testnet is decommissioned, its endpoints stop working. Developers who try to use those old endpoints might call it "deadnet." This is why it's important to always check the official Solana documentation for the current list of active clusters.

How to connect to a reliable Solana RPC endpoint

To avoid the frustration of a dead endpoint, you should use a reputable RPC provider. OnFinality offers public and dedicated endpoints for Solana mainnet and devnet. Here is an example of how to make a JSON-RPC request to the Solana mainnet endpoint using curl:

curl https://solana.api.onfinality.io/public \
  -X POST \
  -H "Content-Type: application/json" \
  -d '{"jsonrpc":"2.0","id":1,"method":"getHealth"}'

This request checks the health of the node. A successful response will return "result": "ok". If you are developing on devnet, you can use the devnet endpoint from the Solana Devnet network page.

Common pitfalls when using Solana test networks

Even when you use the correct cluster, you may encounter issues. Here are some common pitfalls and how to avoid them:

• Using the wrong cluster ID: Each cluster has a unique genesis hash. Make sure your client is configured for the correct cluster.
• Ignoring rate limits: Public endpoints have rate limits. For heavy testing, consider a dedicated node.
• Not checking the faucet: Devnet requires SOL for transactions. Use the official faucet to get free SOL.
• Assuming testnet is for developers: Testnet is primarily for network stress-testing, not for dApp development. Use devnet for that.

How to choose an RPC provider for Solana

When selecting an RPC provider, consider the following criteria:

OnFinality supports Solana mainnet and devnet, with both HTTP and WebSocket transports. You can compare plans on the RPC pricing page and see the full list of supported networks on the networks page.

Debugging a non-responsive endpoint

If you encounter a "dead" endpoint, here is a systematic way to debug:

1. Check the endpoint URL: Ensure you are using the correct URL for the cluster.
2. Test with curl: Use a simple getHealth request to see if the node responds.
3. Check your network: Firewalls or proxies might block the request.
4. Look for deprecation notices: The Solana docs often announce when a cluster is being decommissioned.
5. Switch providers: If the endpoint is consistently down, try a different provider like OnFinality.

Key Takeaways

• Deadnet is not an official Solana cluster; it's a community term for a non-functional network.
• Use devnet for development and testnet for stress-testing.
• Always verify endpoints against official documentation or a trusted provider.
• Consider a dedicated RPC provider for production workloads to avoid rate limits and downtime.
• OnFinality offers reliable Solana RPC endpoints for both mainnet and devnet.

Frequently Asked Questions

What is Solana deadnet?

Deadnet is an informal term for a Solana network environment that is no longer operational or maintained. It is not an official cluster.

Is deadnet the same as devnet?

No. Devnet is an active test network for developers. Deadnet refers to a deprecated or non-functional network.

How do I get a Solana devnet RPC endpoint?

You can use the public devnet endpoint https://api.devnet.solana.com or a provider endpoint like OnFinality's. See the Solana Devnet network page for details.

Can I use deadnet for production?

No. You should never use a dead or deprecated network for production. Use mainnet for production applications.

Where can I find a list of active Solana clusters?

The official Solana documentation lists current clusters and their endpoints. You can also check the supported networks page on OnFinality.

What should I do if my RPC endpoint stops working?

First, verify the endpoint URL and check for any deprecation notices. If the issue persists, switch to a reliable provider like OnFinality.