โ ๏ธ lilin998 reopened an issue: "signet /README.md"
(https://github.com/bitcoin/bitcoin/issues/31798)
MINER="./contrib/signet/miner"
GRIND="./build/src/bitcoin-util grind"
$MINER calibrate --grind-cmd="$GRIND"
nbits=1e00f403 for 25s average mining time
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
PSBT signing failed
How to solve this problem PSBT signing failed
  (https://github.com/bitcoin/bitcoin/issues/31798)
MINER="./contrib/signet/miner"
GRIND="./build/src/bitcoin-util grind"
$MINER calibrate --grind-cmd="$GRIND"
nbits=1e00f403 for 25s average mining time
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
PSBT signing failed
How to solve this problem PSBT signing failed
๐ฌ lilin998 commented on issue "signet /README.md":
(https://github.com/bitcoin/bitcoin/issues/31798#issuecomment-2635526553)
> > PSBT ็ญพๅๅคฑ่ดฅ
>
> ๅฝ้ฑๅ ๆฒกๆ็ง้ฅๆฅ็ญพ็ฝฒๆปก่ถณๆๆ็ๆๆ็ญพๅๅๆถ๏ผๅฐฑไผๅ็่ฟ็งๆ ๅต
root@iZt4n4iibil3u7hsxshmuwZ:~/bitcoin# bitcoin-cli -signet -conf=/root/bitcoin/mysignet.conf getwalletinfo
{
"walletname": "mysignet_wallet",
"walletversion": 169900,
"format": "sqlite",
"balance": 0.00000000,
"unconfirmed_balance": 0.00000000,
"immature_balance": 0.00000000,
"txcount": 4,
"keypoolsize": 4000,
"keypoolsize_hd_internal": 3999,
"paytxfee": 0.00000000,
"private_keys_enabled": true,
"avoid_reuse": false,
"
...
  (https://github.com/bitcoin/bitcoin/issues/31798#issuecomment-2635526553)
> > PSBT ็ญพๅๅคฑ่ดฅ
>
> ๅฝ้ฑๅ ๆฒกๆ็ง้ฅๆฅ็ญพ็ฝฒๆปก่ถณๆๆ็ๆๆ็ญพๅๅๆถ๏ผๅฐฑไผๅ็่ฟ็งๆ ๅต
root@iZt4n4iibil3u7hsxshmuwZ:~/bitcoin# bitcoin-cli -signet -conf=/root/bitcoin/mysignet.conf getwalletinfo
{
"walletname": "mysignet_wallet",
"walletversion": 169900,
"format": "sqlite",
"balance": 0.00000000,
"unconfirmed_balance": 0.00000000,
"immature_balance": 0.00000000,
"txcount": 4,
"keypoolsize": 4000,
"keypoolsize_hd_internal": 3999,
"paytxfee": 0.00000000,
"private_keys_enabled": true,
"avoid_reuse": false,
"
...
๐ฌ lilin998 commented on issue "signet /README.md":
(https://github.com/bitcoin/bitcoin/issues/31798#issuecomment-2635527325)
This seems to have a private key.
  (https://github.com/bitcoin/bitcoin/issues/31798#issuecomment-2635527325)
This seems to have a private key.
๐ฌ pinheadmz commented on issue "signet /README.md":
(https://github.com/bitcoin/bitcoin/issues/31798#issuecomment-2635528630)
do you have the correct `signetchallenge` in `bitcoin.conf`?
  (https://github.com/bitcoin/bitcoin/issues/31798#issuecomment-2635528630)
do you have the correct `signetchallenge` in `bitcoin.conf`?
๐ฌ lilin998 commented on issue "signet /README.md":
(https://github.com/bitcoin/bitcoin/issues/31798#issuecomment-2635529178)
> ไฝ ๆๆญฃ็กฎ็`signetchallenge`ๅ`bitcoin.conf`๏ผ
> do you have the correct `signetchallenge` in `bitcoin.conf`?
server=1
daemon=1
txindex=1
[signet]
rpcuser=myuser
rpcpassword=mypassword
rpcallowip=0.0.0.0/0
rpcbind=127.0.0.1
rpcport=38332
signet=1
  (https://github.com/bitcoin/bitcoin/issues/31798#issuecomment-2635529178)
> ไฝ ๆๆญฃ็กฎ็`signetchallenge`ๅ`bitcoin.conf`๏ผ
> do you have the correct `signetchallenge` in `bitcoin.conf`?
server=1
daemon=1
txindex=1
[signet]
rpcuser=myuser
rpcpassword=mypassword
rpcallowip=0.0.0.0/0
rpcbind=127.0.0.1
rpcport=38332
signet=1
๐ฌ pinheadmz commented on issue "signet /README.md":
(https://github.com/bitcoin/bitcoin/issues/31798#issuecomment-2635536220)
What are you trying to accomplish? If you want to start a brand new signet chain you need to add `signetchallenge=...` in `bitcoin.conf` with a BIP325 challenge: https://github.com/bitcoin/bips/blob/master/bip-0325.mediawiki#specification
  (https://github.com/bitcoin/bitcoin/issues/31798#issuecomment-2635536220)
What are you trying to accomplish? If you want to start a brand new signet chain you need to add `signetchallenge=...` in `bitcoin.conf` with a BIP325 challenge: https://github.com/bitcoin/bips/blob/master/bip-0325.mediawiki#specification
๐ฌ lilin998 commented on issue "signet /README.md":
(https://github.com/bitcoin/bitcoin/issues/31798#issuecomment-2635538514)
 
> What are you trying to accomplish? If you want to start a brand new signet chain you need to add `signetchallenge=...` in `bitcoin.conf` with a BIP325 challenge: https://github.com/bitcoin/bips/blob/master/bip-0325.mediawiki#specification
I want to dig up some sbtc test coins
  (https://github.com/bitcoin/bitcoin/issues/31798#issuecomment-2635538514)
> What are you trying to accomplish? If you want to start a brand new signet chain you need to add `signetchallenge=...` in `bitcoin.conf` with a BIP325 challenge: https://github.com/bitcoin/bips/blob/master/bip-0325.mediawiki#specification
I want to dig up some sbtc test coins
๐ฌ pinheadmz commented on issue "signet /README.md":
(https://github.com/bitcoin/bitcoin/issues/31798#issuecomment-2635540094)
You will not be able to generate blocks on the default signet chain because you do not have the correct private key. You can try one of the other methods listed here: https://github.com/bitcoin/bitcoin/blob/master/contrib/signet/README.md
  (https://github.com/bitcoin/bitcoin/issues/31798#issuecomment-2635540094)
You will not be able to generate blocks on the default signet chain because you do not have the correct private key. You can try one of the other methods listed here: https://github.com/bitcoin/bitcoin/blob/master/contrib/signet/README.md
๐ ryanofsky approved a pull request: "depends: Avoid hardcoding `host_prefix` in toolchain file"
(https://github.com/bitcoin/bitcoin/pull/31358#pullrequestreview-2594540306)
Code review ACK d9c8aacce38ab593ea9277976eb64ccadd7d062f
  (https://github.com/bitcoin/bitcoin/pull/31358#pullrequestreview-2594540306)
Code review ACK d9c8aacce38ab593ea9277976eb64ccadd7d062f
โ
 ryanofsky closed a pull request: "ci: build multiprocess on most jobs"
(https://github.com/bitcoin/bitcoin/pull/30975)
  (https://github.com/bitcoin/bitcoin/pull/30975)
๐ ryanofsky reopened a pull request: "ci: build multiprocess on most jobs"
(https://github.com/bitcoin/bitcoin/pull/30975)
This builds most of the CI jobs with multiprocess enabled.
Two jobs run the functional test suite, one with depends and one with the regular build.
The Windows job does not use multiprocess since that's not supported yet.
The previous version of this PR changed the `depends` system to build libmultiprocess by default as one of the final steps for #31098 - but based discussion here and on IRC it was decided it's too early to ship it.
  (https://github.com/bitcoin/bitcoin/pull/30975)
This builds most of the CI jobs with multiprocess enabled.
Two jobs run the functional test suite, one with depends and one with the regular build.
The Windows job does not use multiprocess since that's not supported yet.
The previous version of this PR changed the `depends` system to build libmultiprocess by default as one of the final steps for #31098 - but based discussion here and on IRC it was decided it's too early to ship it.
๐ฌ luke-jr commented on pull request "multiprocess: Add libmultiprocess git subtree":
(https://github.com/bitcoin/bitcoin/pull/31741#issuecomment-2635647339)
Concept NACK: there's no rationale for why this can't always be external.
  (https://github.com/bitcoin/bitcoin/pull/31741#issuecomment-2635647339)
Concept NACK: there's no rationale for why this can't always be external.
โ ๏ธ JirA44 opened an issue: "Anticipation quantum attack ; post quantum security"
(https://github.com/bitcoin/bitcoin/issues/31799)
### Please describe the feature you'd like to see added.
Post-quantum cryptocurrencies are an emerging field that aims to secure transactions and blockchains against attacks by quantum computers. The latter, thanks to their exponential computing power, could break the classic cryptographic systems used today (such as RSA, ECC and ECDSA) and compromise the security of blockchains.
Why post-quantum cryptos?
Blockchains mainly use two cryptographic mechanisms vulnerable to quantum computers:
  
...
  (https://github.com/bitcoin/bitcoin/issues/31799)
### Please describe the feature you'd like to see added.
Post-quantum cryptocurrencies are an emerging field that aims to secure transactions and blockchains against attacks by quantum computers. The latter, thanks to their exponential computing power, could break the classic cryptographic systems used today (such as RSA, ECC and ECDSA) and compromise the security of blockchains.
Why post-quantum cryptos?
Blockchains mainly use two cryptographic mechanisms vulnerable to quantum computers:
...
๐ฌ luke-jr commented on pull request "rpc: Ensure -debug=0/none behaves consistently with -nodebug":
(https://github.com/bitcoin/bitcoin/pull/31767#discussion_r1942217889)
PR title and commit message too, please
  (https://github.com/bitcoin/bitcoin/pull/31767#discussion_r1942217889)
PR title and commit message too, please
๐ฌ darosior commented on pull request "Double check all block rules in `ConnectBlock`, not only `CheckBlock`":
(https://github.com/bitcoin/bitcoin/pull/31792#issuecomment-2635662333)
> I seem to have a problem running IBD with this change @ [dd2714e](https://github.com/bitcoin/bitcoin/commit/dd2714ed13eea3591162dbade8132ff517ca5509), which I have not investigated yet:
This is because we'd now perform the checkpoints check twice, but it'd fail the second time since a checkpoint with a higher height would already be in the index. Instead of introducing more complexity there i rebased on top of #31649.
> `feature_unsupported_utxo_db.py` fails (times out)
This was faili
...
  (https://github.com/bitcoin/bitcoin/pull/31792#issuecomment-2635662333)
> I seem to have a problem running IBD with this change @ [dd2714e](https://github.com/bitcoin/bitcoin/commit/dd2714ed13eea3591162dbade8132ff517ca5509), which I have not investigated yet:
This is because we'd now perform the checkpoints check twice, but it'd fail the second time since a checkpoint with a higher height would already be in the index. Instead of introducing more complexity there i rebased on top of #31649.
> `feature_unsupported_utxo_db.py` fails (times out)
This was faili
...
โ
 espi3 closed a pull request: "doc: Add test coverage troubleshooting tip"
(https://github.com/bitcoin/bitcoin/pull/31755)
  (https://github.com/bitcoin/bitcoin/pull/31755)
๐ฌ espi3 commented on pull request "doc: Add test coverage troubleshooting tip":
(https://github.com/bitcoin/bitcoin/pull/31755#issuecomment-2635680925)
Closing, as the troubleshooting tips in this PR are too narrow. I ran the same commands on MacOS and got an entirely different set of lcov errors.
  (https://github.com/bitcoin/bitcoin/pull/31755#issuecomment-2635680925)
Closing, as the troubleshooting tips in this PR are too narrow. I ran the same commands on MacOS and got an entirely different set of lcov errors.
๐ฌ ryanofsky commented on pull request "multiprocess: Add libmultiprocess git subtree":
(https://github.com/bitcoin/bitcoin/pull/31741#issuecomment-2635697258)
> Concept NACK: there's no rationale for why this can't always be external.
FWIW, I agree with you and want this to always be external. I personally find it more convenient to work on the library in its standalone git repository, and think cmake's `find_package` mechanism is a cleaner and easier to maintain form of integration than the `add_subdirectory` trick used in this PR. So this PR intentionally does not remove any ability to use the library externally, and it makes git subtree a pure m
...
  (https://github.com/bitcoin/bitcoin/pull/31741#issuecomment-2635697258)
> Concept NACK: there's no rationale for why this can't always be external.
FWIW, I agree with you and want this to always be external. I personally find it more convenient to work on the library in its standalone git repository, and think cmake's `find_package` mechanism is a cleaner and easier to maintain form of integration than the `add_subdirectory` trick used in this PR. So this PR intentionally does not remove any ability to use the library externally, and it makes git subtree a pure m
...
๐ฌ ryanofsky commented on pull request "multiprocess: Add libmultiprocess git subtree":
(https://github.com/bitcoin/bitcoin/pull/31741#issuecomment-2635727935)
Rebased b4d397903d652bae1497140775591f755d857e65 -> 99b7b857d3b8b9ce9bd7501e2480583369740c55 ([`pr/subtree.7`](https://github.com/ryanofsky/bitcoin/commits/pr/subtree.7) -> [`pr/subtree.8`](https://github.com/ryanofsky/bitcoin/commits/pr/subtree.8), [compare](https://github.com/ryanofsky/bitcoin/compare/pr/subtree.7-rebase..pr/subtree.8)) with some more fixes for downstream PR #30975 needed after switching depends build from `find_package` to `add_subdirectory`. Also includes a fix for guix mult
...
  (https://github.com/bitcoin/bitcoin/pull/31741#issuecomment-2635727935)
Rebased b4d397903d652bae1497140775591f755d857e65 -> 99b7b857d3b8b9ce9bd7501e2480583369740c55 ([`pr/subtree.7`](https://github.com/ryanofsky/bitcoin/commits/pr/subtree.7) -> [`pr/subtree.8`](https://github.com/ryanofsky/bitcoin/commits/pr/subtree.8), [compare](https://github.com/ryanofsky/bitcoin/compare/pr/subtree.7-rebase..pr/subtree.8)) with some more fixes for downstream PR #30975 needed after switching depends build from `find_package` to `add_subdirectory`. Also includes a fix for guix mult
...