💬 Sjors commented on pull request "mining: bugfix: Fix duplicate coinbase tx weight reservation":
(https://github.com/bitcoin/bitcoin/pull/31384#discussion_r1939827439)
In 8b8e143a8fdd9c12068c7d7f5bbe5317dd55d22a "init: fail to start when `-blockmaxweight` exceeds `DEFAULT_MAX_BLOCK_WEIGHT`": I think this should only check against consensus.

💬 Sjors commented on pull request "mining: bugfix: Fix duplicate coinbase tx weight reservation":
(https://github.com/bitcoin/bitcoin/pull/31384#discussion_r1939831288)
In cd6cca1018f1c4b0c5d73991afbdb19d1b0b9682 "miner: init: add `-blockreservedweight` startup option"

Same as for the earlier commit, imo this should only check against the consensus limit.
https://github.com/bitcoin/bitcoin/pull/31384/commits/cd6cca1018f1c4b0c5d73991afbdb19d1b0b9682#r1938237527

💬 ismaelsadeeq commented on pull request "mining: bugfix: Fix duplicate coinbase tx weight reservation":
(https://github.com/bitcoin/bitcoin/pull/31384#discussion_r1939839897)
In block assembly, we check against policy. If we were to lower the policy default, users could set a higher value than our policy limit, but the generated block would still be checked against policy, meaning their higher value would have no effect. I think we should be consistent and either check against policy everywhere or remove the policy default and check only against consensus?

💬 ismaelsadeeq commented on pull request "mining: bugfix: Fix duplicate coinbase tx weight reservation":
(https://github.com/bitcoin/bitcoin/pull/31384#discussion_r1939842698)
Done in this [push](https://github.com/bitcoin/bitcoin/compare/e7df348288e81dae104df7f8c984cb8eca57da35..6709e185b93d97b9191597acfecb25c33ab43a0a)
Also updated the release note to fix grammar

📝 Hack666r opened a pull request: "Typos fix"
(https://github.com/bitcoin/bitcoin/pull/31789)
### Changes

1. **File:** `/test/lint/README.md`
- Fixed `lief` to `leaf, life` (Line 48)
1. **File:** `/contrib/guix/INSTALL.md`
- Fixed `debbugs` to `debugs, bedbugs` (Line 761)
1. **File:** `/doc/psbt.md`
- Fixed `Asend` to `Ascend, As end` (Line 132)
1. **File:** `/doc/tracing.md`
- Fixed `stap` to `step, stop` (Line 379)

### Purpose

- Improved documentation accuracy by fixing typographical errors.
- Ensured better readability and consistency.

📝 petryshkaCODE opened a pull request: "Fixed typos"
(https://github.com/bitcoin/bitcoin/pull/31790)
### Changes

1. **File:** `/test/lint/README.md`
- Fixed `LIEF` to `LEAF, LIFE` (Line 48)
1. **File:** `/doc/build-osx.md`
- Fixed `useable` to `usable` (Line 74)
1. **File:** `/doc/psbt.md`
- Fixed `Asend` to `Ascend, As end` (Line 137)

### Purpose

- Enhanced the clarity and professionalism of the documentation.
- Fixed minor grammatical issues for better understanding.

🤔 ryanofsky reviewed a pull request: "multiprocess: Add libmultiprocess git subtree"
(https://github.com/bitcoin/bitcoin/pull/31741#pullrequestreview-2590699485)
Rebased ab041937289f4939758c1896f5cb57f556ae0615 -> 1c10bfc167b0f3c17780b2ae3747999ee56c4e1c ([`pr/subtree.4`](https://github.com/ryanofsky/bitcoin/commits/pr/subtree.4) -> [`pr/subtree.5`](https://github.com/ryanofsky/bitcoin/commits/pr/subtree.5), [compare](https://github.com/ryanofsky/bitcoin/compare/pr/subtree.4-rebase..pr/subtree.5)) incorporating changes from https://github.com/theuni/bitcoin/commits/libmultiprocess-vendor/ and making various build fixes to let multiprocess CI jobs succeed
...

💬 ryanofsky commented on pull request "multiprocess: Add libmultiprocess git subtree":
(https://github.com/bitcoin/bitcoin/pull/31741#discussion_r1939842127)
re: https://github.com/bitcoin/bitcoin/pull/31741#discussion_r1938048845

> for determinism (our sources can be described exactly).

The sources are described by the git hash. The tarball could be generated deterministically too, but should be ok to just use default tar options. If during a deterministic build, you put a directory into a intermediate tarball and extract it and compile it, whether the intermediate tarball was deterministic should not effect whether build outputs are determini
...

💬 pinheadmz commented on pull request "guix: Notarize MacOS app bundle and codesign all MacOS and Windows binaries":
(https://github.com/bitcoin/bitcoin/pull/31407#issuecomment-2631806570)
I got one step further by creating the directory its looking for in the last error:

`$ mkdir -p /home/zip/bitcoin/guix-build-ba67aa681e9b/var/profiles/`

this broke somewhere new...

```
$ DETACHED_SIGS_REPO=../bitcoin-detached-sigs HOSTS=arm64-apple-darwin FORCE_DIRTY_WORKTREE=1 ./contrib/guix/guix-codesign
Checking that we can connect to the guix-daemon...

Hint: If this hangs, you may want to try turning your guix-daemon off and on
again.

INFO: Codesigning ba67aa681e9b f
...

✅ hebasto closed a pull request: "."
(https://github.com/bitcoin/bitcoin/pull/31789)

📝 hebasto locked a pull request: "."
(https://github.com/bitcoin/bitcoin/pull/31789)
### Changes

1. **File:** `/test/lint/README.md`
- Fixed `lief` to `leaf, life` (Line 48)
1. **File:** `/contrib/guix/INSTALL.md`
- Fixed `debbugs` to `debugs, bedbugs` (Line 761)
1. **File:** `/doc/psbt.md`
- Fixed `Asend` to `Ascend, As end` (Line 132)
1. **File:** `/doc/tracing.md`
- Fixed `stap` to `step, stop` (Line 379)

### Purpose

- Improved documentation accuracy by fixing typographical errors.
- Ensured better readability and consistency.

✅ hebasto closed a pull request: "."
(https://github.com/bitcoin/bitcoin/pull/31790)

📝 hebasto locked a pull request: "."
(https://github.com/bitcoin/bitcoin/pull/31790)
### Changes

1. **File:** `/test/lint/README.md`
- Fixed `LIEF` to `LEAF, LIFE` (Line 48)
1. **File:** `/doc/build-osx.md`
- Fixed `useable` to `usable` (Line 74)
1. **File:** `/doc/psbt.md`
- Fixed `Asend` to `Ascend, As end` (Line 137)

### Purpose

- Enhanced the clarity and professionalism of the documentation.
- Fixed minor grammatical issues for better understanding.

✅ hebasto closed a pull request: "."
(https://github.com/bitcoin/bitcoin/pull/31788)

📝 hebasto locked a pull request: "."
(https://github.com/bitcoin/bitcoin/pull/31788)
### Changes

1. **File:** `/contrib/guix/INSTALL.md`
- Fixed `debbugs` to `debugs, bedbugs` (Line 761)
1. **File:** `/doc/psbt.md`
- Fixed `Asend` to `Ascend, As end` (Line 129)
1. **File:** `/doc/tracing.md`
- Fixed `stap` to `step, stop` (Line 378)

### Purpose

- EImproved the documentation's clarity and professional tone.
- Corrected small grammatical errors to enhance comprehension.

👋 hebasto's pull request is ready for review: "cmake: Improve safety and robustness during building `crc32c` subtree"
(https://github.com/bitcoin/bitcoin/pull/31779)

💬 mzumsande commented on pull request "multi-peer orphan resolution followups":
(https://github.com/bitcoin/bitcoin/pull/31666#discussion_r1939898933)
Looks good to me now, rest is just a matter of taste.

💬 theuni commented on pull request "build: simplify by flattening the dependency graph":
(https://github.com/bitcoin/bitcoin/pull/30911#issuecomment-2631884794)
$ cmake -G Ninja -B build
$ cmake --build build -t test_bitcoin
$ touch src/test/data/bip341_wallet_vectors.json
$ cmake --build build -t test_bitcoin

`[2/5] cd /home/cory/dev/bitcoin/build/src/test && /usr/bin/cmake -DJSON_SOURCE_PATH=/home/cory/dev/bitcoin/src/test/data/bip341_wallet_vectors.json -DHEADER_PATH=/home/cory/dev/bitcoin/build/src/test/data/bip341_wallet_vectors.json.h -P /home/cory/dev/bitcoin/cmake/script/GenerateHeaderFromJson.cmake`

Why would the headers need to be reg
...

💬 hebasto commented on pull request "build: simplify by flattening the dependency graph":
(https://github.com/bitcoin/bitcoin/pull/30911#issuecomment-2631897249)
> Why would the headers need to be regenerated unless the .json/.raw files themselves were touched?

The `.json`/`.raw` files are _explicit_ dependencies specified via the `DEPENDS` option. The `DEPENDS_EXPLICIT_ONLY` option changes the treatment of `_implicit_ dependencies.

💬 ryanofsky commented on pull request "cmake: Set top-level target output locations":
(https://github.com/bitcoin/bitcoin/pull/31161#issuecomment-2631914588)
I think if this PR is going to be merged without providing backward compatibility, something should be done to warn developers, like adding a tag `[BREAKING]` or `[INCOMPATIBLE]` or `[!]` or emoji ‼️ or ⚠️ to the subject and a clear warning in the description and maybe saying something in IRC channel too.

In its current form, this change seems likely to cause confusion and wasted time because when upgrading or downgrading around the change, **builds will appear to succeed but old binaries wil
...