⚠️ hebasto opened an issue: "cmake: Cannot find Qt 6 on SunOS / illumos (OpenIndiana Distribution)"
(https://github.com/bitcoin/bitcoin/issues/32536)
Qt 6 was installed as follows:
```
$ sudo pkg install library/qt6
```

As a workaround, the `Qt6_DIR` CMake variable can be set manually:
```
$ cmake -B build -DBUILD_GUI=ON -DQt6_DIR=/usr/lib/qt/6.6/lib/amd64/cmake/Qt6
```

Alternatively, the [`Qt6_ROOT`](https://cmake.org/cmake/help/latest/variable/PackageName_ROOT.html) CMake or [environment](https://cmake.org/cmake/help/latest/envvar/PackageName_ROOT.html) variable can be used:
```
$ env Qt6_DIR=/usr/lib/qt/6.6/lib/amd64 cmake -B build -DBUI
...

💬 furszy commented on pull request "wallet: init, don't error out when loading legacy wallets":
(https://github.com/bitcoin/bitcoin/pull/32449#discussion_r2093346688)
sure, updated.

💬 furszy commented on pull request "wallet: init, don't error out when loading legacy wallets":
(https://github.com/bitcoin/bitcoin/pull/32449#discussion_r2093349150)
Would have liked to do this, but it's not enough. The stderr pipe still needs to be cleared before the test finishes, or the framework will treat the warning message as an error during cleanup.

📝 hebasto opened a pull request: "250516 win min ver"
(https://github.com/bitcoin/bitcoin/pull/32537)
Set minimum supported Windows version to 1903 (May 2019 Update).

This version is the minimum [required](https://learn.microsoft.com/en-us/windows/apps/design/globalizing/use-utf8-code-page#set-a-process-code-page-to-utf-8) to support the UTF-8 code page (CP_UTF8), which is necessary for https://github.com/bitcoin/bitcoin/pull/32380.

Additionally, the `symbol-check.py` script has been amended to verify application manifests for supported OS value.

💬 hebasto commented on pull request "Set minimum supported Windows version to 1903 (May 2019 Update)":
(https://github.com/bitcoin/bitcoin/pull/32537#issuecomment-2887193874)
My Guix build:
```
aarch64
db31eebbbd5ed99567eea6d1e692130815e0b6e6c7041e8fe20918eb743ce3db guix-build-4748c63c1d0f/output/aarch64-linux-gnu/SHA256SUMS.part
05ad41b64f57a027124138e3e5baf3325e4bcb433c851e9086526568068694f2 guix-build-4748c63c1d0f/output/aarch64-linux-gnu/bitcoin-4748c63c1d0f-aarch64-linux-gnu-debug.tar.gz
f230295bc79a313acaa16090609b28c6df6021213b8bd8dea9938b8e48037f17 guix-build-4748c63c1d0f/output/aarch64-linux-gnu/bitcoin-4748c63c1d0f-aarch64-linux-gnu.tar.gz
acc5897b
...

💬 hebasto commented on pull request "Modernize use of UTF-8 in Windows code":
(https://github.com/bitcoin/bitcoin/pull/32380#issuecomment-2887196672)
Rebased on https://github.com/bitcoin/bitcoin/pull/32537.

💬 TheCharlatan commented on pull request "build: Introduce internal kernel library":
(https://github.com/bitcoin/bitcoin/pull/28690#discussion_r2093366846)
I think it is just used for logging. I could just stub it out, like we do for the translation function, but I am also not as sure how important it really is to be printing the clientversion there for these logs.

💬 fanquake commented on pull request "build: Introduce internal kernel library":
(https://github.com/bitcoin/bitcoin/pull/28690#discussion_r2093371205)
Yea, we could probably drop that. There's also `CLIENT_VERSION` fed into the env RNG, which could also likely be dropped.

💬 Eunovo commented on pull request "validation: ensure assumevalid is always used during reindex":
(https://github.com/bitcoin/bitcoin/pull/31615#discussion_r2093372479)
Script checks are only skipped when the current block is roughly 2 weeks away from the tip. See https://github.com/bitcoin/bitcoin/blob/3f83c744ac28b700090e15b5dda2260724a56f49/src/validation.cpp#L2476-L2494

We have to bury the test block 2 weeks deep for script verification to the skipped

👍 fanquake approved a pull request: "ci: Enable feature_init and wallet_reorgsrestore in valgrind task"
(https://github.com/bitcoin/bitcoin/pull/32519#pullrequestreview-2847192390)
ACK fa2be605fee42c1286de2ddefbec976dde2c35ba - x86_64, aarch64

🚀 fanquake merged a pull request: "ci: Enable feature_init and wallet_reorgsrestore in valgrind task"
(https://github.com/bitcoin/bitcoin/pull/32519)

👍 fanquake approved a pull request: "scripted-diff: Remove unused leading newline in RPC docs"
(https://github.com/bitcoin/bitcoin/pull/32514#pullrequestreview-2847195929)
ACK fa1f10a49e7c4f6377fbc7ae2f1520b38c86e5fa

💬 LarryRuane commented on pull request "improve MallocUsage() accuracy":
(https://github.com/bitcoin/bitcoin/pull/28531#issuecomment-2887255441)
Rebased to see if that fixes CI failure (which seems unrelated), the branch was previously rebased on Mar 17 2025.

💬 fanquake commented on pull request "Update leveldb subtree to latest upstream":
(https://github.com/bitcoin/bitcoin/pull/32534#issuecomment-2887264548)
Guix Build
```bash
a12f2290f4e5267f2ba9ad9da0d95e7990ea3e5772d7658a133d607a25afe7b4 guix-build-7015052eba23/output/aarch64-linux-gnu/SHA256SUMS.part
6232c5017a17753b33c62f32def946a72f70ce63b76b55dc9a8fa8c8e75229fe guix-build-7015052eba23/output/aarch64-linux-gnu/bitcoin-7015052eba23-aarch64-linux-gnu-debug.tar.gz
c702cf46c5c463ccd08ec97f3858cf1a1ce612e0c92836f6dedc94d1f6ad16f3 guix-build-7015052eba23/output/aarch64-linux-gnu/bitcoin-7015052eba23-aarch64-linux-gnu.tar.gz
a0e2e6f5198c435c1
...

🚀 fanquake merged a pull request: "[28.x] 28.2rc1"
(https://github.com/bitcoin/bitcoin/pull/32480)

💬 earonesty commented on pull request "policy: uncap datacarrier by default":
(https://github.com/bitcoin/bitcoin/pull/32406#issuecomment-2887275676)
makes more sense to change the default to be larger or whatever not remove the option at all

💬 pinheadmz commented on issue ""rpcallowip=" configuration directive doesn't accept RFC4193 addresses":
(https://github.com/bitcoin/bitcoin/issues/32433#issuecomment-2887277091)
Looking at this a bit closer, I see that this shouldn't be an issue unless you also have `-cjdnsreachable` set. It is currently an issue because we process `rpcallowip` before we even check for `cjdsnreachable`... I'm going to write a patch and open a PR shortly.

💬 mzumsande commented on pull request "validation: ensure assumevalid is always used during reindex":
(https://github.com/bitcoin/bitcoin/pull/31615#discussion_r2093440637)
oh I see, forgot about that check - can be resolved.

👍 stickies-v approved a pull request: "Remove legacy `Parse(U)Int*`"
(https://github.com/bitcoin/bitcoin/pull/32520#pullrequestreview-2847037118)
ACK, nice cleanup.

Introduces some slight behaviour change when passing integer arguments through startup options, the REST interface, as and through `bitcoin-cli` and `bitcoin-tx`. While some of these changes _may_ break existing user flows that were previously fine, they should hopefully be quite rare, and I think are worth the cleanup and more strict parsing.

💬 stickies-v commented on pull request "Remove legacy `Parse(U)Int*`":
(https://github.com/bitcoin/bitcoin/pull/32520#discussion_r2093391212)
If we use `SAFE_CHARS_URI` here (seems appropriate since we're dealing with a uri) the `+` sign is returned in the error description:

<details>
<summary>git diff on fa24012c18</summary>

```diff
diff --git a/src/rest.cpp b/src/rest.cpp
index b340567bd1..464880224c 100644
--- a/src/rest.cpp
+++ b/src/rest.cpp
@@ -964,7 +964,7 @@ static bool rest_blockhash_by_height(const std::any& context, HTTPRequest* req,

const auto blockheight{ToIntegral<int32_t>(height_str)};
if (!bl
...