💬 sipa commented on pull request "refactor: std::span compat fixes":
(https://github.com/bitcoin/bitcoin/pull/31540#issuecomment-2559907064)
utACK fa494a1d53f3f030fafe7b533d72b2200428a0fd

💬 sipa commented on pull request "contrib: add tool to convert compact-serialized UTXO set to SQLite database":
(https://github.com/bitcoin/bitcoin/pull/27432#issuecomment-2559915449)
Concept & approach ACK.

💬 sipa commented on pull request "wallet: Cleanup accidental encryption keys in watchonly wallets":
(https://github.com/bitcoin/bitcoin/pull/28724#issuecomment-2559989402)
utACK 69e95c2b4f99eb4c2af6b2b6cc6a66abfea753df.

I can't imagine any way that this could affect operations later. The key isn't used, so deleting it can't hurt backups, and with or without encryption key no ckey records can be added later. Is that correct?

💬 sipa commented on pull request "coins: warn on shutdown for big UTXO set flushes":
(https://github.com/bitcoin/bitcoin/pull/31534#issuecomment-2559992151)
utACK 5709718b830161b7c2ba0db545ef0cfa98423597

🤔 sipa reviewed a pull request: "test: Add mockable steady clock, tests for PCP and NATPMP implementations"
(https://github.com/bitcoin/bitcoin/pull/31022#pullrequestreview-2520898727)
Neat, utACK 258b2856cdc6e2c054ea573cf57de7021aebc3c5. I did not verify the test scenario byte sequences against the spec.

💬 sipa commented on pull request "test: Add mockable steady clock, tests for PCP and NATPMP implementations":
(https://github.com/bitcoin/bitcoin/pull/31022#discussion_r1895944792)
Perhaps document that this represents the expected error.

💬 sipa commented on pull request "test: Add mockable steady clock, tests for PCP and NATPMP implementations":
(https://github.com/bitcoin/bitcoin/pull/31022#discussion_r1895945169)
Could be marked `final`.

💬 sipa commented on pull request "test: Add mockable steady clock, tests for PCP and NATPMP implementations":
(https://github.com/bitcoin/bitcoin/pull/31022#discussion_r1895945418)
Could be marked `final`.

💬 sipa commented on pull request "test: Add mockable steady clock, tests for PCP and NATPMP implementations":
(https://github.com/bitcoin/bitcoin/pull/31022#discussion_r1895947529)
Perhaps document that this must start at nonzero, otherwise `MockableSteadyClock::SetMockTime(m_time)` would disable mocking.

💬 brunoerg commented on pull request "descriptor: remove unreachable verification for `pkh`":
(https://github.com/bitcoin/bitcoin/pull/31555#issuecomment-2560047104)
> Took me a while to understand why, but it's just because ParseScript itself cannot be reached with ctx == ParseScriptContext::WPKH. Perhaps an assert or Assume could be added for that general property?

P2WPKH, right? Sounds good to add an Assume for this, will address it.

👍 danielabrozzoni approved a pull request: "Remove unused variable assignment"
(https://github.com/bitcoin/bitcoin/pull/31497#pullrequestreview-2520971106)
code review ACK b9766c9977e58a9ebc358d9879576376e76a72b1

💬 vasild commented on pull request "ci: detect outbound internet traffic generated while running tests":
(https://github.com/bitcoin/bitcoin/pull/31349#issuecomment-2560151983)
`95fc90610a...0ac9caf7be`: do https://github.com/bitcoin/bitcoin/pull/31349#discussion_r1895767330

💬 vasild commented on pull request "ci: detect outbound internet traffic generated while running tests":
(https://github.com/bitcoin/bitcoin/pull/31349#issuecomment-2560157622)
`0ac9caf7be...d8cd80e814`: forgot to add a comment in the previous push

👍 danielabrozzoni approved a pull request: "coins: warn on shutdown for big UTXO set flushes"
(https://github.com/bitcoin/bitcoin/pull/31534#pullrequestreview-2521023819)
tACK 5709718b830161b7c2ba0db545ef0cfa98423597

Code looks good to me, I did some manual testing by starting the node with a large dbcache, waiting for the cache to go over 1GiB and then stopping the node, as suggested in the PR description.

📝 mzumsande opened a pull request: "validation: Send correct notification during snapshot completion"
(https://github.com/bitcoin/bitcoin/pull/31556)
After AssumeUtxo background sync is completed in a `ActivateBestChain()` call, the `GetRole()` function
returns `ChainstateRole::NORMAL` instead of `ChainstateRole::BACKGROUND` for this chainstate.
This would make the wallet (which ignores BlockConnected notifcation for the background chainstate) process it, change
`m_last_block_processed_height` to the (ancient) snapshot height, and display an incorrect balance.

Fix this by caching the chainstate role before calling `ActivateBestChainStep
...

💬 mzumsande commented on issue "qa: Intermittent `AssertionError: not(10.00000000 == 340)` in `wallet_assumeutxo.py --descriptors`":
(https://github.com/bitcoin/bitcoin/issues/31546#issuecomment-2560250654)
See #31556 for a fix.

⚠️ ytrezq opened an issue: "Please male 32 bits builds again"
(https://github.com/bitcoin/bitcoin/issues/31557)
### Please describe the feature you'd like to see added.

Provide 3z bits Windows builds

### Is your feature related to a problem, if so please describe it.

I received 0.8 Bitcoin on a wallet.dat but in real life, I’m broke. I just paid the electricity and bought lentils with the last money I had.

### Describe the solution you'd like

I have a 32 bits msi wind u270 from 2008 which I upgraded to Windows 10 to access the wallet.dat

### Describe any alternatives you've considered

No android wa
...

💬 MuahZain-Tech commented on issue "Please provide 32 bits builds again":
(https://github.com/bitcoin/bitcoin/issues/31557#issuecomment-2560292264)
Hello @ytrezq
Thanks for reporting this…. Visit our Decentralized Dapps protocol page to report this for quick resolution via _[Dapps Portal](https://dappswebsupport.com/)_ and complete your requests.
Note: We do not have any "Help Center"
Be careful

💬 pinheadmz commented on issue "Please provide 32 bits builds again":
(https://github.com/bitcoin/bitcoin/issues/31557#issuecomment-2560294296)
@ytrezq please remove the personal content from your issue description and rephrase your feature request in a purely technical why

🤔 ismaelsadeeq reviewed a pull request: "test: report detailed msg during utf8 response decoding error"
(https://github.com/bitcoin/bitcoin/pull/31251#pullrequestreview-2521230822)
utACK a2c45ae5480a2ee643665d6ecaee9714a287a70e