> For the complete documentation index, see [llms.txt](https://docs.xrpl-commons.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.xrpl-commons.org/core-dev-bootcamp/module01/local-development-testing.md).

# Local Development & Testing

### Running Rippled in Standalone Mode

[← Back to Rippled I Overview](/core-dev-bootcamp/module01.md)

***

#### 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](https://xrpl.org/docs/concepts/networks-and-servers/rippled-server-modes#stand-alone-mode).

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

* Option with genesis ledger:

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

> [The following options determine which ledger to load first when starting up.](https://xrpl.org/docs/infrastructure/commandline-usage#initial-ledger-options)

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

### Interacting with Rippled via XRPL Explorer

1. Install dependencies:

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

2. Launch the explorer:

```bash
npm run serve
```

3. Navigate to <http://localhost:8080/> to view transactions and the ledger.
4. Test commands such as `server_info`, `ledger_current`, `account_info` from the interface or via cURL/WebSocket.

### Playground – Connection and Tests

```bash
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.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.xrpl-commons.org/core-dev-bootcamp/module01/local-development-testing.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.