> 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/homeworks/homework1.md).

# Homework 1: Rippled Node Setup and Mainnet Synchronization

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

***

### Objective

* Configure and launch Rippled on the XRPL mainnet
* Analyze the logs to understand the node's behavior during initial synchronization

***

### Tasks

1. Create a `config` directory and copy the example configuration files.
2. Configure `rippled.cfg` to connect to the mainnet.
3. Start synchronization:

```bash
./rippled --conf ./config/rippled.cfg
```

4. Identify your node on the network using `server_info` and check its visibility on the XRPL explorer.
5. Analyze the logs to observe: startup, peer connections, ledger acquisition, and participation in consensus.
6. Document your experience and any errors encountered.

#### Bonus

* Compare your node with other nodes on the network
* Monitor connectivity and latency relative to the global network


---

# 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/homeworks/homework1.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.