Skip to content

Commit a647d44

Browse files
committed
doc: update signet documentation related to build directories
1 parent 36ad951 commit a647d44

File tree

1 file changed

+3
-4
lines changed

1 file changed

+3
-4
lines changed

contrib/signet/README.md

+3-4
Original file line numberDiff line numberDiff line change
@@ -23,17 +23,16 @@ miner
2323

2424
You will first need to pick a difficulty target. Since signet chains are primarily protected by a signature rather than proof of work, there is no need to spend as much energy as possible mining, however you may wish to choose to spend more time than the absolute minimum. The calibrate subcommand can be used to pick a target appropriate for your hardware, eg:
2525

26-
cd src/
27-
MINER="../contrib/signet/miner"
28-
GRIND="./bitcoin-util grind"
26+
MINER="./contrib/signet/miner"
27+
GRIND="./build/src/bitcoin-util grind"
2928
$MINER calibrate --grind-cmd="$GRIND"
3029
nbits=1e00f403 for 25s average mining time
3130

3231
It defaults to estimating an nbits value resulting in 25s average time to find a block, but the --seconds parameter can be used to pick a different target, or the --nbits parameter can be used to estimate how long it will take for a given difficulty.
3332

3433
To mine the first block in your custom chain, you can run:
3534

36-
CLI="./bitcoin-cli -conf=mysignet.conf"
35+
CLI="./build/src/bitcoin-cli -conf=mysignet.conf"
3736
ADDR=$($CLI -signet getnewaddress)
3837
NBITS=1e00f403
3938
$MINER --cli="$CLI" generate --grind-cmd="$GRIND" --address="$ADDR" --nbits=$NBITS

0 commit comments

Comments
 (0)