aboutsummaryrefslogtreecommitdiff
path: root/contrib/linearize/README.md
diff options
context:
space:
mode:
Diffstat (limited to 'contrib/linearize/README.md')
-rw-r--r--contrib/linearize/README.md4
1 files changed, 2 insertions, 2 deletions
diff --git a/contrib/linearize/README.md b/contrib/linearize/README.md
index c141c21fb..3ab72c93b 100644
--- a/contrib/linearize/README.md
+++ b/contrib/linearize/README.md
@@ -20,7 +20,7 @@ standalone hash lists but safe to use with linearize-data.py, which will output
the same data no matter which byte format is chosen.
The `linearize-hashes` script requires a connection, local or remote, to a
-JSON-RPC server. Running `dogecoind` or `dogecoin-qt -server` will be sufficient.
+JSON-RPC server. Running `discoind` or `discoin-qt -server` will be sufficient.
## Step 2: Copy local block data
@@ -38,7 +38,7 @@ will be printed.
respectively, to the current time and to the timestamp of the most recent block
written to the script's blockchain.
* `genesis`: The hash of the genesis block in the blockchain.
-* `input`: dogecoind blocks/ directory containing blkNNNNN.dat
+* `input`: discoind blocks/ directory containing blkNNNNN.dat
* `hashlist`: text file containing list of block hashes created by
linearize-hashes.py.
* `max_out_sz`: Maximum size for files created by the `output_file` option.