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

# Homework 1: Transaction Flow Analysis

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

***

### Objective

This homework reinforces your understanding of the Rippled architecture, transaction processing, and codebase navigation. You will perform hands-on exploration of the codebase and analyze transaction

**Format**: Written report (PDF or Markdown) with screenshots/code snippets

***

### Task

Run Rippled in standalone mode and trace a Payment transaction from submission to ledger closure.

#### Requirements

1. **Setup**
   * Start Rippled in standalone mode
   * Submit a Payment transaction using RPC
   * Manually close the ledger
2. **Documentation**
   * Document the complete transaction lifecycle with timestamps
   * Capture and explain the transaction JSON
   * Take a screenshot of the transaction result
   * Identify which files in the codebase handle each phase:
     * Submission
     * Validation (Preflight/Preclaim)
     * Application (DoApply)
     * Ledger closure

***

### Deliverable

A written report with:

* Commands used
* Transaction details (hash, account, destination, amount)
* Screenshots of the transaction submission and result
* List of relevant source files with brief explanations of their roles


---

# 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/module02/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.