reorganized consensus network articles per new structure

This commit is contained in:
Ryan Young
2018-05-09 14:42:28 -07:00
parent ce4eecab43
commit 64e3347cfa
4 changed files with 34 additions and 8 deletions

View File

@@ -2,30 +2,33 @@
<!--{# TODO: Are we learning about the Consensus Network or the Consensus Process? Both? Is one a child of the other -- or is the parent concept simply Consensus? Also, need to be careful to differentiate this content from the content we provide in Concepts > XRP Ledger Basics > Consensus. What should I expect to learn here - and how is it different from what I will learn there? #}-->
The primary role of consensus is for participants in the process to agree on which XRP Ledger transactions are to be processed as a group to resolve the double spend problem. This section covers concepts that help you learn the "what" and "why" behind fundamental aspects of consensus in the XRP Ledger.
* **[Consensus Principles and Rules](x)**
* **[Consensus Principles and Rules](consensus-principles-and-rules.html)**
Understand the principles and rules involved in reaching consensus in the XRP Ledger, including some background on the double-spend problem and details about how consensus works.
<!--{# TODO: this language needs to be refined based on what we're actually focusing on here. Are these the principles and rules of consensus, the network, or the process? https://developers.ripple.com/concept-reaching-consensus.html #}-->
<!--{#
* **[Validators and the Trust Topology](x)**
<!--{# TODO: need this intro text - what is this about? What page does it link to? New content? #}-->
TODO: need this intro text - what is this about? What page does it link to? New content? #}-->
* **[Amendments](x)**
* **[Amendments](amendments.html)**
An amendment is a fully-functional feature or change, waiting to be enabled by the peer-to-peer network as a part of the consensus process. Understand the purpose of amendments and the amendment voting process.
<!--{# https://developers.ripple.com/concept-amendments.html #}-->
* **[Fee Voting](x)**
* **[Fee Voting](fee-voting.html)**
Fees include basic transaction costs as well as reserve requirements. Validators can vote for changes to fees. Understand the purpose and process of fee voting.
<!--{# https://developers.ripple.com/concept-fee-voting.html #}-->
<!--{# TODO: write conceptual article for this
* **[Pseudo-Transactions](x)**
Pseudo-transactions are never submitted by users, nor are they propagated through the network. Instead, a server may choose to inject them directly into a proposed ledger. If enough servers inject an equivalent pseudo-transaction for it to pass consensus, then it is included in the ledger. Understand the purpose and processing of pseudo-transactions.
<!--{# https://ripple.com/build/transactions/#pseudo-transactions #}-->
https://ripple.com/build/transactions/#pseudo-transactions #}-->
<!--{#
* **[Consensus White Papers](x)**
Access these Ripple white papers to get a close-up look at the XRP Ledger consensus algorithm.
<!--{# TODO: need to create this page of content #}-->
TODO: need to create this page of content #}-->

View File

@@ -1,4 +1,4 @@
# Reaching Consensus in the XRP Ledger
# Consensus Principles and Rules
The XRP Ledger is a universal payment system enabling users to transfer funds (including fiat currencies, digital currencies and other forms of value) across national boundaries as seamlessly as sending an email. Like other digital currencies such as Bitcoin, the XRP Ledger enables peer-to-peer transaction settlement across a decentralized network of computers. Unlike other digital currency protocols,the XRP Ledger also allows users to transact in currencies other than the ledger's native currency, XRP. In addition, the technology enables near real-time settlement (three to six seconds) and is built to route each international transaction to the cheapest FX bid/ask spread available in the network.

View File

@@ -2,7 +2,11 @@
Validators can vote for changes to basic [transaction cost](concept-transaction-cost.html) as well as [reserve requirements](concept-reserves.html). If the preferences in a validator's configuration are different than the network's current settings, the validator expresses its preferences to the network periodically. If a quorum of validators agrees on a change, they can apply a change that takes effect thereafter. Validators may do this for various reasons, especially to adjust to long-term changes in the value of XRP.
Operators of [`rippled` validators](tutorial-rippled-setup.html#running-a-validator) can set their preferences for the transaction cost and reserve requirements in the `[voting]` stanza of the `rippled.cfg` file. **Caution:** insufficient requirements could expose the XRP Ledger peer-to-peer network to denial-of-service attacks. The parameters you can set are as follows:
Operators of [`rippled` validators](tutorial-rippled-setup.html#running-a-validator) can set their preferences for the transaction cost and reserve requirements in the `[voting]` stanza of the `rippled.cfg` file.
**Caution:** Insufficient requirements could expose the XRP Ledger peer-to-peer network to denial-of-service attacks.
The parameters you can set are as follows:
| Parameter | Description | Recommended Value |
|-----------|-------------|-------------------|