diff options
| author | merge-script <fanquake@gmail.com> | 2024-10-16 16:58:31 +0100 |
|---|---|---|
| committer | merge-script <fanquake@gmail.com> | 2024-10-16 16:58:31 +0100 |
| commit | 479715e9db039e881d27c6fa9bb85b81e6b375e7 (patch) | |
| tree | d4aa1ad075a771952793bd76b19113362893734a | |
| parent | 99e041f86fde4219c0568e6c0e724a76ee398112 (diff) | |
| parent | a647d4400d55558735f102988e84eedc39b3affa (diff) | |
Merge bitcoin/bitcoin#30996: doc: update signet documentation related to build directories
a647d4400d55558735f102988e84eedc39b3affa doc: update signet documentation related to build directories (Torkel Rogstad)
Pull request description:
While setting up my own signet I noticed that the binary paths in the documentation for this is out of date, after build artifacts moved to the `build` directory. This PR mimics what happened in #30741
ACKs for top commit:
maflcko:
lgtm ACK a647d4400d55558735f102988e84eedc39b3affa
pablomartin4btc:
ACK a647d4400d55558735f102988e84eedc39b3affa
tdb3:
Code review and light test ACK a647d4400d55558735f102988e84eedc39b3affa
Tree-SHA512: ac7c3806e0ff65860c41d7b7bdad538368d8a6d8d289c10f9714804f963bafd3a9658301b6697f110f5462a92826b62770963508d5eebf88bf9a0a8442d9f72d
| -rw-r--r-- | contrib/signet/README.md | 7 |
1 files changed, 3 insertions, 4 deletions
diff --git a/contrib/signet/README.md b/contrib/signet/README.md index 706b296c54..5fcd8944e6 100644 --- a/contrib/signet/README.md +++ b/contrib/signet/README.md @@ -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 |