✅ 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

📝 hebasto opened a pull request: "doc: Update NetBSD Build Guide"
(https://github.com/bitcoin/bitcoin/pull/31586)
This PR:

1. Updates the documented NetBSD version.

2. Adds the optional ZeroMQ package to align the guide with other *BSD systems.

3. Updates the Python version to meet the minimum requirement specified in https://github.com/bitcoin/bitcoin/pull/30527.

4. Suggests to Install [`net/py-zmq`](https://ftp.netbsd.org/pub/pkgsrc/current/pkgsrc/net/py-zmq/index.html) package to enable the `interface_zmq.py` functional test.

5. Fix a formatting issue.

See also the recent NetBSD nightly
...

👍 hebasto approved a pull request: "txmempool: fix typos in comments"
(https://github.com/bitcoin/bitcoin/pull/31584#pullrequestreview-2526353028)
ACK 34e8ee23b83eeecb1c4022b48e7b8db45a60ffdd.

💬 Sjors commented on pull request "rpc: add gettarget , target getmininginfo field and show next block info":
(https://github.com/bitcoin/bitcoin/pull/31583#issuecomment-2566337776)
Added a helper function `NextEmptyBlockIndex`, which also fixes the missing nBits value on mainnet and signet.

💬 jaeheonshim commented on pull request "refactor: Remove redundant edge case in fee rate rounding logic":
(https://github.com/bitcoin/bitcoin/pull/31572#discussion_r1900111243)
Sorry, that `if` statement is unnecessary. I must have missed it.

✅ jaeheonshim closed a pull request: "refactor: Remove redundant edge case in fee rate rounding logic"
(https://github.com/bitcoin/bitcoin/pull/31572)

💬 jaeheonshim commented on pull request "refactor: Remove redundant edge case in fee rate rounding logic":
(https://github.com/bitcoin/bitcoin/pull/31572#issuecomment-2566452453)
What @maflcko said makes sense. I'll do some more investigating.

🤔 tdb3 reviewed a pull request: "rpc: add gettarget , target getmininginfo field and show next block info"
(https://github.com/bitcoin/bitcoin/pull/31583#pullrequestreview-2526474614)
Approach ACK

Planning to test later today as time allows. Left a minor comment, but it could wait until after testing (to avoid churn).

💬 tdb3 commented on pull request "rpc: add gettarget , target getmininginfo field and show next block info":
(https://github.com/bitcoin/bitcoin/pull/31583#discussion_r1900114122)
Let's add release notes for this, `getdifficulty`, and `gettarget`, e.g. something like:

```
Updated RPCs
---
- `getmininginfo` now returns the current target in the `target` field, and a `next` object, which specifies the `height`, `nBits`, `difficulty`, and `target` for the next block.
- `getdifficulty` can now return the difficulty for the next block (rather than the current tip) when calling with the boolean `next` argument set to true.

New RPCs
---
- `gettarget` can be used to r
...

💬 Sjors commented on pull request "rpc: add gettarget , target getmininginfo field and show next block info":
(https://github.com/bitcoin/bitcoin/pull/31583#issuecomment-2566495339)
Added a testnet4 test, which includes the first 2016 real blocks. This takes up 1 MB (IIUC git effectively gzips that into 250kb).

Also added release notes.

I moved the `NextEmptyBlockIndex` helper from `node/miner.h` to `rpc/util.h`.

💬 jaeheonshim commented on issue "Stale code (that has no effect)":
(https://github.com/bitcoin/bitcoin/issues/31558#issuecomment-2566496077)
@maflcko I'd like to work on this issue, but this being my first time contributing to Bitcoin Core, I'm a bit lost. Where should I look to figure out exactly how the rounding for the fee mechanism should be implemented?

💬 Sjors commented on pull request "rpc: add gettarget , target getmininginfo field and show next block info":
(https://github.com/bitcoin/bitcoin/pull/31583#issuecomment-2566509580)
> I moved the `NextEmptyBlockIndex` helper from `node/miner.h` to `rpc/util.h`.

That didn't work, because `rpc/util.cpp` lives in `libbitcoin_common`, while the `UpdateTime` function it calls lives in `libbitcoin_node`. I moved it to `rpc/server_util.{h,cpp}` instead.