Local Development & Testing

Running Rippled in Standalone Mode

← Back to Rippled I Overview

Introduction

Once built, Rippled can run in standalone mode — a fully local setup for testing transactions and ledger behavior without connecting to the XRPL network. It offers full API access and manual ledger control, perfect for isolated development.

You’ll learn to launch Rippled locally and explore it with XRPL Explorer and Playground to simulate end-to-end XRPL workflows.

In stand-alone mode, the server operates without connecting to the network and participating in the consensus process. Without the consensus process, you have to manually advance the ledger and no distinction is made between "closed" and "validated" ledgers. However, the server still provides API access and processes transactions the same.

Learn more about stand-alone mode.

cd ~/projects/rippled/build
cp ../config -r ./config
./rippled -a --conf ./config/rippled.cfg

  • Option with genesis ledger:

./rippled -a --conf ./config/rippled.cfg --ledgerfile ./config/genesis.json

The following options determine which ledger to load first when starting up.

  • Check the logs to confirm that the server is running correctly.

Interacting with Rippled via XRPL Explorer

  1. Install dependencies:

cd ~/core-dev-bootcamp-2025/explorer
npm install

  1. Launch the explorer:

npm run serve

  1. Navigate to http://localhost:8080/ to view transactions and the ledger.

  2. Test commands such as server_info, ledger_current, account_info from the interface or via cURL/WebSocket.

Playground – Connection and Tests

git clone https://github.com/XRPL-Commons/core-dev-bootcamp-2025/tree/main/playground
cd core-dev-bootcamp-2025/playground
yarn install
ts-node src/connect.ts
ts-node src/fund.ts

  • Create and fund test accounts to interact with the local ledger.

  • Verify transactions in the explorer and via the interface/command.

PreviousCompilation Process & Generating BinaryNextHomeworks

Last updated