💬 setavenger commented on pull request "Silent payment index (for light wallets and consistency check)":
(https://github.com/bitcoin/bitcoin/pull/28241#issuecomment-2105076296)
> Something that will also likely cut the index down by a lot is a "dust filter,"

I have some preliminary numbers [here](https://github.com/setavenger/BIP0352-light-client-specification/?tab=readme-ov-file#dust-limits). They are in the same ballpark as another analysis. Next step would be to see how this reduced UTXO set will actually affect the number of tweaks. Specifically, I'd like to find out to which degree we can actually reduce the set of tweaks based on how dust UTXOs are clustered p
...

👍 theuni approved a pull request: "refactor: Remove unused code from `subprocess.h` header"
(https://github.com/bitcoin/bitcoin/pull/30081#pullrequestreview-2050629489)
Easy code review ACK 5a11d3023f7d0cde777f3496c0f3aa381823d749 since it's all removals :)

I assume since c-i is green that this code is all unneeded, but I can't attest to the specifics.

💬 brunoerg commented on pull request "wallet: add coin selection parameter `add_excess_to_recipient_position` for changeless txs with excess that would be added to fees":
(https://github.com/bitcoin/bitcoin/pull/30080#issuecomment-2105082713)
From CI:
```
291/305 -
rpc_help.py
failed, Duration: 1 s
stdout:
2024-05-10T15:06:20.992000Z TestFramework (INFO): PRNG seed is: 4539310303736745094
2024-05-10T15:06:20.998000Z TestFramework (INFO): Initializing test directory /ci_container_base/ci/scratch/test_runner/test_runner_₿_🏃_20240510_150004/rpc_help_7
2024-05-10T15:06:21.349000Z TestFramework (ERROR): Assertion failed
Traceback (most recent call last):
File "/ci_container_base/ci/scratch/build/bitcoin-i686-pc-linux-gnu/te
...

💬 theuni commented on pull request "build: LLD based macOS toolchain":
(https://github.com/bitcoin/bitcoin/pull/21778#discussion_r1597085098)
-B isn't sufficient here?

👍 theuni approved a pull request: "crypto, refactor: add new KeyPair class"
(https://github.com/bitcoin/bitcoin/pull/30051#pullrequestreview-2050642049)
ACK bdc2a656c2d2a61d226fde1d1fd4e79664106e18

👍 theuni approved a pull request: "crypto: add `NUMS_H` const"
(https://github.com/bitcoin/bitcoin/pull/30048#pullrequestreview-2050650940)
Code review 57a06646952fed98c1c281f02fe58a0758a8ed5a. I didn't verify with sage.

💬 Sjors commented on pull request "Silent payment index (for light wallets and consistency check)":
(https://github.com/bitcoin/bitcoin/pull/28241#issuecomment-2105116651)
Alright, let's see how it goes with dust limit 1000.

💬 Sjors commented on pull request "Silent payment index (for light wallets and consistency check)":
(https://github.com/bitcoin/bitcoin/pull/28241#discussion_r1597120404)
Note that if we serve this via a BIP157 the cut-through version is going to be indeterministic. Same if people pick a different dust limit. This seems hard to avoid in any case, because the entire filter chain potentially changes with each new block that comes in.

💬 paplorinc commented on pull request "refactor: Model the bech32 charlimit as an Enum":
(https://github.com/bitcoin/bitcoin/pull/30047#discussion_r1597108664)
I worked around this 90 in my pr in https://github.com/bitcoin/bitcoin/pull/29607/files#diff-f146300624c06d2e08aadf500952294148a1785edd6ff2e8b50f13b2c08255edL315 (though I'm not sure why it's not replaced here with `limit`) - I will try to review this in more detail next week

💬 theuni commented on pull request "refactor: Model the bech32 charlimit as an Enum":
(https://github.com/bitcoin/bitcoin/pull/30047#discussion_r1597123552)
Ah, can't believe I missed that. Nice catch!

🤔 furszy reviewed a pull request: "assumeutxo, rpc: Improve EOF error when reading snapshot metadata in loadtxoutset"
(https://github.com/bitcoin/bitcoin/pull/28670#pullrequestreview-2050742070)
utACK 521de52c751

💬 furszy commented on pull request "assumeutxo, rpc: Improve EOF error when reading snapshot metadata in loadtxoutset":
(https://github.com/bitcoin/bitcoin/pull/28670#discussion_r1597147718)
Shouldn't use `RPC_INTERNAL_ERROR`. As per it description: "this error should only be used for genuine errors in bitcoind (for example datadir corruption)"

Maybe use `RPC_DESERIALIZATION_ERROR` or `RPC_MISC_ERROR.

💬 willcl-ark commented on issue "Slow memory leak in v22.0?":
(https://github.com/bitcoin/bitcoin/issues/24542#issuecomment-2105183958)
Discovered another attempt to avoid copies from @maflcko https://github.com/bitcoin/bitcoin/pull/25429 while researching further.

Ref my previous test in #30052, I have a branch with some improvements (heavily "insipred" by @martinus 's commit https://github.com/jgarzik/univalue/pull/79/commits/e9109e2a04b47472fe45a9cae3c6b41c245a6db9) which limit allocations to about 60-70MB:


This is about
...

🤔 cbergqvist reviewed a pull request: "net: Favor peers from addrman over fetching seednodes"
(https://github.com/bitcoin/bitcoin/pull/29605#pullrequestreview-2050826137)
re-ACK f3c4c4ba894cf919f7dd2d997c3c0c47b320229e

Ran `test/functional/p2p_seednode.py` 15 times to confirm robustness against timeouts.
Also ran functional tests with `-extended --exclude=feature_dbcrash` with no failures.

Still urge you to do something like f9bfc588f2e81a7febe233f591b75e41a52db8b4 from https://github.com/bitcoin/bitcoin/pull/29605#discussion_r1586847044 (still cherry-picks cleanly). Narrowing state carried around to when it is actually used is cleaner and more respectful
...

💬 theuni commented on pull request "refactor: Model the bech32 charlimit as an Enum":
(https://github.com/bitcoin/bitcoin/pull/30047#discussion_r1597205866)
ctrl+f "90", whew that's the only one. This is exactly why named constants are so important to name. I think it's fair to call this a nice cleanup (getting rid of the constant) in addition to the new feature.

💬 theuni commented on pull request "refactor: Model the bech32 charlimit as an Enum":
(https://github.com/bitcoin/bitcoin/pull/30047#issuecomment-2105238891)
ACK retracted until resolving https://github.com/bitcoin/bitcoin/pull/30047#discussion_r1597108664.

📝 TheCharlatan opened a pull request: "kernel: Remove batchpriority from kernel library"
(https://github.com/bitcoin/bitcoin/pull/30083)
The current usage of ScheduleBatchPriority is not transparent. Once the thread scheduling is changed, it remains unchanged for the remainder of the thread's lifetime. So move the call from `ImportBlocks` to the init code where it is clearer that its effect lasts for the entire lifetime of the thread.

Users of the kernel library might not expect `ImportBlocks` to have an influence on the thread it is called in. Particularly since it is only a compile time option and cannot be controlled at run
...

💬 mzumsande commented on pull request "blockstorage: Separate reindexing from saving new blocks":
(https://github.com/bitcoin/bitcoin/pull/29975#discussion_r1597235280)
I have done that, but bundled most of the doc changes to a doc-only commit at the beginning in order to not have unrelated things in the "blockstorage: split up FindBlockPos function" commit.

💬 mzumsande commented on pull request "blockstorage: Separate reindexing from saving new blocks":
(https://github.com/bitcoin/bitcoin/pull/29975#discussion_r1597235497)
Done as an extra commit at the end.

💬 mzumsande commented on pull request "blockstorage: Separate reindexing from saving new blocks":
(https://github.com/bitcoin/bitcoin/pull/29975#discussion_r1597236294)
I have added this with the latest push. Changed the `// Update the file information so it points to the last block.` comment slightly because the file information doesn't really point to anything.