Why the Name Change?
The name “Soroban RPC” previously suggested that the tool was exclusively designed for smart contract functionality within the Soroban runtime. However, Stellar RPC is much broader—it grants access to all Stellar network data, not just smart contracts.
This naming inconsistency led to confusion within the ecosystem. Developers working outside of smart contracts tended to rely on Horizon, while those building with smart contracts gravitated toward RPC. By rebranding it as Stellar RPC, we’re creating a unified approach to data access and reinforcing its role as the go-to entry point for all Stellar developers.
Why Move Away from Horizon?
Relying on Horizon for data access is like using a heavy-duty tool for a simple task—it’s powerful but often excessive for most applications. Horizon is built to store the entire historical record of Stellar from inception and offers specialized indexing features that only a select group of applications, such as trading bots and payment processors, actually require.
If you’re managing your own infrastructure, you’ll likely find that Horizon is more than what’s necessary for your specific use case. Additionally, as network activity grows, maintaining Horizon will become increasingly difficult and costly due to the ever-expanding historical data.
For a long time, much of this complexity has been masked by the Stellar Development Foundation (SDF), which has absorbed a significant portion of the operational workload by hosting Horizon. Moving forward, shifting away from Horizon encourages a more efficient ecosystem where developers can build solutions that fit their needs without unnecessary infrastructure overhead.
Source: StellarOrg
