mirror of
https://github.com/XRPLF/rippled.git
synced 2026-09-27 15:28:03 +00:00
7f8f5b4be3
Alloy carried no log pipeline at all: no loki.source, loki.write or loki.process anywhere in the config, against a working metrics and OTLP path. Any deployment fed through Alloy rather than the reference collector therefore sent traces and metrics but no logs, so log-to-trace correlation was unavailable there even though both ends of the link were configured. Logs now leave through the same otlphttp exporter as the other two signals, so all three carry one resource identity. Alloy's own filelog receiver would have been the closest match to the reference collector, but it is still public-preview and refuses to load unless the service is started with --stability.level=public-preview, which would mean editing the unit on a box reachable only by RunCommand. The Loki source components are generally available, so they are used and bridged into OTLP by otelcol.receiver.loki; the service needs no extra flag. That bridge hands over an empty resource and puts everything on the log record, so the transform sets the resource attributes in log context. service.instance.id is concatenated in from XRPLD_HOST_LABEL because OTTL has no env() converter, and it is a resource attribute rather than a record one because only resource attributes are promoted to indexed Loki labels. It must equal the node's own service_instance_id or the logs join nothing. devnet writes one flat file rather than a per-node directory, so identity cannot be read off the path the way the docker collector does it; XRPLD_LOG_GLOB overrides the path for other layouts. The line is parsed for its own timestamp, severity and trace context, and trace_id/span_id are set on the first-class OTLP record fields so Grafana links a log to its trace without re-parsing the body. Lines emitted outside a sampled span keep an empty trace id rather than an invalid one. Also carry the node-identity operators into the Grafana Cloud collector variant, align this config's log directory with its service_instance_id, and rename the deprecated otlphttp/filelog collector component names. Alloy's otelcol.exporter.otlphttp is that product's own name and is unchanged.
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. |
./crates |
Rust source code. |
Some of the directories under src are external repositories included using
git-subtree. See those directories' README files for more details.