Rippled II: Deep Dive into the Protocol and Codebase

JavaScript isn't enabled in your browser, so this file can't be opened. Enable and reload.

Rippled II: Deep Dive into the Protocol and Codebase - Quiz

Select the best answer for each question.

Scoring Guide:

18-20 correct answers: Excellent! Your knowledge is solid.
15-17 correct answers: Good understanding. Review the areas you missed.
12-14 correct answers: Decent foundation. Revisit the module materials.
Below 12: Please review the module thoroughly before proceeding.

Email *

Architecture Fundamentals

What is the primary role of the Application class in Rippled?

1 point

Process individual transactions

Manage peer-to-peer connections

Orchestrate initialization and coordination of all subsystems

Store ledger data persistently

Clear selection

Which component is responsible for coordinating ledger progression and maintaining the chain of validated ledgers?

1 point

Application

LedgerMaster

Overlay Network

NodeStore

Clear selection

The Overlay Network layer is primarily responsible for:

1 point

Validating transaction signatures

Storing ledger history

Peer discovery, connection management, and message propagation

Calculating transaction fees

Clear selection

Transaction Processing

In what order do transactions flow through the Rippled system?

1 point

Validation → Submission → Consensus → Application → Closure

Submission → Validation → Open Ledger Application → Consensus → Canonical Application → Ledger Closure

Consensus → Validation → Submission → Application → Closure

Submission → Consensus → Validation → Application → Closure

Clear selection

What happens during the "Open Ledger Application" phase?

1 point

Transactions are permanently written to the ledger

Transactions are tentatively applied to provide immediate feedback

Validators vote on which transactions to include

The ledger is closed and becomes immutable

Clear selection

What is the purpose of the Consensus phase in transaction processing?

1 point

To verify transaction signatures

To check account balances

For validators to agree on which transactions to include in the next ledger

To broadcast transactions to all peers

Clear selection

Transactor Framework

What are the three phases of the Transactor framework in order?

1 point

DoApply → Preflight → Preclaim

Preclaim → Preflight → DoApply

Preflight → Preclaim → DoApply

Preflight → DoApply → Preclaim

Clear selection

Which Transactor phase performs static validation WITHOUT accessing ledger state?

1 point

Preflight

Preclaim

DoApply

PostApply

Clear selection

During which phase are account existence and balance checks performed?

1 point

Preflight - because balances don't change

Preclaim - with read-only ledger access

DoApply - during state modification

Validation - before any processing

Clear selection

What happens during the DoApply phase?

1 point

Transaction format is validated

Signatures are verified

Actual ledger state modification occurs (debiting accounts, creating offers, etc.)

Transaction fees are calculated

Clear selection

Codebase Navigation

Where are the transaction type implementations located in the Rippled codebase?

1 point

src/ripple/protocol/

src/ripple/app/tx/impl/

src/ripple/consensus/

src/ripple/ledger/

Clear selection

Which directory contains the consensus protocol implementation?

1 point

src/ripple/app/

src/ripple/protocol/

src/ripple/consensus/

src/ripple/overlay/

Clear selection

The file `src/ripple/overlay/impl/OverlayImpl.cpp` is responsible for:

1 point

Transaction validation logic

Consensus algorithm implementation

Peer-to-peer networking implementation

Ledger data serialization

Clear selection

Which file contains the Transaction framework foundation?

1 point

src/ripple/app/main/Application.cpp

src/ripple/app/tx/impl/Transactor.cpp

src/ripple/protocol/STTx.h

src/ripple/consensus/Consensus.h

Clear selection

Development Tools & Debugging

What command enables detailed consensus logging in Rippled?

1 point

rippled log_level Consensus info

rippled log_level Consensus trace

rippled enable_logging Consensus

rippled debug Consensus true

Clear selection

What is the primary benefit of running Rippled in standalone mode?

1 point

Better performance for production use

Automatic peer discovery

Deterministic testing with manual ledger control

Enhanced security features

Clear selection

How do you manually close a ledger in standalone mode?

1 point

rippled close_ledger

rippled ledger_accept

rippled finalize_ledger

rippled commit_ledger

Clear selection

What flag is used to start Rippled in standalone mode?

1 point

--alone

--single

--standalone

--isolated

Clear selection

Protocol & Communication

Which of the following is NOT a key architectural layer in Rippled?

1 point

Application Layer

Transaction Processing

Mining Layer

Overlay Network

Clear selection

What is the main purpose of understanding the Rippled codebase architecture?

1 point

To run a validator node

To contribute to XRPL core development and implement protocol amendments

To create simple payment applications

To manage XRP wallets

Clear selection

Please share your social media handles on X and LinkedIn if you want to join the Pizza Challenge (the first 50 to complete the quiz AND post their progress on social get pizza on us). *

1 point

Submit

Clear form

Never submit passwords through Google Forms.

This form was created inside of XRPL Commons.

Does this form look suspicious? Report

Forms