Revised docs based on tips from user (#2611)

This commit is contained in:
Troy McConaghy 2018-12-02 22:07:31 +01:00 committed by GitHub
parent f0df5bd2e0
commit d9725d483b
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
2 changed files with 8 additions and 3 deletions

View File

@ -81,7 +81,7 @@ from all the Members, and should combine them in the file
"validators":[
{
"pub_key":{
"type":"AC26791624DE60",
"type":"tendermint/PubKeyEd25519",
"value":"<Member 1 public key>"
},
"power":10,
@ -89,7 +89,7 @@ from all the Members, and should combine them in the file
},
{
"pub_key":{
"type":"AC26791624DE60",
"type":"tendermint/PubKeyEd25519",
"value":"<Member 2 public key>"
},
"power":10,
@ -103,7 +103,7 @@ from all the Members, and should combine them in the file
},
{
"pub_key":{
"type":"AC26791624DE60",
"type":"tendermint/PubKeyEd25519",
"value":"<Member N public key>"
},
"power":10,

View File

@ -1,5 +1,10 @@
# Tips
## Tendermint Tips
* [Configure Tendermint to create no empty blocks](https://tendermint.com/docs/tendermint-core/using-tendermint.html#no-empty-blocks).
* Store the Tendermint data on a fast drive. You can do that by changing [the location of TMHOME](https://tendermint.com/docs/tendermint-core/using-tendermint.html#directory-root) to be on the fast drive.
## Refreshing Your Node
If you want to refresh your node back to a fresh empty state, then your best bet is to terminate it and deploy a new machine, but if that's not an option, then you can: