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

fixed headings

Browse Source
This commit is contained in:
Jennifer Hasegawa
2018-05-15 16:11:47 -07:00
parent 0bcf003f05
commit 743b7b07dd
2 changed files with 3 additions and 5 deletions
Download Patch File Download Diff File Expand all files Collapse all files

2
content/concepts/the-rippled-server/peer-protocol.md
View File

@@ -160,7 +160,7 @@ Response:
You can use the `[peer_private]` stanza of the `rippled` config file to request that peer servers do not report your IP address in the Peer Crawler response. Servers you do not control can be modified not to respect this setting. However, you can use this to hide the IP addresses of `rippled` servers you control that _only_ connect to peers you control (using `[ips_fixed]` and a firewall). In this way, you can use public rippled servers you control as proxies for your private rippled servers.
To protect an important [validating server](rippled-server-modes.html#types-of-rippled-servers), Ripple recommends configuring one or more public tracking servers to act as proxies, while the validating server is protected by a firewall and only connects to the public tracking servers.
To protect an important [validating server](rippled-server-modes.html), Ripple recommends configuring one or more public tracking servers to act as proxies, while the validating server is protected by a firewall and only connects to the public tracking servers.
<!--{# TODO: network diagram of private peers #}-->

6
content/concepts/the-rippled-server/rippled-server-modes.md
View File

@@ -1,9 +1,5 @@
# rippled Server Modes
`rippled` is the core peer-to-peer server that manages the XRP Ledger.
## Types of rippled Servers
The `rippled` server software can run in several modes depending on its configuration, including:
* Stock server - follows the network with a local copy of the ledger.
@@ -12,6 +8,7 @@ The `rippled` server software can run in several modes depending on its configur
You can also run the `rippled` executable as a client application for accessing [`rippled` APIs](rippled-api.html) locally. (Two instances of the same binary can run side-by-side in this case; one as a server, and the other running briefly as a client and then terminating.)
## Reasons to Run a Stock Server
There are lots of reasons you might want to run your own `rippled` server, but most of them can be summarized as: you can trust your own server, you have control over its workload, and you're not at the mercy of others to decide when and how you can access it. Of course, you must practice good network security to protect your server from malicious hackers.
@@ -35,6 +32,7 @@ Not all `rippled` servers need to be validators: trusting more servers from the
If your organization runs a validating server, you may also run one or more stock servers, to balance the computing load of API access, or as a proxy between your validation server and the outside network.
### Properties of a Good Validator
There are several properties that define a good validator. The more of these properties your server embodies, the more reason others have to include your server in their list of trusted validators: