💬 achow101 commented on pull request "test: fixing failing system_tests/run_command under some Locales":
(https://github.com/bitcoin/bitcoin/pull/30788#issuecomment-2329801442)
ACK ae48a22a3df086fb59843b7b814619ed5df7557b
(https://github.com/bitcoin/bitcoin/pull/30788#issuecomment-2329801442)
ACK ae48a22a3df086fb59843b7b814619ed5df7557b
✅ achow101 closed an issue: "test: "system_tests/run_command" unit test fails with different locale"
(https://github.com/bitcoin/bitcoin/issues/30608)
(https://github.com/bitcoin/bitcoin/issues/30608)
🚀 achow101 merged a pull request: "test: fixing failing system_tests/run_command under some Locales"
(https://github.com/bitcoin/bitcoin/pull/30788)
(https://github.com/bitcoin/bitcoin/pull/30788)
💬 achow101 commented on pull request "lint: Speed up and fix flake8 checks":
(https://github.com/bitcoin/bitcoin/pull/30723#issuecomment-2329824409)
ACK fafdb7df34507eee735893aa871da6ae529e6372
(https://github.com/bitcoin/bitcoin/pull/30723#issuecomment-2329824409)
ACK fafdb7df34507eee735893aa871da6ae529e6372
🚀 achow101 merged a pull request: "lint: Speed up and fix flake8 checks"
(https://github.com/bitcoin/bitcoin/pull/30723)
(https://github.com/bitcoin/bitcoin/pull/30723)
💬 ryanofsky commented on pull request "contrib: fix check-deps.sh to check for weak symbols":
(https://github.com/bitcoin/bitcoin/pull/30415#issuecomment-2329845810)
Rebased 2bca4af323c5b505689c5203e6ddba8becac5dc8 -> 76ef8113f70070ab1deeeb142977d46d8132c36e ([`pr/weakcheck.7`](https://github.com/ryanofsky/bitcoin/commits/pr/weakcheck.7) -> [`pr/weakcheck.8`](https://github.com/ryanofsky/bitcoin/commits/pr/weakcheck.8), [compare](https://github.com/ryanofsky/bitcoin/compare/pr/weakcheck.7-rebase..pr/weakcheck.8)) updating this to work with cmake and dropping suppression no longer needed after #30377
(https://github.com/bitcoin/bitcoin/pull/30415#issuecomment-2329845810)
Rebased 2bca4af323c5b505689c5203e6ddba8becac5dc8 -> 76ef8113f70070ab1deeeb142977d46d8132c36e ([`pr/weakcheck.7`](https://github.com/ryanofsky/bitcoin/commits/pr/weakcheck.7) -> [`pr/weakcheck.8`](https://github.com/ryanofsky/bitcoin/commits/pr/weakcheck.8), [compare](https://github.com/ryanofsky/bitcoin/compare/pr/weakcheck.7-rebase..pr/weakcheck.8)) updating this to work with cmake and dropping suppression no longer needed after #30377
💬 achow101 commented on pull request "ci: parse TEST_RUNNER_EXTRA into an array":
(https://github.com/bitcoin/bitcoin/pull/30244#issuecomment-2329850413)
ACK 8131bf7483c0ea10d3573c9f2e977d19d8569b7f
(https://github.com/bitcoin/bitcoin/pull/30244#issuecomment-2329850413)
ACK 8131bf7483c0ea10d3573c9f2e977d19d8569b7f
🚀 achow101 merged a pull request: "ci: parse TEST_RUNNER_EXTRA into an array"
(https://github.com/bitcoin/bitcoin/pull/30244)
(https://github.com/bitcoin/bitcoin/pull/30244)
🤔 glozow reviewed a pull request: "Ephemeral Dust"
(https://github.com/bitcoin/bitcoin/pull/30239#pullrequestreview-2278092199)
Looks good. New rules seem easier to reason about (up to 1 as long as 0-fee, must spend all of my parent's dust no matter what).
Can you remind me of the use cases of a keyed dust output again? It seems slightly safer to require ephemeral dust be P2A, as it would allow anybody to clean them up in case something goes wrong, but perhaps too narrow.
Additionally, could add a release note fragment.
(https://github.com/bitcoin/bitcoin/pull/30239#pullrequestreview-2278092199)
Looks good. New rules seem easier to reason about (up to 1 as long as 0-fee, must spend all of my parent's dust no matter what).
Can you remind me of the use cases of a keyed dust output again? It seems slightly safer to require ephemeral dust be P2A, as it would allow anybody to clean them up in case something goes wrong, but perhaps too narrow.
Additionally, could add a release note fragment.
💬 glozow commented on pull request "Ephemeral Dust":
(https://github.com/bitcoin/bitcoin/pull/30239#discussion_r1742455118)
```suggestion
return state.Invalid(TxValidationResult::TX_NOT_STANDARD, "dust", "tx has more than 1 dust output");
```
(https://github.com/bitcoin/bitcoin/pull/30239#discussion_r1742455118)
```suggestion
return state.Invalid(TxValidationResult::TX_NOT_STANDARD, "dust", "tx has more than 1 dust output");
```
💬 glozow commented on pull request "Ephemeral Dust":
(https://github.com/bitcoin/bitcoin/pull/30239#discussion_r1744281879)
could go in test_framework/mempool_util.py?
(https://github.com/bitcoin/bitcoin/pull/30239#discussion_r1744281879)
could go in test_framework/mempool_util.py?
💬 glozow commented on pull request "Ephemeral Dust":
(https://github.com/bitcoin/bitcoin/pull/30239#discussion_r1742455496)
```suggestion
return state.Invalid(TxValidationResult::TX_NOT_STANDARD, "dust", "tx with dust output must be 0 fee");
```
(https://github.com/bitcoin/bitcoin/pull/30239#discussion_r1742455496)
```suggestion
return state.Invalid(TxValidationResult::TX_NOT_STANDARD, "dust", "tx with dust output must be 0 fee");
```
💬 glozow commented on pull request "Ephemeral Dust":
(https://github.com/bitcoin/bitcoin/pull/30239#discussion_r1744291930)
```suggestion
self.log.info("Test that ephemeral dust is allowed for non-0 dust values")
```
(https://github.com/bitcoin/bitcoin/pull/30239#discussion_r1744291930)
```suggestion
self.log.info("Test that ephemeral dust is allowed for non-0 dust values")
```
💬 glozow commented on pull request "Ephemeral Dust":
(https://github.com/bitcoin/bitcoin/pull/30239#discussion_r1744323500)
if you make 1 a constexpr `MAX_DUST_OUTPUTS_PER_TX`, you can `static_assert` that it == 1 as an assumption in `CheckEphemeralSpends`
(https://github.com/bitcoin/bitcoin/pull/30239#discussion_r1744323500)
if you make 1 a constexpr `MAX_DUST_OUTPUTS_PER_TX`, you can `static_assert` that it == 1 as an assumption in `CheckEphemeralSpends`
💬 glozow commented on pull request "Ephemeral Dust":
(https://github.com/bitcoin/bitcoin/pull/30239#discussion_r1744296294)
I think all of these `assert_mempool_contents` can also have a `self.sync_mempools()` to check that the ephemeral dust packages propagate.
(https://github.com/bitcoin/bitcoin/pull/30239#discussion_r1744296294)
I think all of these `assert_mempool_contents` can also have a `self.sync_mempools()` to check that the ephemeral dust packages propagate.
💬 glozow commented on pull request "Ephemeral Dust":
(https://github.com/bitcoin/bitcoin/pull/30239#discussion_r1744310449)
```suggestion
// Now with dust, ok because the tx has no dusty parents
```
(https://github.com/bitcoin/bitcoin/pull/30239#discussion_r1744310449)
```suggestion
// Now with dust, ok because the tx has no dusty parents
```
💬 glozow commented on pull request "Ephemeral Dust":
(https://github.com/bitcoin/bitcoin/pull/30239#discussion_r1744335056)
Could comment that `tx_input.prevout.n` doesn't need to equal `map_tx_dust.at(tx_input.prevout.hash)`; a child can spend multiple outputs of a parent.
(https://github.com/bitcoin/bitcoin/pull/30239#discussion_r1744335056)
Could comment that `tx_input.prevout.n` doesn't need to equal `map_tx_dust.at(tx_input.prevout.hash)`; a child can spend multiple outputs of a parent.
💬 glozow commented on pull request "Ephemeral Dust":
(https://github.com/bitcoin/bitcoin/pull/30239#discussion_r1744312279)
```suggestion
const Txid& parent_txid = ephemeral_violation.value();
```
(https://github.com/bitcoin/bitcoin/pull/30239#discussion_r1744312279)
```suggestion
const Txid& parent_txid = ephemeral_violation.value();
```
💬 alphachart commented on pull request "p2p: detect addnode cjdns peers in GetAddedNodeInfo()":
(https://github.com/bitcoin/bitcoin/pull/30085#issuecomment-2329956541)
Shet
(https://github.com/bitcoin/bitcoin/pull/30085#issuecomment-2329956541)
Shet
💬 furszy commented on pull request "init: fix init fatal error on invalid negated option value":
(https://github.com/bitcoin/bitcoin/pull/30684#issuecomment-2330067124)
> May want to update the pr description to say this bug also when happens passing a double negated value, since the not_a_boolean case is really just a special case of that
yeah, thanks. Done. PR description updated.
(https://github.com/bitcoin/bitcoin/pull/30684#issuecomment-2330067124)
> May want to update the pr description to say this bug also when happens passing a double negated value, since the not_a_boolean case is really just a special case of that
yeah, thanks. Done. PR description updated.