ARCHIVE/xrpl-dev-portal
1
0
Fork 0
mirror of https://github.com/XRPLF/xrpl-dev-portal.git synced 2025-11-28 23:55:49 +00:00
Code Issues Packages Projects Releases Wiki Activity

Consensus diagram cleanup

Browse Source 
- Remove unused HTML tx queue diagram and associated images
- Add white (not transparent) background to some diagrams
- Fix line breaks on a couple images
- Change a couple other concept pages to use the new diagrams
- Remove some newly unused old diagrams
This commit is contained in:
mDuo13
2018-09-27 18:21:23 -07:00
parent 26db69fc41
commit 81d970893a
31 changed files with 26 additions and 6383 deletions
Download Patch File Download Diff File Expand all files Collapse all files

4
content/concepts/payment-system-basics/ledgers.md
View File

@@ -2,13 +2,13 @@
The XRP Ledger is a shared, global ledger that is open to all. Individual participants can trust the integrity of the ledger without having to trust any single institution to manage it. The `rippled` server software accomplishes this by managing a ledger database that can only be updated according to very specific rules. Each instance of `rippled` keeps a full copy of the ledger, and the peer-to-peer network of `rippled` servers distributes candidate transactions among themselves. The consensus process determines which transactions get applied to each new version of the ledger. See also: [The Consensus Process](consensus.html).
![Diagram: Each ledger is the result of applying transactions to the previous ledger version.](img/ledger-process.png)
![Diagram: Each ledger is the result of applying transactions to the previous ledger version.](img/ledger-changes.png)
The shared global ledger is actually a series of individual ledgers, or ledger versions, which `rippled` keeps in its internal database. Every ledger version has a [Ledger Index][] which identifies the order in which ledgers occur. Each closed ledger version also has an identifying hash value, which uniquely identifies the contents of that ledger. At any given time, a `rippled` instance has an in-progress "current" open ledger, plus some number of closed ledgers that have not yet been approved by consensus, and any number of historical ledgers that have been validated by consensus. Only the validated ledgers are certain to be correct and immutable.
A single ledger version consists of several parts:
![Diagram: A ledger has transactions, a state tree, and a header with the close time and validation info](img/ledger-components.png)
![Diagram: A ledger has transactions, a state tree, and a header with the close time and validation info](img/anatomy-of-a-ledger-simplified.png)
* A **header** - The [Ledger Index][], hashes of its other contents, and other metadata.
* A **transaction tree** - The [transactions](transaction-formats.html) that were applied to the previous ledger to make this one. Transactions are the _only_ way to change the ledger.