mirror of
https://github.com/ElementsProject/elements.git
synced 2026-08-15 12:51:00 +02:00
Merge 479715e9db into merged_master (Bitcoin PR bitcoin/bitcoin#30996)
This commit is contained in:
commit
30a075180c
1 changed files with 3 additions and 4 deletions
|
|
@ -23,9 +23,8 @@ miner
|
|||
|
||||
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:
|
||||
|
||||
cd src/
|
||||
MINER="../contrib/signet/miner"
|
||||
GRIND="./bitcoin-util grind"
|
||||
MINER="./contrib/signet/miner"
|
||||
GRIND="./build/src/bitcoin-util grind"
|
||||
$MINER calibrate --grind-cmd="$GRIND"
|
||||
nbits=1e00f403 for 25s average mining time
|
||||
|
||||
|
|
@ -33,7 +32,7 @@ It defaults to estimating an nbits value resulting in 25s average time to find a
|
|||
|
||||
To mine the first block in your custom chain, you can run:
|
||||
|
||||
CLI="./bitcoin-cli -conf=mysignet.conf"
|
||||
CLI="./build/src/bitcoin-cli -conf=mysignet.conf"
|
||||
ADDR=$($CLI -signet getnewaddress)
|
||||
NBITS=1e00f403
|
||||
$MINER --cli="$CLI" generate --grind-cmd="$GRIND" --address="$ADDR" --nbits=$NBITS
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue