📝 furszy opened a pull request: "Fix peers abruptly disconnecting from AssumeUTXO nodes during IBD"
(https://github.com/bitcoin/bitcoin/pull/30807)
Context:
AssumeUTXO nodes prioritize tip synchronization first, meaning they advertise
knowledge of all blocks posterior to the snapshot base block hash. This, in
conjunction with the current protocol behavior where nodes request blocks
from peers that directly advertise them or their descendants, causes honest
peers trying to synchronize historical blocks from AssumeUTXO nodes to
forcibly disconnect, after stalling for ~10 minutes, due to a `getdata` lack
of response while the AssumeUTXO
...

💬 hashbender commented on issue "Testnet4 consensus failure due to timewarp related "softfork"":
(https://github.com/bitcoin/bitcoin/issues/30786#issuecomment-2327647103)
You have my hashpower 🫡

📝 fjahr opened a pull request: "rpd: dumptxoutset height parameter followups (29553)"
(https://github.com/bitcoin/bitcoin/pull/30808)
First, this addresses two left-over comments in #29553:

- When running `dumptxoutset` the network gets disabled in the beginning and then re-enabled in the beginning. The network would be re-enabled even if the user had already disabled the network themself before running `dumptxoutset`. The network is now not re-enabled anymore since that might not be what the user wants.
- The `-rpcclienttimeout=0` option is added to `loadtxoutset` examples in documentation

Additionally, pablomartin4btc
...

💬 fjahr commented on pull request "rpd: dumptxoutset height parameter followups (29553)":
(https://github.com/bitcoin/bitcoin/pull/30808#issuecomment-2327682955)
cc @pablomartin4btc

💬 1440000bytes commented on issue "Testnet4 consensus failure due to timewarp related "softfork"":
(https://github.com/bitcoin/bitcoin/issues/30786#issuecomment-2327691014)
> You have my hashpower 🫡

This will help

📝 Sarsilmazxx02 opened a pull request: "Update README.md"
(https://github.com/bitcoin/bitcoin/pull/30809)
<!--
*** 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
...

💬 tdb3 commented on pull request "rpc: add getorphantxs":
(https://github.com/bitcoin/bitcoin/pull/30793#issuecomment-2327703573)
> this PR might be a good time to enhance `test/functional/p2p_orphan_handling.py`, reducing our reliance on log messages at least

Great idea. For now, a child branch was started (https://github.com/tdb3/bitcoin/tree/enhance_p2p_orphan_handling) that adds a commit (https://github.com/tdb3/bitcoin/commit/344ab30487235a2096d878894dc6f4e2d0d1ef65) to update `p2p_orphan_handling`.

Since additional enhancements could be made to that branch (e.g. to check the orphanage when the debug log is sile
...

💬 tdb3 commented on pull request "rpc: add getorphantxs":
(https://github.com/bitcoin/bitcoin/pull/30793#discussion_r1742851986)
Updated

✅ achow101 closed a pull request: "Update README.md"
(https://github.com/bitcoin/bitcoin/pull/30809)

📝 achow101 locked a pull request: "Update README.md"
(https://github.com/bitcoin/bitcoin/pull/30809)
<!--
*** 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
...

💬 tdb3 commented on pull request "rpc: add getorphantxs":
(https://github.com/bitcoin/bitcoin/pull/30793#issuecomment-2327705761)
Updated to include an experimental warning and make the RPC hidden.
Also added a convenience function for checking the orphanage in tests.

💬 wiz commented on issue "Testnet4 consensus failure due to timewarp related "softfork"":
(https://github.com/bitcoin/bitcoin/issues/30786#issuecomment-2327715298)
ok will do

💬 hashbender commented on issue "Testnet4 consensus failure due to timewarp related "softfork"":
(https://github.com/bitcoin/bitcoin/issues/30786#issuecomment-2327719259)
Here's my last chain tip in case you want to verify the correct chain. This is from `Bitcoin Core version v28.0rc1`

```
hashbender@macbook-pro-124: bitcoin-cli -testnet4 getchaintips
[
{
"height": 42375,
"hash": "00000000000000306de15dd9ee1e6af0461e5bdef12d6dc6be212ca7f5296fa1",
"branchlen": 0,
"status": "active"
}
]
```

💬 tdb3 commented on pull request "Feature: Use different datadirs for different signets":
(https://github.com/bitcoin/bitcoin/pull/29838#issuecomment-2327729423)
This is a great feature. Looks like the CI logs might be gone? Maybe this CI could be nudged to run again. Not sure if this CI failure is related to the one seen a few months ago related to macOS.

💬 russeree commented on issue "Testnet4 consensus failure due to timewarp related "softfork"":
(https://github.com/bitcoin/bitcoin/issues/30786#issuecomment-2327729867)
> Here's my last chain tip in case you want to verify the correct chain. This is from `Bitcoin Core version v28.0rc1`
>
> ```
> hashbender@macbook-pro-124: bitcoin-cli -testnet4 getchaintips
> [
> {
> "height": 42375,
> "hash": "00000000000000306de15dd9ee1e6af0461e5bdef12d6dc6be212ca7f5296fa1",
> "branchlen": 0,
> "status": "active"
> }
> ]
> ```

Got 500TH/s pointed toward T4 UASF

💬 luke-jr commented on pull request "Show transactions as not fully confirmed during background validation":
(https://github.com/bitcoin/bitcoin/pull/28616#discussion_r1742909675)
For example, an attacker might give a lot of people a UTXO set with one additional entry, controlled by his key. Then, he can at any point later send that UTXO to anyone who used his modified UTXO set.

💬 hebasto commented on pull request "build: Minor build system fixes and amendments":
(https://github.com/bitcoin/bitcoin/pull/30803#discussion_r1742912171)
Thanks! Done.

💬 kevkevinpal commented on pull request "[tests] New fuzz target wallet_rpc":
(https://github.com/bitcoin/bitcoin/pull/30570#discussion_r1742922167)
Thanks!

Updated in [2c8cb2b](https://github.com/bitcoin/bitcoin/pull/30570/commits/2c8cb2b7cf9b6aa60562feb6aad2c6d071ee184b)

💬 hebasto commented on pull request "build: Introduce CMake-based build system":
(https://github.com/bitcoin/bitcoin/pull/30454#discussion_r1742927650)
> nit in [a2317e2](https://github.com/bitcoin/bitcoin/commit/a2317e27b7fb86df4e32cd1674c06e09cb808248): Maybe add a comment that this can be removed after `cmake_minimum_required(VERSION 3.25)`?

It seems redundant to me. Since policies are tied to specific versions, it's generally understood that one should review every `if(CMAKE_VERSION...)` and `if(POLICY...)` statement in the code when updating the minimum required version.

> Alternatively, given that "The default installation of the l
...

💬 hebasto commented on pull request "build: Introduce CMake-based build system":
(https://github.com/bitcoin/bitcoin/pull/30454#discussion_r1742931121)
I'd rather not include Wine installation instructions in this build doc. It is not a trivial process and could create an additional maintenance burden in the future.

> it wasn't present previously with autotools.

Let's just remove it.