validator tut: daniel, rome feedback

This commit is contained in:
Jennifer Hasegawa
2019-02-27 17:05:03 -08:00
parent 2a0990495f
commit 75fd2bbccd
4 changed files with 84 additions and 98 deletions

View File

@@ -37,14 +37,14 @@ To configure your `rippled` server to run in validator mode, generate a validato
<span class="use-case-step-num">{{n.next()}}</span>
<!-- <span class="use-case-step-length">(1 hour)</span> -->
## [Set up a stock rippled server as a proxy](run-rippled-as-a-validator.html#connect-to-the-network-using-proxies)
## [Set up a stock rippled server as a proxy](run-rippled-as-a-validator.html#connect-using-proxies)
To protect a production validator from DDoS attacks, you can use a stock `rippled` server as a proxy between the validator and the outside network.
<span class="use-case-step-num">{{n.next()}}</span>
<!-- <span class="use-case-step-length">(1 hour)</span> -->
## [Associate your validator with a web domain you control](run-rippled-as-a-validator.html#provide-domain-verification)
## [Associate your validator with a web domain you control](run-rippled-as-a-validator.html#6-provide-domain-verification)
Network participants are unlikely to trust a validator without knowing who is operating it. To address this concern, associate your validator with a web domain you control.
You may also wish to have your validator listed with one or more validator tracking services, such as the [XRP Charts Validator Registry](https://xrpcharts.ripple.com/#/validators).