Practical overview
When it fits
Use Rippled when a project needs node-level access to the XRP Ledger or infrastructure built around its protocol. For an API Server or Full History Server, follow the repository's reference to Clio instead.
Who it is for
- Blockchain infrastructure operators
- Developers building services connected to the XRP Ledger
- Teams creating monitoring or operational tools for XRP Ledger nodes
- Researchers and contributors examining the ledger's protocol implementation
Documented uses
- Run an XRP Ledger node.
- Build a transaction-settlement service connected to an XRP Ledger node.
- Create application infrastructure that uses XRP Ledger transactions.
- Develop monitoring and operational tooling around peer-to-peer nodes.
- Study or contribute to the XRP Ledger's C++ implementation.
Requirements & limits
The repository is public and available under the ISC open-source license. The cited materials provide build and installation documentation rather than hosted-service access details.
- Choose it when direct XRP Ledger node infrastructure is required.
- Account for the need to follow repository-specific build and configuration documentation.
- Check whether the required server role is covered by rippled or should use Clio for API and full-history service needs.
- The implementation is primarily C++, with repository contents also including some Rust source.
Check current requirements in the official documentation. Source-based guidance does not mean OpenViST has run or independently tested this project.
Sources & review
Source record details
- Source availability
- Active
- Sources checked
- 2 October 2026
- Original website title
- XRPLF/rippled · Official homepage title · retained in its source language
Related options
Clio — The repository identifies Clio as the separate API Server and Full History Server component for XRP Ledger use cases.
Explore project →
