💬 starkshade commented on pull request "[28.x] backports + 28.3rc1":
(https://github.com/bitcoin/bitcoin/pull/33476#discussion_r2390343614)
## 💡 Improvement Needed
**Line:** 3
The version number `_CLIENT_VERSION_MINOR` is hardcoded. For better maintainability and to avoid manual updates across different configuration files, consider using a more dynamic versioning strategy or a dedicated version management tool.
(https://github.com/bitcoin/bitcoin/pull/33476#discussion_r2390343614)
## 💡 Improvement Needed
**Line:** 3
The version number `_CLIENT_VERSION_MINOR` is hardcoded. For better maintainability and to avoid manual updates across different configuration files, consider using a more dynamic versioning strategy or a dedicated version management tool.
💬 starkshade commented on pull request "[28.x] backports + 28.3rc1":
(https://github.com/bitcoin/bitcoin/pull/33476#discussion_r2390343984)
## 💡 Improvement Needed
**Line:** 4
The version number `v28.3.0rc1` in the NAME section should be updated to match the version specified in the `.TH` directive (line 2). This ensures consistency throughout the manual page.
(https://github.com/bitcoin/bitcoin/pull/33476#discussion_r2390343984)
## 💡 Improvement Needed
**Line:** 4
The version number `v28.3.0rc1` in the NAME section should be updated to match the version specified in the `.TH` directive (line 2). This ensures consistency throughout the manual page.
💬 starkshade commented on pull request "[28.x] backports + 28.3rc1":
(https://github.com/bitcoin/bitcoin/pull/33476#discussion_r2390343881)
## 💡 Improvement Needed
**Line:** 2
The version number `v28.3.0rc1` and the date `September 2025` appear to be inconsistent. If this is a release candidate, the date should reflect the development stage. If it's a stable release, the version number should be updated. This inconsistency can confuse users about the software's current status.
(https://github.com/bitcoin/bitcoin/pull/33476#discussion_r2390343881)
## 💡 Improvement Needed
**Line:** 2
The version number `v28.3.0rc1` and the date `September 2025` appear to be inconsistent. If this is a release candidate, the date should reflect the development stage. If it's a stable release, the version number should be updated. This inconsistency can confuse users about the software's current status.
💬 starkshade commented on pull request "[28.x] backports + 28.3rc1":
(https://github.com/bitcoin/bitcoin/pull/33476#discussion_r2390344184)
## 💡 Improvement Needed
**Line:** 708
The default value for `-minrelaytxfee` has been decreased from `0.00001` to `0.000001`. This change in a critical fee parameter warrants a more detailed explanation in the documentation regarding the reasoning and potential impact on transaction relaying and mining. Consider adding a brief note about the implications of this reduced default.
(https://github.com/bitcoin/bitcoin/pull/33476#discussion_r2390344184)
## 💡 Improvement Needed
**Line:** 708
The default value for `-minrelaytxfee` has been decreased from `0.00001` to `0.000001`. This change in a critical fee parameter warrants a more detailed explanation in the documentation regarding the reasoning and potential impact on transaction relaying and mining. Consider adding a brief note about the implications of this reduced default.
💬 starkshade commented on pull request "[28.x] backports + 28.3rc1":
(https://github.com/bitcoin/bitcoin/pull/33476#discussion_r2390344408)
## 💡 Improvement Needed
**Line:** 4
The version number in the NAME section should be updated to `v28.3.0rc1` to accurately reflect the current release of `bitcoin-tx`.
(https://github.com/bitcoin/bitcoin/pull/33476#discussion_r2390344408)
## 💡 Improvement Needed
**Line:** 4
The version number in the NAME section should be updated to `v28.3.0rc1` to accurately reflect the current release of `bitcoin-tx`.
💬 starkshade commented on pull request "[28.x] backports + 28.3rc1":
(https://github.com/bitcoin/bitcoin/pull/33476#discussion_r2390344078)
## 💡 Improvement Needed
**Line:** 18
The version number `v28.3.0rc1` in the DESCRIPTION section should be updated to match the version specified in the `.TH` directive (line 2) and the NAME section (line 4). This ensures consistency throughout the manual page.
(https://github.com/bitcoin/bitcoin/pull/33476#discussion_r2390344078)
## 💡 Improvement Needed
**Line:** 18
The version number `v28.3.0rc1` in the DESCRIPTION section should be updated to match the version specified in the `.TH` directive (line 2) and the NAME section (line 4). This ensures consistency throughout the manual page.
💬 starkshade commented on pull request "[28.x] backports + 28.3rc1":
(https://github.com/bitcoin/bitcoin/pull/33476#discussion_r2390345094)
## 💡 Improvement Needed
**Line:** 4
The version number `v28.3.0rc1` in the NAME section should be consistent with the version specified in the `.TH` directive (line 2) and the DESCRIPTION section (line 6). This ensures accurate and unified version information throughout the manual page.
(https://github.com/bitcoin/bitcoin/pull/33476#discussion_r2390345094)
## 💡 Improvement Needed
**Line:** 4
The version number `v28.3.0rc1` in the NAME section should be consistent with the version specified in the `.TH` directive (line 2) and the DESCRIPTION section (line 6). This ensures accurate and unified version information throughout the manual page.
💬 starkshade commented on pull request "[28.x] backports + 28.3rc1":
(https://github.com/bitcoin/bitcoin/pull/33476#discussion_r2390344715)
## 💡 Improvement Needed
**Line:** 4
The version number in the NAME section of the manual page should be updated to reflect the current release. The current entry shows 'v28.3.0rc1', which indicates a release candidate. For a stable release, this should be updated to the final version number.
(https://github.com/bitcoin/bitcoin/pull/33476#discussion_r2390344715)
## 💡 Improvement Needed
**Line:** 4
The version number in the NAME section of the manual page should be updated to reflect the current release. The current entry shows 'v28.3.0rc1', which indicates a release candidate. For a stable release, this should be updated to the final version number.
💬 starkshade commented on pull request "[28.x] backports + 28.3rc1":
(https://github.com/bitcoin/bitcoin/pull/33476#discussion_r2390344263)
## 💡 Improvement Needed
**Line:** 735
The default value for `-blockmintxfee` has been significantly reduced from `0.00001` to `0.00000001`. This change has substantial implications for which transactions are considered for block inclusion. The documentation should include a clear explanation of the rationale behind this drastic reduction and any anticipated effects on transaction propagation and block composition.
(https://github.com/bitcoin/bitcoin/pull/33476#discussion_r2390344263)
## 💡 Improvement Needed
**Line:** 735
The default value for `-blockmintxfee` has been significantly reduced from `0.00001` to `0.00000001`. This change has substantial implications for which transactions are considered for block inclusion. The documentation should include a clear explanation of the rationale behind this drastic reduction and any anticipated effects on transaction propagation and block composition.
💬 starkshade commented on pull request "[28.x] backports + 28.3rc1":
(https://github.com/bitcoin/bitcoin/pull/33476#discussion_r2390344607)
## 💡 Improvement Needed
**Line:** 2
The version number in the manual page should be updated to reflect the current release. The current entry shows 'v28.3.0rc1', which indicates a release candidate. For a stable release, this should be updated to the final version number.
(https://github.com/bitcoin/bitcoin/pull/33476#discussion_r2390344607)
## 💡 Improvement Needed
**Line:** 2
The version number in the manual page should be updated to reflect the current release. The current entry shows 'v28.3.0rc1', which indicates a release candidate. For a stable release, this should be updated to the final version number.
💬 starkshade commented on pull request "[28.x] backports + 28.3rc1":
(https://github.com/bitcoin/bitcoin/pull/33476#discussion_r2390344497)
## 💡 Improvement Needed
**Line:** 12
The version number in the DESCRIPTION section should be updated to `v28.3.0rc1` to accurately reflect the current release of `bitcoin-tx`.
(https://github.com/bitcoin/bitcoin/pull/33476#discussion_r2390344497)
## 💡 Improvement Needed
**Line:** 12
The version number in the DESCRIPTION section should be updated to `v28.3.0rc1` to accurately reflect the current release of `bitcoin-tx`.
💬 starkshade commented on pull request "[28.x] backports + 28.3rc1":
(https://github.com/bitcoin/bitcoin/pull/33476#discussion_r2390343799)
## 💡 Improvement Needed
**Line:** 5
The version number `_CLIENT_VERSION_RC` is hardcoded. For better maintainability and to avoid manual updates across different configuration files, consider using a more dynamic versioning strategy or a dedicated version management tool.
(https://github.com/bitcoin/bitcoin/pull/33476#discussion_r2390343799)
## 💡 Improvement Needed
**Line:** 5
The version number `_CLIENT_VERSION_RC` is hardcoded. For better maintainability and to avoid manual updates across different configuration files, consider using a more dynamic versioning strategy or a dedicated version management tool.
💬 starkshade commented on pull request "[28.x] backports + 28.3rc1":
(https://github.com/bitcoin/bitcoin/pull/33476#discussion_r2390345189)
## 💡 Improvement Needed
**Line:** 6
The version number `v28.3.0rc1` in the DESCRIPTION section should be consistent with the version specified in the `.TH` directive (line 2) and the NAME section (line 4). This ensures accurate and unified version information throughout the manual page.
(https://github.com/bitcoin/bitcoin/pull/33476#discussion_r2390345189)
## 💡 Improvement Needed
**Line:** 6
The version number `v28.3.0rc1` in the DESCRIPTION section should be consistent with the version specified in the `.TH` directive (line 2) and the NAME section (line 4). This ensures accurate and unified version information throughout the manual page.
💬 starkshade commented on pull request "[28.x] backports + 28.3rc1":
(https://github.com/bitcoin/bitcoin/pull/33476#discussion_r2390345411)
## 💡 Improvement Needed
**Line:** 733
The default value for `blockmintxfee` has been changed from `0.00001` to `0.00000001`. This is a substantial decrease and should be clearly communicated as a potentially impactful change for users, possibly with a note about its implications for transaction fees and block inclusion.
(https://github.com/bitcoin/bitcoin/pull/33476#discussion_r2390345411)
## 💡 Improvement Needed
**Line:** 733
The default value for `blockmintxfee` has been changed from `0.00001` to `0.00000001`. This is a substantial decrease and should be clearly communicated as a potentially impactful change for users, possibly with a note about its implications for transaction fees and block inclusion.
💬 luke-jr commented on pull request "RPC: add sendrawtransactiontopeer":
(https://github.com/bitcoin/bitcoin/pull/33507#discussion_r2390335595)
This feels better as a named-only param.
(https://github.com/bitcoin/bitcoin/pull/33507#discussion_r2390335595)
This feels better as a named-only param.
💬 luke-jr commented on pull request "RPC: add sendrawtransactiontopeer":
(https://github.com/bitcoin/bitcoin/pull/33507#discussion_r2390359165)
This doesn't belong in rpc/mempool since it never touches the mempool...?
(https://github.com/bitcoin/bitcoin/pull/33507#discussion_r2390359165)
This doesn't belong in rpc/mempool since it never touches the mempool...?
💬 luke-jr commented on pull request "RPC: add sendrawtransactiontopeer":
(https://github.com/bitcoin/bitcoin/pull/33507#discussion_r2390338390)
Probably should include the (more likely to be used) "maxfeerate" option too?
(https://github.com/bitcoin/bitcoin/pull/33507#discussion_r2390338390)
Probably should include the (more likely to be used) "maxfeerate" option too?
💬 luke-jr commented on pull request "RPC: add sendrawtransactiontopeer":
(https://github.com/bitcoin/bitcoin/pull/33507#discussion_r2390361071)
Seems like this ought to check if the peer accepted it, and if not, return the rejection reason.
(https://github.com/bitcoin/bitcoin/pull/33507#discussion_r2390361071)
Seems like this ought to check if the peer accepted it, and if not, return the rejection reason.
💬 maflcko commented on pull request "build: Drop support for EOL macOS 13":
(https://github.com/bitcoin/bitcoin/pull/33489#discussion_r2390376092)
> Upgrading Xcode 15.4 on macOS 14.4 requires updating macOS itself, at least to 14.5.
Correct. This should be no problem, because running on insecure minor releases is no different from running on EOL versions. See also the auto-upgrade: https://support.apple.com/guide/mac-help/software-update-settings-on-mac-mchla7037245/15.0/mac/15.0
> Therefore, the effective minimum supported macOS version becomes 14.5, not 14.0.
Correct. However, I don't think it is beneficial to micro-manage the
...
(https://github.com/bitcoin/bitcoin/pull/33489#discussion_r2390376092)
> Upgrading Xcode 15.4 on macOS 14.4 requires updating macOS itself, at least to 14.5.
Correct. This should be no problem, because running on insecure minor releases is no different from running on EOL versions. See also the auto-upgrade: https://support.apple.com/guide/mac-help/software-update-settings-on-mac-mchla7037245/15.0/mac/15.0
> Therefore, the effective minimum supported macOS version becomes 14.5, not 14.0.
Correct. However, I don't think it is beneficial to micro-manage the
...
💬 pejfat08-rgb commented on issue "Inconsistent CJDNS address handling in Local addresses and AddLocal logs":
(https://github.com/bitcoin/bitcoin/issues/33471#issuecomment-3350965244)
- [ ]
(https://github.com/bitcoin/bitcoin/issues/33471#issuecomment-3350965244)
- [ ]