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

Update content/faq.md

Browse Source 
Co-authored-by: Rome Reginelli <mduo13@gmail.com>
This commit is contained in:
Wo Jake
2022-09-08 03:42:24 +00:00
committed by GitHub
parent 5df7d45a47
commit 53fd502d40
1 changed files with 3 additions and 1 deletions
Download Patch File Download Diff File Expand all files Collapse all files

4
content/faq.md
View File

@@ -104,7 +104,9 @@ For recommendations and best practices, see [Run `rippled` as a Validator](run-r
#### If the dUNL has the most influence on the network, then is the XRPL centralized? #### If the dUNL has the most influence on the network, then is the XRPL centralized?
Validators can choose to not use the dUNL, or any widely-used UNL for that matter. Anyone can create a new UNL at any time. Validators can choose to not use the dUNL, or any widely-used UNL for that matter. Anyone can create a new UNL at any time.
There can be other UNLs in use on the network. The dUNL is the most widely-used UNL, but validators can choose others. There can be multiple UNLs in use on the same network. Each operator can customize their server's own UNL or choose to follow a different recommended list. All these servers can still operate on the same chain and reach consensus with one another.
However, if your UNL does not have sufficient overlap with the UNLs used by others, there is a risk that your server forks away from the rest of the network. As long as your UNL has > 90% overlap with the one used by people you're transacting with, you are completely safe from forking. If you have less overlap, you may still be able to follow the same chain, but the chances of forking increase with lower overlap, worse network connectivity, and the presence of unreliable or malicious validators on your UNL.
## Role of XRP ## Role of XRP