# Staked RPC Services

### Background

Stake-weighted QoS (SWQoS) is a feature of Solana that was first released during March 2024. To put it simply, SWQoS allows users to send transactions on Solana and have them get confirmed faster than compared to an RPC not using this feature. This is especially evident in times of bursts of high traffic on the Solana network.

When an RPC attempts to forward a transaction to the leader validator at any given moment, it must compete with other RPC nodes in order to establish a QUIC connection to the leader. A validator leader can only handle a finite amount of QUIC connections at any given time. By default, 80% of the available QUIC connections are reserved for staked nodes. The other 20% is left over for un-staked nodes. Since Solana RPC nodes are inherently not staked (and shouldn't be) you are required to setup a SWQoS connection with a staked validator in order to get around this.

An RPC node with a configured SWQoS connection will forward all transactions sent to it through the staked validator it has the SWQoS connection setup through. The validator then forwards the transaction to the current Solana leader validator in order to get processed and added to the blockchain.

The reason transactions are slow to land many times is because the RPC cannot make a connection to the leader validator at the current moment. This is because the network is busy and it can't handle any more connections. SWQoS gives you a special priority connection to leaders that gets to circumvent all the other network connection which ensures your transaction will get seen by the leader.

SWQoS doesn't put you in the front of the line for priority. It just ensures that your transaction will make it to the leader validator and get a chance in the auction. If you have low fees it will likely still be slow to land or not land at all

### Overview

* Access to all [Solana RPC HTTP and WebSocket methods](https://solana.com/docs/rpc) that are current and stable
* Access to the Jito-Solana `simulateBundle` RPC method
* For Historical queries please reference [our api doc](https://docs.solanavibestation.com/developers/historical/overview)
* 0.1 ms latency from our RPC nodes to our primary staked validator partner
* Over 500,000 SOL in stake weighted peering
* Transactions sent over multiple channels to decrease landing time

## Pricing

<table><thead><tr><th>Tier</th><th width="214">Rate Limit (sendTransaction)</th><th width="225">Rate Limit (All other Methods)</th><th>1 Month</th></tr></thead><tbody><tr><td>Basic</td><td>25 r/s</td><td>150 r/s<br>5 GPA r/s</td><td>$300</td></tr><tr><td>Ultra</td><td>50 r/s</td><td>250 r/s<br>10 GPA r/s</td><td>$500</td></tr><tr><td>Elite</td><td>100 r/s</td><td>500 r/s<br>15 GPA r/s</td><td>$1000</td></tr></tbody></table>

## Benchmarks

<figure><img src="/files/DhyolBCoUo3xfTOdax9v" alt=""><figcaption><p>Staked Send Transaction RPC Service memobench benchmark</p></figcaption></figure>


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.solanavibestation.com/services/solana-node-services/staked-rpc-services.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.