Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Fix typos #40

Merged
merged 1 commit into from
Sep 18, 2020
Merged

Fix typos #40

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
8 changes: 4 additions & 4 deletions doc/setup-masternodes.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -2,7 +2,7 @@

## Introduction

Setting up a masternode on Defichain allows you to participate in the consensus protocol and receive staking awards. One thing to note is that in order to set up a masternode, you must have a minimum of 1 million DFI tokens.
Setting up a masternode on DefiChain allows you to participate in the consensus protocol and receive staking awards. One thing to note is that in order to set up a masternode, you must have a minimum of 1 million DFI tokens.

> NOTE: This how-to expects some basic familiarity with the Linux terminal
Expand Down Expand Up @@ -57,7 +57,7 @@ into the file and hit `Ctrl-X` then enter to save the file.

### Step 4 - Setting up owner address with sufficient funds

In order to run a masternode, you must own atleast 1 million DFI tokens. Let's set up an address with sufficient funds to use as an owner. Masternodes currently only support legacy addresses, so create a masternode address using:
In order to run a masternode, you must own at least 1 million DFI tokens. Let's set up an address with sufficient funds to use as an owner. Masternodes currently only support legacy addresses, so create a masternode address using:

```
~/.defi/defi-cli getnewaddress "<label>" legacy
Expand Down Expand Up @@ -93,7 +93,7 @@ masternode_operator=OPERATOR_ADDRESS
masternode_owner=OWNER_ADDRESS
```

Because we have decided to run owner and operator on the same address, just substitue the same legacy address you created for `OPERATOR_ADDRESS` and `OWNER_ADDRESS`.
Because we have decided to run owner and operator on the same address, just substitute the same legacy address you created for `OPERATOR_ADDRESS` and `OWNER_ADDRESS`.

Now the final step is to restart the node. Since we have crontab running, we just have to kill the process and crontab will start it again for us after one minute. We can do this final step by running `killall defi-init`. One minute later, we should have our masternode running and minting coins.

Expand Down Expand Up @@ -170,5 +170,5 @@ Masternodes can exist in these states:
- `ENABLED` - masternode is in fully operable state, can mint blocks and sign anchors
- `PRE_RESIGNED` - masternode is still operable, but have received a 'resign' transaction and will wait for a special delay to get resigned
- `RESIGNED` - masternode resigned, collateral unlocked and is available to be reclaimed
- `PRE_BANNED` - masternode was caught as a 'criminal' (signing two blocks from parrallel forks on close heights and we got special proofing tx on chain) but still operable (waiting, as in the case of PRE_RESIGNED)
- `PRE_BANNED` - masternode was caught as a 'criminal' (signing two blocks from parallel forks on close heights and we got special proofing tx on chain) but still operable (waiting, as in the case of PRE_RESIGNED)
- `BANNED` - masternode deactivated, collateral unlocked and can be reclaimed (same as RESIGNED, but forced through deactivation)