mirror of
https://github.com/XRPLF/xrpl-dev-portal.git
synced 2026-06-03 00:36:40 +00:00
Merge pull request #227 from mDuo13/validation_caution
rippled setup - clarify people shouldn't use the validation_seed from example
This commit is contained in:
@@ -218,11 +218,13 @@ Running a `rippled` validator that participates in the Consensus process is simp
|
||||
"validation_seed" : "ssdecohJMDPFuUPDkmG1w4objZyp4"
|
||||
}
|
||||
|
||||
4. Add the generated validator signing key from above to your `rippled.cfg`:
|
||||
4. Edit your `rippled.cfg` file to add the `validation_seed` value you generated in step 3:
|
||||
|
||||
[validation_seed]
|
||||
ssdecohJMDPFuUPDkmG1w4objZyp4
|
||||
|
||||
**Warning:** Be sure to use your own unique random seed, and keep it secure! If others know your `validation_seed`, they can forge validations from your server.
|
||||
|
||||
5. Restart `rippled` validator:
|
||||
|
||||
$ sudo service rippled restart
|
||||
|
||||
@@ -379,10 +379,11 @@ $ sudo apt-get install yum-utils alien
|
||||
</code></pre>
|
||||
</li>
|
||||
<li>
|
||||
<p>Add the generated validator signing key from above to your <code>rippled.cfg</code>:</p>
|
||||
<p>Edit your <code>rippled.cfg</code> file to add the <code>validation_seed</code> value you generated in step 3:</p>
|
||||
<pre><code>[validation_seed]
|
||||
ssdecohJMDPFuUPDkmG1w4objZyp4
|
||||
</code></pre>
|
||||
<p class="devportal-callout warning"><strong>Warning:</strong> Be sure to use your own unique random seed, and keep it secure! If others know your <code>validation_seed</code>, they can forge validations from your server.</p>
|
||||
</li>
|
||||
<li>
|
||||
<p>Restart <code>rippled</code> validator:</p>
|
||||
|
||||
Reference in New Issue
Block a user