📝 Sjors opened a pull request: "test: round difficulty and networkhashps"
(https://github.com/bitcoin/bitcoin/pull/32725)
Both are rational numbers. Client software should only use them to display information to humans. Followup calculations should use the underlying values such as target.

Therefore it's not necessary to test the handling of these floating point values. Round them down to avoid spurious test failures.

Fixes #32515

💬 Sjors commented on issue "test: failure in `mining_basic.py` AssertionError: not(4.656542373906924E-10 == 4.656542373906925E-10)":
(https://github.com/bitcoin/bitcoin/issues/32515#issuecomment-2961959561)
#32725 should fix this

💬 Sjors commented on pull request "test: round difficulty and networkhashps":
(https://github.com/bitcoin/bitcoin/pull/32725#issuecomment-2961968599)
Note that `mining_mainnet.py` uses round difficulty values (1 and 4) so it shouldn't have this issue.

📝 scott-weeden opened a pull request: "Add initial OpenAPI/Swagger specification for Bitcoin Core RPC and REST interfaces (issue #29912) "
(https://github.com/bitcoin/bitcoin/pull/32726)

## Motivation

Currently, (almost) all clients manually implement the Bitcoin Core RPC API, which leads to:
- Accidental implementation bugs (e.g., unit mistakes such as vB vs BTC/kvB)
- Difficulty maintaining clients as the API evolves
- Increased effort to implement clients in new programming languages

There is no formal, machine-readable specification of the RPC API. Existing documentation is not sufficient for code generation or type-safe client implementations. See discussion in #
...

💬 maflcko commented on pull request "wallet, rpc: Remove deprecated balances from getwalletinfo and getunconfirmedbalance":
(https://github.com/bitcoin/bitcoin/pull/32721#discussion_r2139713359)
I think back when I deprecated this, the legacy wallet allowed for mine and watch_only dicts in the getbalances. so listing one but not the other here was confusing. however, now that descriptor wallets are required, this is no longer the case. Seems fine to remove or un-deprecate. No strong opinion.

💬 maflcko commented on pull request "wallet, rpc: Remove deprecated balances from getwalletinfo and getunconfirmedbalance":
(https://github.com/bitcoin/bitcoin/pull/32721#discussion_r2139700994)
lgtm. Seems confusing to have a single inconsistent RPC that mirrors a single field of another RPC

💬 jurraca commented on pull request "Embed default ASMap as binary dump header file":
(https://github.com/bitcoin/bitcoin/pull/28792#issuecomment-2962177367)
> How quickly does the data degrade?

ran some numbers, counting by the number of addresses within networks, and diff'ing month to month, the ASmap from Dec 1 to Apr 1 drifted about 5%:
```
IPv4 drift from Dec 1
Jan 1: 1.40%
Feb 1: 3.72%
Mar 1: 4.90%
Apr 1: 5.23%

IPv6 drift from Dec 1
Jan 1: 2.04%
Feb 1: 4.29%
Mar 1: 5.23%
Apr 1: 5.74%
```
Method: running `python3 contrib/asmap/asmap-tool.py diff map1.txt map2.txt` which outputs the total count of addresses changed between the t
...

📝 vasild opened a pull request: "doc: add release notes for #32425"
(https://github.com/bitcoin/bitcoin/pull/32727)
Add release notes for https://github.com/bitcoin/bitcoin/pull/32425.

💬 vasild commented on pull request "config: allow setting -proxy per network":
(https://github.com/bitcoin/bitcoin/pull/32425#issuecomment-2962235283)
> Needs release note?

Right. Done in https://github.com/bitcoin/bitcoin/pull/32727

✅ scott-weeden closed a pull request: "Add initial OpenAPI/Swagger specification for Bitcoin Core RPC and REST interfaces (issue #29912)"
(https://github.com/bitcoin/bitcoin/pull/32726)

📝 scott-weeden reopened a pull request: "Add initial OpenAPI/Swagger specification for Bitcoin Core RPC and REST interfaces (issue #29912)"
(https://github.com/bitcoin/bitcoin/pull/32726)

## Motivation

Currently, (almost) all clients manually implement the Bitcoin Core RPC API, which leads to:
- Accidental implementation bugs (e.g., unit mistakes such as vB vs BTC/kvB)
- Difficulty maintaining clients as the API evolves
- Increased effort to implement clients in new programming languages

There is no formal, machine-readable specification of the RPC API. Existing documentation is not sufficient for code generation or type-safe client implementations. See discussion in #
...

✅ scott-weeden closed a pull request: "Add initial OpenAPI/Swagger specification for Bitcoin Core RPC and REST interfaces (issue #29912)"
(https://github.com/bitcoin/bitcoin/pull/32726)

💬 vasild commented on pull request "config: allow setting -proxy per network":
(https://github.com/bitcoin/bitcoin/pull/32425#discussion_r2139847689)
What about this:

```diff
diff --git a/src/init.cpp b/src/init.cpp
index 77dc74f690..08ec964e25 100644
--- a/src/init.cpp
+++ b/src/init.cpp
@@ -1190,14 +1190,20 @@ bool CheckHostPortOptions(const ArgsManager& args) {
{"-zmqpubhashtx", true, false},
{"-zmqpubrawblock", true, false},
{"-zmqpubrawtx", true, false},
{"-zmqpubsequence", true, false},
}) {
for (const std
...

📝 ismaelsadeeq reopened a pull request: "init: make `-blockmaxweight` startup option debug only"
(https://github.com/bitcoin/bitcoin/pull/32654)
This PR updates `-blockmaxweight` startup option to be debug-only so that it will be hidden from help text.

The option is currently unlikely to be used on mainnet, after the addition of the new `blockreservedweight` option. however it can be useful for test and signet network see https://github.com/bitcoin/bitcoin/pull/32654#issuecomment-2925674473

📝 scott-weeden opened a pull request: " Add initial OpenAPI/Swagger specification for Bitcoin Core RPC and REST interfaces (issue #29912) "
(https://github.com/bitcoin/bitcoin/pull/32728)
## Motivation

Currently, (almost) all clients manually implement the Bitcoin Core RPC API, which leads to:
- Accidental implementation bugs (e.g., unit mistakes such as vB vs BTC/kvB)
- Difficulty maintaining clients as the API evolves
- Increased effort to implement clients in new programming languages

There is no formal, machine-readable specification of the RPC API. Existing documentation is not sufficient for code generation or type-safe client implementations. See discussion in #29
...

💬 ismaelsadeeq commented on pull request "init: make `-blockmaxweight` startup option debug only":
(https://github.com/bitcoin/bitcoin/pull/32654#issuecomment-2962264233)
> No particular objection to that.

Done.

💬 willcl-ark commented on pull request "Add initial OpenAPI/Swagger specification for Bitcoin Core RPC and REST interfaces (issue #29912)":
(https://github.com/bitcoin/bitcoin/pull/32728#issuecomment-2962274183)
I strongly suspect this PR description is AI-generated; this makes it seem likely to me that the code is also AI-generated.

I also don't think this PR is ready for review, and it should be marked as draft (or probably better still, closed) while you work on it, at which point it can be opened.

FYI you can run tests locally while you work on your changes. Once you have those passing it can be opened here and run against the full CI suite.

💬 josibake commented on pull request "depends: fix cmake compatibility error for freetype":
(https://github.com/bitcoin/bitcoin/pull/32693#issuecomment-2962317000)
> Another approach might be to bump freetype itself to 2.12.1

I had considered this, but this felt like a more invasive change. The goal here is simply to un-break the depends build for newer versions of CMake. Whether or not to bump the version of freetype in depends can then be evaluated as its own change, with its own motivation.

💬 Sjors commented on pull request "init: make `-blockmaxweight` startup option debug only":
(https://github.com/bitcoin/bitcoin/pull/32654#issuecomment-2962337460)
tACK e017ef3c7eb775e2cf999674df341be56f7ba72d

Although I don't think this is super important, it's nice to declutter the default `--help` output.

💬 fanquake commented on pull request "deps: Bump lief to 0.16.6":
(https://github.com/bitcoin/bitcoin/pull/32431#issuecomment-2962338677)
Guix Build:
```bash
8ee8f51264bd5f28d838207486f83db69a1dd4d00eeda009f35ef9ebff794d0f guix-build-4f56c9145a60/output/aarch64-linux-gnu/SHA256SUMS.part
aaf5a45736f062df340bbd434295a087f90897401a8d9e1489f5ad56c4a82fab guix-build-4f56c9145a60/output/aarch64-linux-gnu/bitcoin-4f56c9145a60-aarch64-linux-gnu-debug.tar.gz
d6b4a08a7e9dad84dcfdc504896cf0b13a4c2c416ef8608903cd542297936f74 guix-build-4f56c9145a60/output/aarch64-linux-gnu/bitcoin-4f56c9145a60-aarch64-linux-gnu.tar.gz
c236ea00cde96213
...

👍 fanquake approved a pull request: "deps: Bump lief to 0.16.6"
(https://github.com/bitcoin/bitcoin/pull/32431#pullrequestreview-2916777725)
ACK 4f56c9145a60c4fb837f11e47c5aa39ad8fa3523