Re-levelization: move non-docs content, rename content→docs

For better URLs, the content folder has been renamed 'docs' and all
other files have been moved up a level. Also, non-docs images have been
moved to the static folder at the top level where they belong.

Many relative paths had to be fixed to make this work.
This commit is contained in:
mDuo13
2024-01-31 17:53:52 -08:00
parent 971053ebcc
commit 7645140477
844 changed files with 3136 additions and 3458 deletions

View File

@@ -15,35 +15,35 @@ The XRP Ledger is a decentralized blockchain that uses its own digital currency
A blockchain is a continuously growing list of records. The blockchain starts with a block of data.
![A block of data](/img/introduction2-data-block.png)
![A block of data](/docs/img/introduction2-data-block.png)
A group of trusted validator nodes reach consensus that the data is valid.
![Validator nodes](/img/introduction3-validators.png)
![Validator nodes](/docs/img/introduction3-validators.png)
The block is uniquely identified with a very elaborate, complicated, computer-generated, cryptographic Hash number that is 64 hexadecimal characters long.
![Crypto hash](/img/introduction4-hash.png)
![Crypto hash](/docs/img/introduction4-hash.png)
The block is also identified by a timestamp with its creation time.
![Timestamp](/img/introduction5-time-stamp.png)
![Timestamp](/docs/img/introduction5-time-stamp.png)
Each validator node gets its own copy of the data block. There is no single central authority. All copies are equally valid.
![Validators with valid copies](/img/introduction6-valid-copies.png)
![Validators with valid copies](/docs/img/introduction6-valid-copies.png)
Each block contains a hash pointer as a link to the previous block. It also has a timestamp, new data, and its own unique hash number.
![Hash pointer](/img/introduction7-two-blocks.png)
![Hash pointer](/docs/img/introduction7-two-blocks.png)
Using this structure, each block has a clear position in the chain, linking back to the previous data block. This creates an immutable chain of blocks. You can always verify all current information on the chain by tracing back through the previous blocks.
![Three data blocks](/img/introduction8-3-blocks.png)
![Three data blocks](/docs/img/introduction8-3-blocks.png)
By design, blockchains are resistant to modification of the data. Every ledger node gets an exact copy of the blockchain.
![Two validators with identical copies of the blockchain](/img/introduction9-2-sets-of-3.png)
![Two validators with identical copies of the blockchain](/docs/img/introduction9-2-sets-of-3.png)
This creates an open, distributed ledger that records transactions between parties efficiently and in a verifiable and permanent way.
@@ -53,11 +53,11 @@ Once recorded, the data in any given block cannot be altered retroactively, unle
Most of the rippled servers in the XRPL monitor or propose transactions. An important subset of servers are run as validators. These trusted servers accumulate lists of new transactions into a new possible ledger instance (a new block in the block chain).
![Gathering Transactions](/img/introduction17-gather-txns.png)
![Gathering Transactions](/docs/img/introduction17-gather-txns.png)
They share their lists with all of the other validators. The validators incorporate proposed changes from one another and distribute a new version of the ledger proposal.
![80% Consensus](/img/introduction18-80-percent-consensus.png)
![80% Consensus](/docs/img/introduction18-80-percent-consensus.png)
When 80% of the validators agree on a set of transactions, they create a new ledger instance at the end of the chain and start the process again. This consensus process takes 4-6 seconds. You can monitor as ledger instances are created in real time by visiting [https://livenet.xrpl.org/](https://livenet.xrpl.org/).