mirror of
https://github.com/XRPLF/rippled.git
synced 2026-08-21 22:30:57 +00:00
206d3620c7
Second pass on the 54-panel audit. The first commit handled the count panels and the description drift; these are the query and threshold defects. Panels 4 and 6 (DNS Resolve / Outbound Dial p95) read NaN for the whole run. Two faults compounded: both hard-coded [5m] instead of $__rate_interval, so they ignored the dashboard time range entirely, and both wrapped the histogram buckets in rate() even though DNS resolution and outbound dialling only happen during startup -- a windowed rate over a series that stopped moving is 0/0. Dropping rate() and reading the cumulative buckets gives the real distribution: p95 900 ms for DNS, 1750 ms for dialling. Panel 52 kept its rate() (consensus rounds are ongoing) but its hard-coded [5m] became $__rate_interval. Panel 15 plotted 105,892,534 "ledgers behind" during the flagship window. The underlying cause is in NetworkOPs.cpp -- getLedgersBehindNetwork() subtracts the validated sequence from a networkTarget of 0 before any peer has reported -- and that still needs a code fix. Meanwhile one sentinel spike flattened the real 0-20 backlog for the rest of the window, so the query now clamps at 1e6, far above any true backlog. Reads 4 where it read 105 million. Panel 17's sum by (from, to) dropped node identity, so with All nodes selected every node's transitions summed into one bar. It now carries service_instance_id, xrpl_branch and xrpl_work_item like every other panel. Panel 38 divided by clamp_min(op_rate, 1), which turns "no operations in this interval" into "one operation", reporting the whole duration total as if a single op had consumed it. Replaced with a `> 0` gate so an idle interval draws a gap instead of a fabricated latency. Panels 13 and 45 had inverted thresholds: green began at 1 second, so every sub-second time-to-full and time-to-first-validated rendered red -- the healthy case was the alarming colour. Now green by default, yellow past 10 minutes, red past 30. Panel 48's p95 had no outcome filter, mixing abandoned and timed-out spans (which sit at the retry ceiling by construction) into what reads as completion latency. Restricted to outcome="complete". Verified against Grafana Cloud: 66 queries, 0 parse errors, 56 with data, 9 legitimately empty (fault-only counters plus the write-timing series that pre-dates both recorded nodes). The single remaining NaN is on panel 47 and is an artifact of my verification harness forcing a hard 5m window; the panel's own $__rate_interval returns 492 ms, so it needs no change. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
The XRP Ledger
The XRP Ledger is a decentralized cryptographic ledger powered by a network of peer-to-peer nodes. The XRP Ledger uses a novel Byzantine Fault Tolerant consensus algorithm to settle and record transactions in a secure distributed database without a central operator.
XRP
XRP is a public, counterparty-free crypto-asset native to the XRP Ledger, and is designed as a gas token for network services and to bridge different currencies. XRP is traded on the open-market and is available for anyone to access. The XRP Ledger was created in 2012 with a finite supply of 100 billion units of XRP.
xrpld
The server software that powers the XRP Ledger is called xrpld and is available in this repository under the permissive ISC open-source license. The xrpld server software is written primarily in C++ and runs on a variety of platforms. The xrpld server software can run in several modes depending on its configuration.
If you are interested in running an API Server (including a Full History Server), take a look at Clio. (xrpld Reporting Mode has been replaced by Clio.)
Build from Source
- Read the build instructions in
BUILD.md - If you encounter any issues, please open an issue
Key Features of the XRP Ledger
- Censorship-Resistant Transaction Processing: No single party decides which transactions succeed or fail, and no one can "roll back" a transaction after it completes. As long as those who choose to participate in the network keep it healthy, they can settle transactions in seconds.
- Fast, Efficient Consensus Algorithm: The XRP Ledger's consensus algorithm settles transactions in 4 to 5 seconds, processing at a throughput of up to 1500 transactions per second. These properties put XRP at least an order of magnitude ahead of other top digital assets.
- Finite XRP Supply: When the XRP Ledger began, 100 billion XRP were created, and no more XRP will ever be created. The available supply of XRP decreases slowly over time as small amounts are destroyed to pay transaction fees.
- Responsible Software Governance: A team of full-time developers at Ripple & other organizations maintain and continually improve the XRP Ledger's underlying software with contributions from the open-source community. Ripple acts as a steward for the technology and an advocate for its interests.
- Secure, Adaptable Cryptography: The XRP Ledger relies on industry standard digital signature systems like ECDSA (the same scheme used by Bitcoin) but also supports modern, efficient algorithms like Ed25519. The extensible nature of the XRP Ledger's software makes it possible to add and disable algorithms as the state of the art in cryptography advances.
- Modern Features: Features like Escrow, Checks, and Payment Channels support financial applications atop of the XRP Ledger. This toolbox of advanced features comes with safety features like a process for amending the network and separate checks against invariant constraints.
- On-Ledger Decentralized Exchange: In addition to all the features that make XRP useful on its own, the XRP Ledger also has a fully-functional accounting system for tracking and trading obligations denominated in any way users want, and an exchange built into the protocol. The XRP Ledger can settle long, cross-currency payment paths and exchanges of multiple currencies in atomic transactions, bridging gaps of trust with XRP.
Source Code
Here are some good places to start learning the source code:
- Read the markdown files in the source tree:
src/xrpld/**/*.md. - Read the levelization document to get an idea of the internal dependency graph.
- In the big picture, the
mainfunction constructs anApplicationImpobject, which implements theApplicationvirtual interface. Almost every component in the application takes anApplication¶meter in its constructor, typically namedappand stored as a member variableapp_. This allows most components to depend on any other component.
Repository Contents
| Folder | Contents |
|---|---|
./bin |
Scripts and data files for XRPL developers. |
./Builds |
Platform-specific guides for building xrpld. |
./docs |
Source documentation files and doxygen config. |
./cfg |
Example configuration files. |
./src |
Source code. |
Some of the directories under src are external repositories included using
git-subtree. See those directories' README files for more details.