💬 vasild commented on pull request "net, init: derive default onion port if a user specified a -port":
(https://github.com/bitcoin/bitcoin/pull/31223#issuecomment-2470680219)
> It's important to make this clear in the release notes.
Note that the problem this PR is trying to resolve has a release note and an easy workaround. We are here because some people (many?) didn't read the release notes even after encountering the problem (second bitcoind refuses to start because of port collision). A startup failure is an error that cannot be ignored. Whereas a silent breakage of the hidden service could remain unnoticed for a long time - one would have to check the number
...
(https://github.com/bitcoin/bitcoin/pull/31223#issuecomment-2470680219)
> It's important to make this clear in the release notes.
Note that the problem this PR is trying to resolve has a release note and an easy workaround. We are here because some people (many?) didn't read the release notes even after encountering the problem (second bitcoind refuses to start because of port collision). A startup failure is an error that cannot be ignored. Whereas a silent breakage of the hidden service could remain unnoticed for a long time - one would have to check the number
...
💬 instagibbs commented on pull request "Ephemeral Dust":
(https://github.com/bitcoin/bitcoin/pull/30239#issuecomment-2470681103)

rebased due to conflict with merge of https://github.com/bitcoin/bitcoin/pull/30592
going to go over all outstanding comments
(https://github.com/bitcoin/bitcoin/pull/30239#issuecomment-2470681103)

rebased due to conflict with merge of https://github.com/bitcoin/bitcoin/pull/30592
going to go over all outstanding comments
💬 polespinasa commented on pull request "wallet, rpc: Settxfeerate":
(https://github.com/bitcoin/bitcoin/pull/31278#issuecomment-2470706357)
The functional test runs correctly on my local environment:
``64/313 - rpc_settxfeerate.py passed, Duration: 1 s``
I don't know if anything needs to be done in the IC to run the tests correctly.
Help regarding this is greatly appreciated.
(https://github.com/bitcoin/bitcoin/pull/31278#issuecomment-2470706357)
The functional test runs correctly on my local environment:
``64/313 - rpc_settxfeerate.py passed, Duration: 1 s``
I don't know if anything needs to be done in the IC to run the tests correctly.
Help regarding this is greatly appreciated.
💬 instagibbs commented on pull request "Ephemeral Dust":
(https://github.com/bitcoin/bitcoin/pull/30239#discussion_r1838215999)
should be the same, or even better since it's not being fetched from the mempool?
(https://github.com/bitcoin/bitcoin/pull/30239#discussion_r1838215999)
should be the same, or even better since it's not being fetched from the mempool?
💬 instagibbs commented on pull request "Ephemeral Dust":
(https://github.com/bitcoin/bitcoin/pull/30239#discussion_r1838230470)
If it's not in mempool or the package, then it can't have unconfirmed dust. Is there a scenario you're concerned about?
(https://github.com/bitcoin/bitcoin/pull/30239#discussion_r1838230470)
If it's not in mempool or the package, then it can't have unconfirmed dust. Is there a scenario you're concerned about?
💬 instagibbs commented on pull request "Ephemeral Dust":
(https://github.com/bitcoin/bitcoin/pull/30239#discussion_r1838232378)
might be heretical but I find as-is easier to read? Can add to follow-up if demand is there.
(https://github.com/bitcoin/bitcoin/pull/30239#discussion_r1838232378)
might be heretical but I find as-is easier to read? Can add to follow-up if demand is there.
💬 instagibbs commented on pull request "Ephemeral Dust":
(https://github.com/bitcoin/bitcoin/pull/30239#discussion_r1838237284)
I probably used it more than once before, will remove in follow-up
(https://github.com/bitcoin/bitcoin/pull/30239#discussion_r1838237284)
I probably used it more than once before, will remove in follow-up
💬 instagibbs commented on pull request "Ephemeral Dust":
(https://github.com/bitcoin/bitcoin/pull/30239#discussion_r1838238296)
good idea, will rename in follow-up
(https://github.com/bitcoin/bitcoin/pull/30239#discussion_r1838238296)
good idea, will rename in follow-up
💬 instagibbs commented on pull request "Ephemeral Dust":
(https://github.com/bitcoin/bitcoin/pull/30239#discussion_r1838239454)
think we're sticking with 0-fee both base and modified
(https://github.com/bitcoin/bitcoin/pull/30239#discussion_r1838239454)
think we're sticking with 0-fee both base and modified
💬 instagibbs commented on pull request "Ephemeral Dust":
(https://github.com/bitcoin/bitcoin/pull/30239#discussion_r1838240592)
will touch on follow-up
(https://github.com/bitcoin/bitcoin/pull/30239#discussion_r1838240592)
will touch on follow-up
💬 instagibbs commented on pull request "Ephemeral Dust":
(https://github.com/bitcoin/bitcoin/pull/30239#discussion_r1838241720)
will touch on followup
(https://github.com/bitcoin/bitcoin/pull/30239#discussion_r1838241720)
will touch on followup
💬 instagibbs commented on pull request "Ephemeral Dust":
(https://github.com/bitcoin/bitcoin/pull/30239#discussion_r1838243525)
will handle on follow-up
(https://github.com/bitcoin/bitcoin/pull/30239#discussion_r1838243525)
will handle on follow-up
💬 instagibbs commented on pull request "Ephemeral Dust":
(https://github.com/bitcoin/bitcoin/pull/30239#discussion_r1838244559)
will touch in follow-up
(https://github.com/bitcoin/bitcoin/pull/30239#discussion_r1838244559)
will touch in follow-up
💬 instagibbs commented on pull request "Ephemeral Dust":
(https://github.com/bitcoin/bitcoin/pull/30239#discussion_r1838246221)
It shouldn't effect the complexity much, as the cost is scanning all the parents' outputs
(https://github.com/bitcoin/bitcoin/pull/30239#discussion_r1838246221)
It shouldn't effect the complexity much, as the cost is scanning all the parents' outputs
💬 instagibbs commented on pull request "Ephemeral Dust":
(https://github.com/bitcoin/bitcoin/pull/30239#discussion_r1838251721)
will touch in follow-up
(https://github.com/bitcoin/bitcoin/pull/30239#discussion_r1838251721)
will touch in follow-up
💬 instagibbs commented on pull request "Ephemeral Dust":
(https://github.com/bitcoin/bitcoin/pull/30239#discussion_r1838253911)
I'll consider the other comment's suggestions, but this really is just a belt and suspenders, the caller is given no guarantees on if you're calling with nullptrs.
(https://github.com/bitcoin/bitcoin/pull/30239#discussion_r1838253911)
I'll consider the other comment's suggestions, but this really is just a belt and suspenders, the caller is given no guarantees on if you're calling with nullptrs.
💬 instagibbs commented on pull request "Ephemeral Dust":
(https://github.com/bitcoin/bitcoin/pull/30239#discussion_r1838255351)
good point, will take a look in followup
(https://github.com/bitcoin/bitcoin/pull/30239#discussion_r1838255351)
good point, will take a look in followup
💬 instagibbs commented on pull request "Ephemeral Dust":
(https://github.com/bitcoin/bitcoin/pull/30239#discussion_r1838256440)
maybe touch in follow-up
(https://github.com/bitcoin/bitcoin/pull/30239#discussion_r1838256440)
maybe touch in follow-up
💬 instagibbs commented on pull request "Ephemeral Dust":
(https://github.com/bitcoin/bitcoin/pull/30239#discussion_r1838257019)
will touch in follow-up
(https://github.com/bitcoin/bitcoin/pull/30239#discussion_r1838257019)
will touch in follow-up
💬 instagibbs commented on pull request "Ephemeral Dust":
(https://github.com/bitcoin/bitcoin/pull/30239#discussion_r1838257543)
will touch in follow-up
(https://github.com/bitcoin/bitcoin/pull/30239#discussion_r1838257543)
will touch in follow-up