add Blockdaemon to public RPC providers (#572)

This reverts commit dbe05f3.

docs/reference/rpc.mdx

@@ -112,12 +112,25 @@ Now you can replace `--network standalone` with `--network futurenet` (or whatev
 
 ## Public RPC Providers
 
-These providers host an publicly available RPC endpoint that you can connect to. The following currently support Futurenet (with more to come).
+These providers host a publicly available RPC endpoint that you can connect to. The following currently support Futurenet (with more to come).
+
+### Stellar Development Foundation (SDF)
 
 | Provider                      | Endpoint                            | Friendbot                                 |
 | :---------------------------- | ----------------------------------- | ----------------------------------------- |
 | [SDF](http://www.stellar.org) | `https://rpc-futurenet.stellar.org` | `https://friendbot-futurenet.stellar.org` |
 
+### Blockdaemon
+
+You can signup to join the waitlist for Blockdaemon's RPC endpoint on Mainnet.
+
+Provider: [Blockdaemon](https://www.blockdaemon.com/apply/soroban)
+
+Blockdaemon offers access to an institutional-grade RPC endpoint that supports Soroban's Testnet. As one of the largest independent blockchain infrastructure providers, Blockdaemon provides institutional-grade
+SLAs, 99.9% uptime, 24/7 support, and decentralized data centers with SOC2-compliance.
+
+You can apply to receive a 1-month free “Starter” tier, and up to five months at the reduced price.
+
 ## Deploy your own RPC instance
 
 If your target deployment environment includes Kubernetes infrastructure, you can utilize [soroban rpc helm chart](https://github.com/stellar/helm-charts/blob/main/charts/soroban-rpc) for an automated deployment on the cluster. Install the [Helm cli tool](https://helm.sh/docs/intro/install/), minimum of version 3 if you haven't already on your workstation. Next, add the Stellar repo to the helm client's list of repos, update it to the latest published versions: