Run a rippled Validator
rippled server (not running in stand-alone mode) connects to a network of peers, relays cryptographically signed transactions, and maintains a local copy of the complete shared global ledger. A
rippled server running in validator mode additionally participates in the consensus process and is a part of an interconnected web of validators who each trust a specific set of validators not to collude. Here’s a roadmap to the high-level tasks you’ll need to perform to run a
If you or your organization relies on the XRP Ledger, it is in your interest to run a validator to participate in the consensus process and provide a trusted validator that supports the ongoing decentralization of the XRP Ledger.
If you are an independent developer, you may want to run a validator as a way to participate in and dive into the technology that supports the XRP Ledger network.
While validator diversity is important, not every validator is likely to be widely trusted and validator list publishers may require validators to meet stringent criteria before they list them on validator lists.
Despite that, it is important to note that every validator contributes to the long-term health and decentralization of the XRP Ledger.
Install and run a
rippled server. Anyone can run their own
rippled server that follows the network and keeps a complete copy of the XRP Ledger.
For configuration guidance and network and hardware requirements, see Capacity Planning.
To configure your
rippled server to run in validator mode, generate a validator key pair and add it to your
To protect a production validator from DDoS attacks, you can use a stock
rippled server as a proxy between the validator and the outside network.
Network participants are unlikely to trust a validator without knowing who is operating it. To address this concern, associate your validator with a web domain you control. You may also wish to have your validator listed with one or more validator tracking services, such as the XRP Charts Validator Registry .