🚀 achow101 merged a pull request: "cli: Detect port errors in rpcconnect and rpcport"
(https://github.com/bitcoin/bitcoin/pull/29521)

💬 achow101 commented on pull request "validation: improve performance of CheckBlockIndex":
(https://github.com/bitcoin/bitcoin/pull/28339#issuecomment-2161560686)
ACK 5bc2077e8f592442b089affdf0b5795fbc053bb8

💬 mzumsande commented on pull request "p2p: For assumeutxo, download snapshot chain before background chain":
(https://github.com/bitcoin/bitcoin/pull/29519#discussion_r1635456871)
> This means if the snapshot is not on the best chain, the node may be unable to sync to a better chain.

I've thought about this for a while, and I'm not sure if that problem is really being fixed by your suggestion for the following (slightly philosophical) reasons:
- Accepting a snapshot means that we've created a new chainstate with its Active Tip being set to that block.
- That is a commitment, we can't just reorg away from it to another chain that doesn't contain the snapshot block, ev
...

🚀 achow101 merged a pull request: "validation: improve performance of CheckBlockIndex"
(https://github.com/bitcoin/bitcoin/pull/28339)

💬 murchandamus commented on pull request "wallet, rpc: add anti-fee-sniping to `send` and `sendall`":
(https://github.com/bitcoin/bitcoin/pull/28944#issuecomment-2161576108)
> > ```diff
> > --- a/test/functional/wallet_import_rescan.py
> > +++ b/test/functional/wallet_import_rescan.py
> > @@ -293,6 +293,7 @@ class ImportRescanTest(BitcoinTestFramework):
> > add_to_wallet=False,
> > inputs=[unspent_txid_map[variant.initial_txid]],
> > outputs=[{ADDRESS_BCRT1_UNSPENDABLE : variant.initial_amount}],
> > + locktime=0,
> > subtract_fee_from_outputs=[0]
> > )
> >
...

👍 brunoerg approved a pull request: "fuzz: add I2P harness"
(https://github.com/bitcoin/bitcoin/pull/30230#pullrequestreview-2111463661)
ACK 193c748e44f8647a056121fc9cbb9c2efbcbfc49

💬 achow101 commented on pull request "util: add BitSet":
(https://github.com/bitcoin/bitcoin/pull/30160#issuecomment-2161613165)
ACK 47f705b33fc1381d96c99038e2110e6fe2b2f883

🚀 achow101 merged a pull request: "util: add BitSet"
(https://github.com/bitcoin/bitcoin/pull/30160)

💬 Eunovo commented on pull request "Tr partial descriptors":
(https://github.com/bitcoin/bitcoin/pull/30243#issuecomment-2161639208)
@ajtowns Thanks for the review. I added some examples to `wallet_miniscript.py` and updated `descriptors.md`

💬 sipa commented on pull request "Several randomness improvements":
(https://github.com/bitcoin/bitcoin/pull/29625#issuecomment-2161757848)
Rebased.

💬 sipa commented on pull request "feefrac: 128-bit multiply support in MSVC":
(https://github.com/bitcoin/bitcoin/pull/29758#issuecomment-2161872276)
@hebasto Thanks. I was assuming this would be an obvious improvement, but if it isn't, it'll need some more investigation into what this is all compiled to. That's not something I'm interested in doing for a half-supported architecture.

✅ sipa closed a pull request: "feefrac: 128-bit multiply support in MSVC"
(https://github.com/bitcoin/bitcoin/pull/29758)

💬 rocholojavinar commented on issue "Change estimate_mode default to "ECONOMICAL" in these RPC calls":
(https://github.com/bitcoin/bitcoin/issues/30009#issuecomment-2161991913)

💬 alfonsoromanz commented on pull request "test: Assumeutxo: import snapshot in a node with a divergent chain":
(https://github.com/bitcoin/bitcoin/pull/29996#discussion_r1635899433)
I just pushed my recent changes for this PR. This is the approach I decided to move forward with:

1. **Scenario Choice**: Between these two scenarios mentioned by @fjahr: "Particularly 'but has less work' could mean A) less work than the tip of the chain that includes the snapshot or B) less work than the snapshot block itself," I chose B) for this PR: less work than the snapshot block itself. I am happy to add tests for the other scenario in a separate PR.
2. **Added Fix**: I incorporated t
...

💬 alfonsoromanz commented on pull request "test: Assumeutxo: import snapshot in a node with a divergent chain":
(https://github.com/bitcoin/bitcoin/pull/29996#discussion_r1635899839)
Fixed

💬 alfonsoromanz commented on pull request "test: Assumeutxo: import snapshot in a node with a divergent chain":
(https://github.com/bitcoin/bitcoin/pull/29996#discussion_r1635900277)
Fixed

💬 vasild commented on pull request "netbase: extend CreateSock() to support creating arbitrary sockets":
(https://github.com/bitcoin/bitcoin/pull/30202#discussion_r1635902059)
Done

💬 vasild commented on pull request "netbase: extend CreateSock() to support creating arbitrary sockets":
(https://github.com/bitcoin/bitcoin/pull/30202#issuecomment-2162239639)
`77e34ded54...5f549c35d9`: fix typo in the comment: `s/socke/socket/`

💬 vasild commented on pull request "netbase: extend CreateSock() to support creating arbitrary sockets":
(https://github.com/bitcoin/bitcoin/pull/30202#discussion_r1635907777)
Oh, it is usually either `s`, `sock` or `socket`. `socke` is something new, that is extra genuine ;-)

Fixed, invalidating 3 ACKs but should be trivial to re-review.

Thanks!

💬 vasild commented on pull request "fuzz: add I2P harness":
(https://github.com/bitcoin/bitcoin/pull/30230#discussion_r1635926463)
Alright, I did not realize this.
(can resolve this)