FAQ - SWQoS

Q. How can I use the shared SWQoS endpoint?

To use the shared SWQoS endpoint, you first need to subscribe to one of the ERPC plans: Developer, Business, or Pro.
The available rate is calculated as elSOL holdings ÷ 4.2 TPS, meaning you receive 1 TPS for every 4.2 elSOL you hold.
Example: Holding 10 elSOL grants you 2 TPS.
The more elSOL you hold, the greater your available bandwidth, while also contributing to strengthening ERPC’s overall SWQoS capacity.
The actual TPS you can use will be capped at the lower of either your plan’s maximum TPS or the TPS granted by your elSOL holdings.

Q. How can I apply SWQoS to a dedicated RPC node?

There are two ways to apply SWQoS to a dedicated RPC node:
  • Monthly subscription: Payment in euros (100 EUR per month grants 100 SOL worth of SWQoS)
  • elSOL staking: Staking 1 elSOL applies 1 SOL worth of SWQoS
For more details, please feel free to contact us via our official Discord.

Q. In which regions are your nodes located?

We currently operate nodes for shared endpoints in the following region:
  • Frankfurt (FRA)

Q. My dedicated RPC node transactions are having trouble going through

Transaction success rate and speed are strongly influenced by a mechanism called QoS. We can provide QoS for dedicated nodes. Please see the page below or reach out to us on our official Discord for more information.

Q. What is the latency like?

Latency varies depending on the measurement method and your specific usage environment. Rather than focusing on exact numerical values, it's crucial to ensure that the latency meets your actual operational requirements.
We offer free trials across all our plans, enabling you to test performance directly in your real-world environment. Additionally, we provide easy-to-use tools in TypeScript and Rust for measuring latency. Feel free to utilize these tools alongside your free trial.

Q. Is this RPC (gRPC, Shreds) faster than others?

We encourage you to try our free trial and compare the performance against other services. If you find our service slower, please let us know the specific conditions and competitors you've compared it against via Discord. We will identify the cause and improve the speed further.
We continually work on improving latency based on customer feedback. If you seek the fastest possible endpoint, please share detailed information with us. Providing specific metrics and comparison conditions against competitors allows us to deliver superior performance. This feedback-driven approach has consistently enabled us to enhance our services.

Q. Which plan offers the fastest performance?

Generally, our highest-tier plan provides the fastest performance due to superior CPUs, higher memory capacities, and robust hardware configurations.
We also offer customized solutions if you require even more powerful servers, but our standard plans are designed to deliver optimal price-to-performance ratios.
We are confident in providing world-class performance at every price level. If you find a faster provider within the same price range, please let us know so we can investigate and make improvements.

Q. I'm experiencing high latency. Why?

Latency increases with distance from the endpoint. We recommend accessing from servers close to the provided endpoint. The fastest environments are available through our Bare-Metal servers and VPS services.

Q. Which is the fastest: WebSockets, gRPC, or Shreds?

Customer feedback consistently indicates the following performance order:
Shreds > gRPC > WebSockets
Please let us know if you experience different results.

Q. I need latency of at least ~400ms or better.

To achieve latency within approximately 400ms, consider these essential points:
  • Realistic Understanding of Ping Values: Ping values indicate ideal conditions and do not reflect actual latency in streaming communications, which typically experience around 5 times the ping latency. For example, a ping of 100ms across continents realistically results in about 500ms of latency. Thus, infrastructure must be established within the same region to achieve ~400ms latency.
    • Typical Ping Value Reference:
      • Same network: ~0.1ms
      • Private Network Interconnect (PNI): ~0.2ms
      • Same data center: ~0.3ms
      • Same city: ~1ms
      • Neighboring country: ~5–10ms
      • Intercontinental: ~100–300ms
  • Avoiding the Pitfall of Average Latency: Solana validators are geographically dispersed globally, and the leader schedule changes randomly with each epoch. Relying on average latency to achieve ~400ms is impractical. Instead, you should precisely track validator schedules in your specific region to identify slots with the lowest latency. To consistently achieve minimal latency, infrastructure across all relevant regions is required. Within the same region, data acquisition can occur in tens of milliseconds, with transmission possible in just a few milliseconds.
  • Tracking the Leader Schedule: Continuously monitor the leader validator schedule for your region using the ERPC Leader Slot API (getLeaderSlots).
    It provides real-time data on upcoming leaders, validator geolocations, and reference ping values, allowing you to accurately identify optimal trading slots with minimal latency.
    This eliminates the limitations of public data sources such as Solana Beach or native RPC APIs, which have slower update frequencies and lower precision.
Solana Validators Solana Beach

Q. How can I achieve zero-block (zero-slot) trading?

Successfully achieving zero-block (zero-slot) trading requires more sophisticated strategies, as follows:
  • Identifying Opportunity Zones: Solana validators are distributed globally, and it is physically impossible to achieve optimal latency for every slot. Therefore, monitor validator leader schedules in the region where your infrastructure is located and identify the most favorable opportunity zones. Deploying infrastructure across multiple regions can also be advantageous. For example, Frankfurt is a key region due to its high validator density, resulting in more frequent leader selection and greater trading opportunities.
    Use the ERPC Leader Slot API (getLeaderSlots) to obtain real-time leader schedules, validator geolocation data, and reference ping values with far greater precision than Solana Beach or native RPC APIs. This allows you to predict opportunity zones more accurately and execute near-zero-latency trades.
  • Implementing Dedicated Nodes: If you struggle to compete, consider deploying dedicated nodes. Shared nodes experience latency due to traffic from other users, and thus are not recommended. Furthermore, placing your dedicated node within the same network as your application significantly reduces network latency and optimizes performance.

Q. Latency isn't what I expected.

Performance can vary based on your chosen programming language. Generally, languages perform in the following order:
Rust > Go > TypeScript (JavaScript) > Python
For more detailed comparisons, refer to this resource:
We strongly recommend using Rust if you're aiming for maximum performance.

Q. Why are dedicated endpoints faster?

Shared endpoints are used by multiple customers who share the same resources. As traffic increases, latency tends to occur. Server resources have physical limits, and the amount of work they can handle is finite. When too many requests arrive at the same time, they must be processed sequentially, which results in slower response times.
Although we take various measures to optimize performance even on shared endpoints, with dedicated endpoints you are the sole user of the resource. This means you are completely unaffected by other users, ensuring consistently stable and fast responses.
In addition, dedicated endpoints provide communication options without TLS, such as HTTP. By skipping the TLS handshake (around 20ms), communication becomes even faster compared to HTTPS.

Q. I want to pay with crypto

ERPC is currently developing “Subscription NFTs.” This mechanism issues subscription rights as NFTs, allowing ownership, transfer, and resale, thereby greatly improving the crypto payment experience. The release is scheduled for the end of 2025. For more details, please see the following link:
However, since development and release will take time, if you want to start paying with crypto right now, we recommend trying services that allow you to use cryptocurrencies as credit card payments:
By using these services, you can immediately start paying with cryptocurrency just like with a regular credit card.