🚀 achow101 merged a pull request: "descriptor: remove unreachable verification for `pkh`"
(https://github.com/bitcoin/bitcoin/pull/31555)

💬 ismaelsadeeq commented on pull request "RPC: Add reserve member function to `UniValue` and use it in `getblock` RPC":
(https://github.com/bitcoin/bitcoin/pull/31179#issuecomment-2565964265)
Thanks for taking a look @Eunovo @l0rinc

> could you commit the diff you’ve provided and include the benchmark results in the commit message?

I've added 8d4823b383be4f8cd0152176a4f67b447d29549 For the benchmarks and instead update the PR title with the bench results.

> I ran your benchmarks from https://github.com/bitcoin/bitcoin/pull/31179#issuecomment-2446067820, but I only see a 7% speedup in the TxVerbosity::SHOW_TXID bench - while the rest were exactly the same as before.

I did
...

💬 l0rinc commented on pull request "RPC: Add reserve member function to `UniValue` and use it in `getblock` RPC":
(https://github.com/bitcoin/bitcoin/pull/31179#issuecomment-2565981600)
I can implement my suggestions in separate PRs if you say the RPC speedups would be welcome

💬 tdb3 commented on pull request "rpc: add target to getmininginfo and introduce gettarget":
(https://github.com/bitcoin/bitcoin/pull/31583#discussion_r1899866083)
nit: Since `7fffff0...` is used both here and in `mining_basic.py`, might be worth de-duplicating? Maybe into `test_framework/util.py`?

🤔 tdb3 reviewed a pull request: "rpc: add target to getmininginfo and introduce gettarget"
(https://github.com/bitcoin/bitcoin/pull/31583#pullrequestreview-2526096356)
Approach ACK

Welcome addition

Sanity checked on mainnet (at block 200,000)
```
$ build/src/bitcoin-cli gettarget
00000000000005db8b0000000000000000000000000000000000000000000000
$ build/src/bitcoin-cli getmininginfo
{
"blocks": 200000,
"difficulty": 2864140.507810974,
"target": "00000000000005db8b0000000000000000000000000000000000000000000000",
"networkhashps": 26411459642253.2,
"pooledtx": 0,
"chain": "main",
"warnings": [
"This is a pre-release test build -
...

💬 starius commented on pull request "Extend signetchallenge to set target block spacing":
(https://github.com/bitcoin/bitcoin/pull/29365#issuecomment-2566090827)
Rebased the PR, including https://github.com/bitcoin/bitcoin/pull/31468 and resolving the conflict in `test/functional/feature_signet.py`.

💬 starius commented on pull request "Extend signetchallenge to set target block spacing":
(https://github.com/bitcoin/bitcoin/pull/29365#discussion_r1899891585)
Thanks for the proposal! I reworked the change of feature_signet.py test. Instead of modifying the existing test case, I added a new one with the wrapped signet challenge.

📝 starius opened a pull request: "txmempool: fix typos in comments"
(https://github.com/bitcoin/bitcoin/pull/31584)
Fixed typos identified by codespell lint in CI.

🤔 Pitan1993 requested changes to a pull request: "scripted-diff: Type-safe settings retrieval"
(https://github.com/bitcoin/bitcoin/pull/31260#pullrequestreview-2526132864)
2024-12-14T00:04:24.9747967Z Cleaning up orphan processes

💬 Pitan1993 commented on pull request "scripted-diff: Type-safe settings retrieval":
(https://github.com/bitcoin/bitcoin/pull/31260#issuecomment-2566096091)
e12edf7661384f593b5868b3f3374613773019d9

📝 mikeknack86 opened a pull request: "Create docker-image.yml"
(https://github.com/bitcoin/bitcoin/pull/31585)
<!--
*** Please remove the following help text before submitting: ***

Pull requests without a rationale and clear improvement may be closed
immediately.

GUI-related pull requests should be opened against
https://github.com/bitcoin-core/gui
first. See CONTRIBUTING.md
-->

<!--
Please provide clear motivation for your patch and explain how it improves
Bitcoin Core user experience or Bitcoin Core developer experience
significantly:

* Any test improvements or new tests that improv
...

🤔 mikeknack86 reviewed a pull request: "Create docker-image.yml"
(https://github.com/bitcoin/bitcoin/pull/31585#pullrequestreview-2526149918)
[](url)

✅ achow101 closed a pull request: "Create docker-image.yml"
(https://github.com/bitcoin/bitcoin/pull/31585)

📝 achow101 locked a pull request: "."
(https://github.com/bitcoin/bitcoin/pull/31585)
<!--
*** Please remove the following help text before submitting: ***

Pull requests without a rationale and clear improvement may be closed
immediately.

GUI-related pull requests should be opened against
https://github.com/bitcoin-core/gui
first. See CONTRIBUTING.md
-->

<!--
Please provide clear motivation for your patch and explain how it improves
Bitcoin Core user experience or Bitcoin Core developer experience
significantly:

* Any test improvements or new tests that improv
...

💬 davidgumberg commented on pull request "refactor: Remove redundant edge case in fee rate rounding logic":
(https://github.com/bitcoin/bitcoin/pull/31572#discussion_r1899948765)
Why the second `if` statement?

💬 hebasto commented on pull request "doc: Install `net/py-pyzmq` port on FreeBSD for `interface_zmq.py`":
(https://github.com/bitcoin/bitcoin/pull/31526#issuecomment-2566279518)
Also see the recent nightly builds:
- https://github.com/hebasto/bitcoin-core-nightly/actions/runs/12554769828/job/35003929128
- https://github.com/hebasto/bitcoin-core-nightly/actions/runs/12554769828/job/35003929381

💬 Sjors commented on pull request "rpc: add gettarget , target getmininginfo field and show next block info":
(https://github.com/bitcoin/bitcoin/pull/31583#discussion_r1900019991)
Done and also added test coverage for nBits.

💬 Sjors commented on pull request "rpc: add gettarget , target getmininginfo field and show next block info":
(https://github.com/bitcoin/bitcoin/pull/31583#issuecomment-2566298895)
Rebased and split things across more commits.

I also realized that `getmininginfo`, `getdifficulty` and `gettarget` always refer to the tip, rather than the upcoming block which is what miners actually care about. So added a `next` argument to `getdifficulty` and `gettarget` and a `next` object to `getmininginfo`. You'll have to test this manually, because regtest doesn't have difficulty adjustment.

I might push a test that uses the testnet4 genesis block and the rule that difficulty reset
...

💬 maflcko commented on pull request "doc: Install `net/py-pyzmq` port on FreeBSD for `interface_zmq.py`":
(https://github.com/bitcoin/bitcoin/pull/31526#issuecomment-2566305211)
lgtm ACK 0a76c292ac8fa29166a7ec6efda1fafce86af0d3

💬 maflcko commented on pull request "refactor: Remove redundant edge case in fee rate rounding logic":
(https://github.com/bitcoin/bitcoin/pull/31572#issuecomment-2566313057)
> Addresses #31558. This fix improves code readability.

I don't think it does. Someone will need to investigate why the behavior is not symmetric for negative feerates and whether making it symmetric is a bugfix. See https://github.com/bitcoin/bitcoin/issues/31558#issuecomment-2560984394:

> I haven't checked if such a change is a bugfix or behavior change for prioritisetransaction, so it would be good to check that as well.

💬 maflcko commented on pull request "txmempool: fix typos in comments":
(https://github.com/bitcoin/bitcoin/pull/31584#issuecomment-2566317181)
lgtm ACK 34e8ee23b83eeecb1c4022b48e7b8db45a60ffdd