Label: Core Server

Get an overview of what XRP Ledger software is out there and how it fits together.

Learn about rippled server modes, including stock servers, validator servers, and rippled servers run in stand-alone mode.

Run rippled servers in a cluster to share the load of cryptography between them.

rippled servers store a variable amount of transaction and state history locally.

Online deletion purges outdated transaction and state history.

History sharding divides the work of keeping historical ledger data among rippled servers.

The peer protocol specifies the language rippled servers speak to each other.

Use these public servers to access the XRP Ledger without needing your own infrastructure.

Hardware and software requirements for running rippled.

Install a precompiled rippled binary on CentOS or Red Hat Enterprise Linux.

Install a precompiled rippled binary on Ubuntu Linux.

Set up automatic updates for rippled on Linux.

Manually update rippled on CentOS or Red Hat Enterprise Linux.

Manually update rippled on Ubuntu Linux.

Compile rippled yourself on Ubuntu Linux.

Compile rippled yourself on macOS.

Build and run a special operating mode of rippled that handles remote procedure calls (RPC) for validated data.

Plan system specs and tune configuration for rippled in production environments.

Have your server vote on the consensus ledger.

A multipurpose configuration for anyone integrating XRP.

Set your server's votes on protocol amendments.

Monitor your rippled server with StatsD metrics.

Connect your rippled server to the test net to try out new features or test functionality with fake money.

Configure how far back your server should store transaction history.

Use advisory deletion to delete older ledger history on a schedule rather than as new history becomes available.

Set up a server to contribute to preserving shards of historical XRP Ledger data.

Full history servers provide a record of every transaction ever to occur in the XRP Ledger, although they are expensive to run.

Enable and configure the gRPC API.

Allow others to use your server to sign transactions. (Not recommended)

Configure how your server connects to the peer-to-peer network.

Set up a group of servers that share work for higher efficiency.

Set up a server to connect only to specific, trusted peers.

Configure how much information your rippled server reports publicly about its status and peers.

Save bandwidth by compressing peer-to-peer communications.

Configure your firewall to allow incoming peers to your rippled server.

Connect your rippled server to a specific peer.

Set the maximum number of peers your rippled server connects to.

Set up a more reliable connection to a specific peer using a peer reservation.

Start from a fresh genesis ledger in stand-alone mode.

Start in stand-alone mode from a specific saved ledger to test or replay transactions.

Make progress in stand-alone mode by manually closing the ledger.

Collect information to identify the cause of problems.

Use the rippled server's health check as part of automated infrastructure monitoring.

Interpret and respond to warning and error messages in the debug log.

Troubleshoot problems that make a rippled server unable to sync with the rest of the XRP Ledger.

Troubleshoot a server that can't implement amendment changes.

A collection of problems that would cause a rippled server not to start, and how to fix them.

Information on how public APIs limit clients from making too many requests.

Definitions of state information reported in some API methods.

Get data from the XRP Ledger and submit transactions using these public API methods.

Retrieve status of the server in human-readable format.

Retrieve status of the server in machine-readable format.

Retrieve status of the Clio server in human-readable format.

Pass JSON through the commandline.

Confirm connectivity with the server.

Generate a random number.

Administer an XRP Ledger server with these API methods.

Generate keys for a rippled server to identify itself to the network.

Close and advance the ledger in stand-alone mode.

Shut down the rippled server.

(Obsolete) Temporarily set key to be used for validating.

Force the rippled server to connect to a specific peer.

Add a reserved slot for a specific peer server.

Remove a reserved slot for a specific peer server.

List reserved slots for specific peer servers.

Get information about the peer servers connected.

Get information about the state of consensus as it happens.

Get information about protocol amendments.

Get information about the server's sync with the network.

Get statistics about the server's internals and memory usage.

Get information about internal subsystems.

Get information about sites that publish validator lists.

Get information about the current validators.

Commandline usage options for the rippled server.

Special API method for reporting server health.

Special API method for sharing network topology and status metrics.

Special API method for sharing recommended validator lists.