👍 ryanofsky approved a pull request: "Introduce waitTipChanged() mining interface, replace RPCNotifyBlockChange, drop CRPCSignals & g_best_block"
(https://github.com/bitcoin/bitcoin/pull/30409#pullrequestreview-2280948816)
Code review ACK 6c419285720fe5a954e01f09cbe053a0f51bef47. Since last review just rebased, added suggested m_tip_block_cv notify call on shutdown, and added two new commits dropping g_best_block.
(https://github.com/bitcoin/bitcoin/pull/30409#pullrequestreview-2280948816)
Code review ACK 6c419285720fe5a954e01f09cbe053a0f51bef47. Since last review just rebased, added suggested m_tip_block_cv notify call on shutdown, and added two new commits dropping g_best_block.
💬 achow101 commented on pull request "cli: restrict multiple exclusive argument usage in bitcoin-cli":
(https://github.com/bitcoin/bitcoin/pull/30148#issuecomment-2329705872)
ACK c8e6771af002eaf15567794fcdc57fdb0e3fb140
(https://github.com/bitcoin/bitcoin/pull/30148#issuecomment-2329705872)
ACK c8e6771af002eaf15567794fcdc57fdb0e3fb140
👍 ryanofsky approved a pull request: "init: fix init fatal error on invalid negated option value"
(https://github.com/bitcoin/bitcoin/pull/30684#pullrequestreview-2280954609)
Code review ACK ee47ca29d6ef55650a0af63bca817c5d494f31ef, just adding the suggested test since last review
(https://github.com/bitcoin/bitcoin/pull/30684#pullrequestreview-2280954609)
Code review ACK ee47ca29d6ef55650a0af63bca817c5d494f31ef, just adding the suggested test since last review
💬 achow101 commented on pull request "fix: increase consistency of rpcauth parsing":
(https://github.com/bitcoin/bitcoin/pull/30401#issuecomment-2329711694)
ACK 27c976d11a68d66db97d9a7a30c6a6a71c6ab586
(https://github.com/bitcoin/bitcoin/pull/30401#issuecomment-2329711694)
ACK 27c976d11a68d66db97d9a7a30c6a6a71c6ab586
💬 ryanofsky commented on pull request "init: fix init fatal error on invalid negated option value":
(https://github.com/bitcoin/bitcoin/pull/30684#issuecomment-2329714304)
May want to update the pr description to say this bug also when happens passing a double negated value, since the not_a_boolean case is really just a special case of that
(https://github.com/bitcoin/bitcoin/pull/30684#issuecomment-2329714304)
May want to update the pr description to say this bug also when happens passing a double negated value, since the not_a_boolean case is really just a special case of that
💬 TheCharlatan commented on pull request "kernel: Create usable static kernel library":
(https://github.com/bitcoin/bitcoin/pull/30814#issuecomment-2329722680)
Not sure yet why the CI fails, will investigate and leave this in draft for now. If it is something cmake version related, I'll probably end up abandoning this approach and instead try to get the installation of all the required libraries working.
(https://github.com/bitcoin/bitcoin/pull/30814#issuecomment-2329722680)
Not sure yet why the CI fails, will investigate and leave this in draft for now. If it is something cmake version related, I'll probably end up abandoning this approach and instead try to get the installation of all the required libraries working.
📝 TheCharlatan converted_to_draft a pull request: "kernel: Create usable static kernel library"
(https://github.com/bitcoin/bitcoin/pull/30814)
Since the move to cmake, the kernel static library that is installed after a cmake --install build is unusable. It lacks symbols for the internal libraries, besides those defined in the kernel library target.
Fix this by explicitly adding the required object files of its dependencies to the library instead of relying on additional linker
steps.
A generator expression guard is added to ensure that libraries that are not compatible with the target architecture are not compiled. It is not cl
...
(https://github.com/bitcoin/bitcoin/pull/30814)
Since the move to cmake, the kernel static library that is installed after a cmake --install build is unusable. It lacks symbols for the internal libraries, besides those defined in the kernel library target.
Fix this by explicitly adding the required object files of its dependencies to the library instead of relying on additional linker
steps.
A generator expression guard is added to ensure that libraries that are not compatible with the target architecture are not compiled. It is not cl
...
⚠️ somethingbeta opened an issue: "Test Framework - test_framework.test_node.FailedToStartError: No RPC credentials"
(https://github.com/bitcoin/bitcoin/issues/30818)
### Is there an existing issue for this?
- [X] I have searched the existing issues
### Current behaviour
On execution bitcoind fails to start and logs Failed to start error. Have pasted logs into the logs section.
It looks as though there is some rpc config required for this to run, but have not found a way to specify whats required. When i hard code a username/password in utils.py .. fails with Connection Refused.
**Example Command**
`
python functional/feature_rbf.py --logleve
...
(https://github.com/bitcoin/bitcoin/issues/30818)
### Is there an existing issue for this?
- [X] I have searched the existing issues
### Current behaviour
On execution bitcoind fails to start and logs Failed to start error. Have pasted logs into the logs section.
It looks as though there is some rpc config required for this to run, but have not found a way to specify whats required. When i hard code a username/password in utils.py .. fails with Connection Refused.
**Example Command**
`
python functional/feature_rbf.py --logleve
...
📝 edilmedeiros converted_to_draft a pull request: "contrib/signet/miner: increase miner search space"
(https://github.com/bitcoin/bitcoin/pull/30130)
The miner script will call `bitcoin-util grind` to compute PoW which will try to exhaust the block's nonce field and fail if it can't find a valid hash. This behavior does not appear for low difficulty chains, but make the miner unusable for higher difficulty settings.
We capture `bitcoin-util grind` failure, build a new block header by changing the block time and try to grind again.
Fixes #30102.
## How this was tested
This is a follow-up from #30091 and #30102.
I've started a ne
...
(https://github.com/bitcoin/bitcoin/pull/30130)
The miner script will call `bitcoin-util grind` to compute PoW which will try to exhaust the block's nonce field and fail if it can't find a valid hash. This behavior does not appear for low difficulty chains, but make the miner unusable for higher difficulty settings.
We capture `bitcoin-util grind` failure, build a new block header by changing the block time and try to grind again.
Fixes #30102.
## How this was tested
This is a follow-up from #30091 and #30102.
I've started a ne
...
💬 pablomartin4btc commented on pull request "rpc: dumptxoutset height parameter follow-ups (29553)":
(https://github.com/bitcoin/bitcoin/pull/30808#issuecomment-2329740537)
post-merge tACK https://github.com/bitcoin/bitcoin/commit/a3108a7c5692d137b70b8442b4741936277e89be
(manipulated `maybe_stats` as suggested and other manual tests: rolling back, shutdown node during `invalidate` & `reconsider`)
(https://github.com/bitcoin/bitcoin/pull/30808#issuecomment-2329740537)
post-merge tACK https://github.com/bitcoin/bitcoin/commit/a3108a7c5692d137b70b8442b4741936277e89be
(manipulated `maybe_stats` as suggested and other manual tests: rolling back, shutdown node during `invalidate` & `reconsider`)
💬 edilmedeiros commented on pull request "contrib/signet/miner: increase miner search space":
(https://github.com/bitcoin/bitcoin/pull/30130#issuecomment-2329741824)
Returned to draft so I can refactor this PR on top of #28417 recently merged.
(https://github.com/bitcoin/bitcoin/pull/30130#issuecomment-2329741824)
Returned to draft so I can refactor this PR on top of #28417 recently merged.
💬 russeree commented on issue "Testnet4 consensus failure due to timewarp related "softfork"":
(https://github.com/bitcoin/bitcoin/issues/30786#issuecomment-2329743955)
> > I think there is a small risk, that we will see a huge double-spending attempt in testnet4, because after block 00000000000000263393ce5f648afd53676f13d360cc9f264b89351623bf1242, there are transactions in the old chain, which are not picked by nodes, mining the new chain. Which means, that suddenly, when the deep reorg will revert hundreds of blocks, all of those transactions will suddenly become unconfirmed.
> > So, if anyone has any coins, which were received after block number 42335, then
...
(https://github.com/bitcoin/bitcoin/issues/30786#issuecomment-2329743955)
> > I think there is a small risk, that we will see a huge double-spending attempt in testnet4, because after block 00000000000000263393ce5f648afd53676f13d360cc9f264b89351623bf1242, there are transactions in the old chain, which are not picked by nodes, mining the new chain. Which means, that suddenly, when the deep reorg will revert hundreds of blocks, all of those transactions will suddenly become unconfirmed.
> > So, if anyone has any coins, which were received after block number 42335, then
...
🚀 achow101 merged a pull request: "cli: restrict multiple exclusive argument usage in bitcoin-cli"
(https://github.com/bitcoin/bitcoin/pull/30148)
(https://github.com/bitcoin/bitcoin/pull/30148)
🤔 BrandonOdiwuor reviewed a pull request: "test: Use std::span and std::string_view for raw data"
(https://github.com/bitcoin/bitcoin/pull/30796#pullrequestreview-2281002924)
Concept ACK
(https://github.com/bitcoin/bitcoin/pull/30796#pullrequestreview-2281002924)
Concept ACK
💬 achow101 commented on pull request "fuzz: make FuzzedDataProvider usage deterministic":
(https://github.com/bitcoin/bitcoin/pull/29043#issuecomment-2329761067)
ACK 01960c53c7d71c70792abe19413315768dc2275a
(https://github.com/bitcoin/bitcoin/pull/29043#issuecomment-2329761067)
ACK 01960c53c7d71c70792abe19413315768dc2275a
🚀 achow101 merged a pull request: "fuzz: make FuzzedDataProvider usage deterministic"
(https://github.com/bitcoin/bitcoin/pull/29043)
(https://github.com/bitcoin/bitcoin/pull/29043)
💬 achow101 commented on issue "Testnet4 consensus failure due to timewarp related "softfork"":
(https://github.com/bitcoin/bitcoin/issues/30786#issuecomment-2329788335)
> My question is why did we merge code into Core that forked T4 without contacting any of the larger swaths of hashrate and or having the HR to outrun the previously canonical chain?
There was no indication at the time that anyone would mine blocks that were outside of MAX_TIMEWARP of 600. And generally, the assumption is that if someone is running code from an unmerged PR, they should be following it and be aware that it might majorly change before it is merged.
(https://github.com/bitcoin/bitcoin/issues/30786#issuecomment-2329788335)
> My question is why did we merge code into Core that forked T4 without contacting any of the larger swaths of hashrate and or having the HR to outrun the previously canonical chain?
There was no indication at the time that anyone would mine blocks that were outside of MAX_TIMEWARP of 600. And generally, the assumption is that if someone is running code from an unmerged PR, they should be following it and be aware that it might majorly change before it is merged.
💬 achow101 commented on pull request "test: fixing failing system_tests/run_command under some Locales":
(https://github.com/bitcoin/bitcoin/pull/30788#issuecomment-2329801442)
ACK ae48a22a3df086fb59843b7b814619ed5df7557b
(https://github.com/bitcoin/bitcoin/pull/30788#issuecomment-2329801442)
ACK ae48a22a3df086fb59843b7b814619ed5df7557b
✅ achow101 closed an issue: "test: "system_tests/run_command" unit test fails with different locale"
(https://github.com/bitcoin/bitcoin/issues/30608)
(https://github.com/bitcoin/bitcoin/issues/30608)
🚀 achow101 merged a pull request: "test: fixing failing system_tests/run_command under some Locales"
(https://github.com/bitcoin/bitcoin/pull/30788)
(https://github.com/bitcoin/bitcoin/pull/30788)