👍 brunoerg approved a pull request: "lint: [doc] Clarify Windows line endings (CR LF) not to be used"
(https://github.com/bitcoin/bitcoin/pull/30010#pullrequestreview-2033554704)
ACK fa9be2f79520fff9cfe2ed35ace05cb322680af3

⚠️ tylerztl opened an issue: "How to get Signet test coins(sBTC)?"
(https://github.com/bitcoin/bitcoin/issues/30013)
### Issues, reports or feature requests related to the GUI should be opened directly on the GUI repo

- [X] I still think this issue should be opened here

### Report

I am a developer. I want to get more test coins of the signet network. The faucet is too small. If I want to get more, I try to start the test node, but I cannot mint any sBTC.

✅ maflcko closed an issue: "How to get Signet test coins(sBTC)?"
(https://github.com/bitcoin/bitcoin/issues/30013)

💬 maflcko commented on issue "How to get Signet test coins(sBTC)?":
(https://github.com/bitcoin/bitcoin/issues/30013#issuecomment-2088439640)
Usually the issue tracker is used to track technical issues related to the Bitcoin Core code base.

General bitcoin questions and/or support requests are best directed to the [Bitcoin StackExchange](https://bitcoin.stackexchange.com) or the `#bitcoin` IRC channel on Libera Chat, or one of the Bitcoin subreddits, or any other place that you feel is well suited.

💬 sr-gi commented on pull request "net: Favor peers from addrman over fetching seednodes":
(https://github.com/bitcoin/bitcoin/pull/29605#discussion_r1586275063)
Done inn [33ddd1b](https://github.com/bitcoin/bitcoin/pull/29605/commits/33ddd1b4c1cb1165b5068fbf7a9461e295f6cef1)

💬 hebasto commented on pull request "refactor: Use our own implementation of urlDecode":
(https://github.com/bitcoin/bitcoin/pull/29904#issuecomment-2088465111)
Ported to the CMake-based build system in https://github.com/hebasto/bitcoin/pull/181.

💬 vasild commented on pull request "Broadcast own transactions only via short-lived Tor or I2P connections":
(https://github.com/bitcoin/bitcoin/pull/29415#issuecomment-2088480026)
`fd603b8f5c...42cb080600`: rebase and address suggestions

📝 shinghim opened a pull request: "doc: Remove outdated description for --port argument"
(https://github.com/bitcoin/bitcoin/pull/30014)
Removing an outdated sentence in the argument description for the --port argument. The note says to wait until #23542 have become widespread, which I think has happened since those changes were merged over two years ago on March 2, 2022

💬 vasild commented on pull request "Broadcast own transactions only via short-lived Tor or I2P connections":
(https://github.com/bitcoin/bitcoin/pull/29415#discussion_r1586316212)
Yes, but I did not like the behavior of the wallet "unexpectedly" stopping to broadcast its own transactions because `-privatebroadcast` is enabled.

> It's not the most user-friendly thing to introduce a new command arg that would only work if another arg was also changed from its default.

Yes, I agree. I do not like that either but somewhat prefer it over automatically switching off wallet broadcast. I can imagine GUI users who enable `-privatebroadcast` and still try to send transactions
...

💬 vasild commented on pull request "Broadcast own transactions only via short-lived Tor or I2P connections":
(https://github.com/bitcoin/bitcoin/pull/29415#discussion_r1586317728)
Updated.

💬 vasild commented on pull request "Broadcast own transactions only via short-lived Tor or I2P connections":
(https://github.com/bitcoin/bitcoin/pull/29415#discussion_r1586317921)
Yes, fixed!

📝 shinghim converted_to_draft a pull request: "doc: Remove outdated description for --port argument"
(https://github.com/bitcoin/bitcoin/pull/30014)
Removing an outdated sentence in the argument description for the --port argument. The note says to wait until changes in #23542 have become widespread, which I think has happened since those changes were merged over two years ago on March 2, 2022

💬 vasild commented on pull request "Broadcast own transactions only via short-lived Tor or I2P connections":
(https://github.com/bitcoin/bitcoin/pull/29415#discussion_r1586318759)
Added `Assume(false)` and a comment.

💬 vasild commented on pull request "Broadcast own transactions only via short-lived Tor or I2P connections":
(https://github.com/bitcoin/bitcoin/pull/29415#discussion_r1586319178)
Yes, I was thinking the same. Moved away.

💬 vasild commented on pull request "Broadcast own transactions only via short-lived Tor or I2P connections":
(https://github.com/bitcoin/bitcoin/pull/29415#discussion_r1586319383)
Removed.

💬 vasild commented on pull request "Broadcast own transactions only via short-lived Tor or I2P connections":
(https://github.com/bitcoin/bitcoin/pull/29415#discussion_r1586319507)
Updated.

💬 vasild commented on pull request "Broadcast own transactions only via short-lived Tor or I2P connections":
(https://github.com/bitcoin/bitcoin/pull/29415#discussion_r1586320176)
To avoid negative values. I added a comment in the source code to explain.

👋 shinghim's pull request is ready for review: "doc: Remove outdated description for --port argument"
(https://github.com/bitcoin/bitcoin/pull/30014)

💬 furszy commented on pull request "net: introduce block tracker to retry to download blocks after failure":
(https://github.com/bitcoin/bitcoin/pull/27837#discussion_r1586351758)
fixed

💬 glozow commented on pull request "p2p: opportunistically accept 1-parent-1-child packages":
(https://github.com/bitcoin/bitcoin/pull/28970#discussion_r1586354156)
^I added this to #30012

💬 pinheadmz commented on pull request "Support JSON-RPC 2.0 when requested by client":
(https://github.com/bitcoin/bitcoin/pull/27101#discussion_r1586354746)
ok thanks, originally I wanted to use a default value to ensure that bitcoin-cli continued to work without any changes