ERPC Implements Keep Warming for Solana SWQoS Endpoints, Improving Initial Send Behavior and Strengthening Transaction Reliability
ERPC Implements Keep Warming for Solana SWQoS Endpoints, Improving Initial Send Behavior and Strengthening Transaction Reliability

ELSOUL LABO B.V. (Headquartered in Amsterdam, the Netherlands) and Validators DAO announce that ERPC has implemented Keep Warming support for its Solana SWQoS endpoints, improving transaction send behavior at the moment of initiation.
This update does not change the existing design or usage of SWQoS endpoints. Instead, it suppresses delays that could occur at the very beginning of transaction submission and improves the conditions under which transactions can enter the send path more quickly at the required moment. For ERPC users, this enhancement strengthens transaction reliability without requiring any changes to daily operations.
ERPC’s distributed systems platform, including this update, is recognized as a research and development project under the Dutch government’s R&D support program (WBSO). This implementation is part of an ongoing R&D process that is directly connected to real-world operations.
Key Points of This Update
ERPC’s SWQoS endpoints have been designed to increase transaction success probability even under network congestion. The Keep Warming implementation does not alter this core design but focuses specifically on improving behavior at the moment transaction sending begins.
By reducing the impact of communication initialization at the time of submission, transactions can enter processing more smoothly from the instant they are sent.
The Role of ERPC’s SWQoS Endpoints
SWQoS functions as stake-based priority control that takes effect at the network acceptance stage before leader execution. During congestion, it stabilizes the fundamental condition of whether a transaction reaches the network at all.
ERPC’s SWQoS endpoints provide this mechanism for real-world operations, functioning as a transmission path that ensures reachability before priority fees are evaluated. Their primary role is to create conditions under which outcomes are less prone to fluctuation during congested periods.
Issues Observed at Transaction Initiation in Real Operations
Even when SWQoS conditions were satisfied, slight delays could occur at the moment transaction sending began, depending on the sender’s environment.
In particular, for usage patterns where transactions are not sent frequently, communication initialization could coincide with the moment of submission. This initial delay was observed to affect outcomes in certain cases. While the transmission path itself remained strong, there was still room for improvement in initiation behavior.
Improvements Achieved Through Keep Warming
With the Keep Warming implementation, connection states can be maintained prior to sending, making it less likely for communication initialization to occur at the exact moment a transaction is submitted.
As a result, when transactions are actually sent, it becomes easier to enter the send process immediately. This update improves only the initial send behavior without changing the design of SWQoS or priority fee mechanisms.
For detailed usage information, please refer to the official documentation below:
https://erpc.global/en/doc/rpc/swqos-endpoint/
Concrete Changes for Users
With Keep Warming in place, use cases where send timing is critical are less affected by delays at initiation. Even when transactions need to be sent at a specific moment, send behavior at the start becomes more stable.
As a result, transactions sent by ERPC users move closer to conditions under which they are more likely to succeed in real-world operations. This improvement is not intended to require constant high-frequency communication, but rather to ensure faster sending when it matters.
Continuity With Previous Infrastructure Enhancements
ERPC’s SWQoS endpoints depend on sufficient and sustained processing capacity on the validator side that receives prioritized traffic.
ELSOUL LABO B.V. and Validators DAO have continuously strengthened the Epics DAO validator, which operates as a core node supporting SWQoS, through upgrades such as EPYC 5th Gen (Turin) CPUs, DDR5 6400MHz memory, and NVMe Gen5 storage. The Keep Warming implementation builds on these infrastructure enhancements as an improvement on the sending path.
Positioning as Research and Development
The ERPC platform is recognized as an R&D project under the Dutch WBSO program. Observed issues in real-world operations are incorporated into research targets, and iterative verification and improvement contribute directly to sustained quality enhancements.
The Keep Warming implementation is based on insights obtained from production environments and was developed within a system where research and operations are not separated.
Future Direction
Currently, SWQoS endpoints are primarily provided over HTTPS. Development is underway to add TPU QUIC options, further strengthening the overall sending path so that outcomes remain stable even during congestion.
Notice to Users
The Keep Warming implementation has been automatically applied to all existing ERPC users. No additional configuration or operational changes are required. For technical details, please refer to the official SWQoS endpoint documentation.
ERPC will continue to incrementally improve conditions under which results are achieved in real operations, enhancing both transmission paths and execution infrastructure. For the latest updates, please refer to the Validators DAO official Discord.
- Validators DAO Official Discord: https://discord.gg/C7ZQSrCkYR
- ERPC Official Website: https://erpc.global/en
- elSOL Official Website: https://elsol.app/en


