mirror of
https://github.com/XRPLF/rippled.git
synced 2026-08-21 22:30:57 +00:00
7551d57db9
A 54-panel audit across 11 dimensions, each finding adversarially re-verified against live data, returned 38 confirmed defects. This fixes them. Most were introduced by the recent rate-to-count conversion itself. 1. increase() was the wrong function for these counters. A counter that only moves at startup is born at its final value inside the window and never rises, so increase() reports 0. Measured: dns_resolve_total reads 4 but round(increase(...[$__range])) returned 0 -- the panel lost the signal entirely. increase() also drops whatever accrued before the window opened, which under-reported the rest (overlay_connect_total 110 against a true 130, unl_fetch_total 10 against 14, peer_disconnect_total 7 against 8). All 18 count panels now use last_over_time(...[$__range]), which on a fresh-node board is the cumulative total since the process started -- exactly what "count" means here. EXCEPT panel 49. span_calls_total comes from the collector's spanmetrics connector, which is collector-side state and does NOT reset when xrpld restarts, so last_over_time would report the collector's lifetime across every run: it read 2624 header completions where run C actually had 297. That panel keeps round(increase(...)) and now reports 297/278/212/7, matching the analysis. The distinction is process-level counter vs collector-side counter, and it decides which function is correct. 2. Descriptions still described rates after the conversion, over three passes of wording (Reading it / Healthy range / Watch for blocks, "Rate of", "per second", "/s", "a rising rate"). 11 panels corrected; the two surviving uses of "rate" are legitimate (a cache hit-rate reference, and panel 49 explaining why a count reads better than a rate). 3. Ten descriptions pointed at panel titles that no longer exist, because the conversion renamed the panels they cross-referenced. Two others named panels that never existed on this board at all: "Total Jobs Queued" (now Worker Pool Capacity & Total Backlog, panel 27) and "Fetch-Pack Peer Starvation" (now Peers Able to Serve Needed Sequence, panel 28). 4. Panels 18 and 23 applied $acquire_metric on top of a hard-coded metric selector, so the two ANDed: any selection outside the panel's own values gave an empty graph and All was the only usable state. The redundant template selector is gone; the panel's metric pair is its identity. 5. Panel 23 drew two series with different ranges (received_data_depth 0-20, in_flight 13-49) under one yellow threshold at 16, so in_flight was permanently yellow. The threshold is now scoped to received_data_depth. 6. The "Spans & traces" row sat at y=248, the same y as panels 38/39, so Grafana folded the Back-fill panels into the wrong row. Moved to y=296, below the last back-fill panel. Rows are now strictly ascending with no collision. Verified against Grafana Cloud Prometheus: all 66 panel queries parse, 0 errors, 57 returning data (up from 56 -- panel 3 was one of the ones increase() had silenced). validate_dashboards and check_otel_naming both pass. Not verified: no PNG renders this round; the local Grafana and Prometheus are down, so every check ran against Cloud data via the datasource proxy. 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.