💬 fanquake commented on pull request "test: change log rate limit version gate":
(https://github.com/bitcoin/bitcoin/pull/33612#issuecomment-3402716396)
Backported to `30.x` in #33609.

💬 fanquake commented on pull request "test: change log rate limit version gate":
(https://github.com/bitcoin/bitcoin/pull/33612#issuecomment-3402720496)
Backported to `29.x` in #33611.

💬 fanquake commented on pull request "Update libmultiprocess subtree in 30.x branch":
(https://github.com/bitcoin/bitcoin/pull/33519#issuecomment-3402730706)
cc @Sjors @theuni

💬 diegoviola commented on issue "Qt6 version of Bitcoin Core (bitcoin-qt) flickers on Wayland":
(https://github.com/bitcoin-core/gui/issues/903#issuecomment-3402733857)
> > ```
> > 2025-10-14T14:47:07Z Qt 6.10.0 (dynamic), plugin=wayland
> > 2025-10-14T14:47:07Z No static plugins.
> > ```
>
> Could you please try the release binary from https://bitcoincore.org/bin/bitcoin-core-30.0/ or build a statically linked binary with [depends](https://github.com/bitcoin-core/gui/tree/master/depends)?
>
> EDIT: Both options have only the XCB plugin built in and do not use Wayland. I just want to ensure that release binaries are not affected on your system.

Sure, I just
...

💬 Sjors commented on pull request "Update libmultiprocess subtree in 30.x branch":
(https://github.com/bitcoin/bitcoin/pull/33519#issuecomment-3402738575)
Since it missed the 30.0 cut-off, should we wait a bit longer?

💬 instagibbs commented on pull request "test: P2SH sig ops are only counted with `SCRIPT_VERIFY_P2SH`":
(https://github.com/bitcoin/bitcoin/pull/33624#discussion_r2429811753)
```suggestion
assert(GetTransactionSigOpCost(CTransaction(spendingTx), coins, /*flags=*/0) == 0);
```

💬 instagibbs commented on pull request "test: P2SH sig ops are only counted with `SCRIPT_VERIFY_P2SH`":
(https://github.com/bitcoin/bitcoin/pull/33624#discussion_r2429816763)
we're not ignoring, we're not setting it
```suggestion
// P2SH sigops are not counted if we don't set the SCRIPT_VERIFY_P2SH flag
```

👋 instagibbs's pull request is ready for review: "TxGraph: change m_excluded_clusters"
(https://github.com/bitcoin/bitcoin/pull/33469)

💬 instagibbs commented on pull request "TxGraph: change m_excluded_clusters":
(https://github.com/bitcoin/bitcoin/pull/33469#issuecomment-3402795146)
ready for review

💬 yancyribbens commented on pull request "docs: add doc comment for SRD selection algorithm":
(https://github.com/bitcoin/bitcoin/pull/33622#issuecomment-3402801716)
cc @furszy as related to https://github.com/bitcoin/bitcoin/issues/33168

🤔 instagibbs reviewed a pull request: "txgraph: randomize order of same-feerate distinct-cluster transactions"
(https://github.com/bitcoin/bitcoin/pull/33335#pullrequestreview-3336623868)
Thinking a bit more on the fact that this randomizes eviction ordering in addition to INV gossiping, but rebase was straight forward

`git range-diff master 593d418137e4802bbe229707dcda5796522e2e5e 949353ac63249bf51fce34f50ac27f6ec51d0172`

💬 instagibbs commented on pull request "txgraph: randomize order of same-feerate distinct-cluster transactions":
(https://github.com/bitcoin/bitcoin/pull/33335#discussion_r2429842707)
seems this got lost in rebase?
```suggestion
* equal-feerate transactions in distinct clusters, to avoid leaking insertion order. */
```

📝 fanquake opened a pull request: "ci: run native fuzz with MSAN job"
(https://github.com/bitcoin/bitcoin/pull/33626)
I think this job should exist in this repo (not just qa-assets), if the alternative is double-handling changes to the interpreter (regardless of if it's to work around false positives). #32998 made changes which are now being re-changed in #33600, to work around the false positive mentioned there (so the job should currently fail here).

💬 dergoegge commented on pull request "ci: run native fuzz with MSAN job":
(https://github.com/bitcoin/bitcoin/pull/33626#issuecomment-3402849862)
Concept ACK

💬 ismaelsadeeq commented on pull request "Policy: Report reason inputs are non standard":
(https://github.com/bitcoin/bitcoin/pull/29060#issuecomment-3402862243)
Forced push from db5c7ed388a8eb72247dff015bbf47654f27faf1 to 9eea72d3f3647197c24329b412c7fc71895e3ea2 Compare diff [4f27faf1..9eea72d](https://github.com/bitcoin/bitcoin/compare/db5c7ed388a8eb72247dff015bbf47654f27faf1..9eea72d3f3647197c24329b412c7fc71895e3ea2)

I've believed @sipa recent comment https://github.com/bitcoin/bitcoin/pull/29060#issuecomment-3401998439 is now fixed, I've maintained the error code and add the additional information in the debug message.

> Somewhat related questi
...

👍 stickies-v approved a pull request: "doc: archive release notes for v29.2"
(https://github.com/bitcoin/bitcoin/pull/33610#pullrequestreview-3336705070)
ACK c11a3dcc88950d35cc8a97c6afba7d8f7eff9883, matches https://github.com/bitcoin/bitcoin/blob/3226616493289b111997bb107e569fef54386743/doc/release-notes.md

🚀 fanquake merged a pull request: "doc: archive release notes for v29.2"
(https://github.com/bitcoin/bitcoin/pull/33610)

💬 fanquake commented on pull request "ci: run native fuzz with MSAN job":
(https://github.com/bitcoin/bitcoin/pull/33626#issuecomment-3402903110)
This has actually failed in a different way. Looks like #30760?

📝 maflcko opened a pull request: "ci: Remove unused workaround: sysctl -w vm.mmap_rnd_bits=28"
(https://github.com/bitcoin/bitcoin/pull/33627)
Remove the workaround that is no longer needed.

💬 diegoviola commented on issue "Qt6 version of Bitcoin Core (bitcoin-qt) flickers on Wayland":
(https://github.com/bitcoin-core/gui/issues/903#issuecomment-3402926319)
@hebasto @pablomartin4btc can we just get rid of the problematic code in this case? According to this comment: https://github.com/swaywm/sway/issues/4739#issuecomment-555965289

"Qt.WindowStaysOnTopHint won't work on Wayland. Clients don't get to dictate whether they stay on top or not.".