💬 Mikaela11 commented on something "":
(https://github.com/bitcoin/bitcoin/commit/fa3b8162406bb21425a6fb5c6a96d17175545a4c#r153562187)
Michaela Lörinczová

🤔 glozow reviewed a pull request: "validation, fix: Use wtxid instead of txid in `CheckEphemeralSpends`"
(https://github.com/bitcoin/bitcoin/pull/32025#pullrequestreview-2674965082)
nice catch, concept ACK

💬 glozow commented on pull request "validation, fix: Use wtxid instead of txid in `CheckEphemeralSpends`":
(https://github.com/bitcoin/bitcoin/pull/32025#discussion_r1989504076)
callers typically use txid, so it's best to include both

```suggestion
strprintf("tx %s (wtxid=%s) did not spend parent's ephemeral dust", out_child_txid.ToString(), out_child_wtxid.ToString()));
```

💬 instagibbs commented on pull request "validation, fix: Use wtxid instead of txid in `CheckEphemeralSpends`":
(https://github.com/bitcoin/bitcoin/pull/32025#issuecomment-2714715220)
concept ACK, agree that txid should also be reported to user since that's used quite often by callers

💬 ryanofsky commented on issue "build: ccache doesn't hit across build dirs":
(https://github.com/bitcoin/bitcoin/issues/31994#issuecomment-2714742260)
> This interpretation of the Ccache documentation does not describe the actual behaviour on my different systems. I read "base_dir matches the CWD" as "base_dir equals the CWD". However, I might be wrong.

You are probably right but this behavior does not seem to make sense or correspond to documentation of base_dir. It is probably ok for us to force CCACHE_NOHASHDIR, but it seems like it would be safer if ccache just detected conditions it should and shouldn't hash CWD correctly itself. Ccache'
...

💬 hebasto commented on pull request "[POC] build: Use clang-cl to build on Windows natively":
(https://github.com/bitcoin/bitcoin/pull/31507#issuecomment-2714766273)
Rebased on https://github.com/bitcoin/bitcoin/pull/32028.

> > < to be added >
>
> It'd be good if this could actually be filled in, so it's clear what the goals are / what's trying to be acheived here.

Done.

💬 hebasto commented on pull request "Update `secp256k1` subtree to latest master":
(https://github.com/bitcoin/bitcoin/pull/32028#issuecomment-2714770025)
> > The latter is required for #31507.
>
> If we are going to start bumping subtrees, can you at least add a PR description, given 31507 [still doesn't have one](https://github.com/bitcoin/bitcoin/pull/31507#issuecomment-2548249261).

My apologies. Fixed.

💬 ryanofsky commented on pull request "cmake: Set top-level target output locations":
(https://github.com/bitcoin/bitcoin/pull/31161#issuecomment-2714781131)
I don't see a good reason to cause silent breakage here, but if that's what we want to do it seems fine (really) to merge 568fcdddaec2cc8decba5a098257f31729cc1caa anytime. Would just point to https://github.com/bitcoin/bitcoin/pull/31161#pullrequestreview-2644640989 to explain why silent failures are unnecessary and should be easy to avoid.

💬 hebasto commented on pull request "qt: 29.0 translations update":
(https://github.com/bitcoin/bitcoin/pull/32004#issuecomment-2714784268)
cc @darosior for sanity check of French (fr) translation.

💬 darosior commented on issue "29.0 RC Testing Guide Feedback":
(https://github.com/bitcoin/bitcoin/issues/32026#issuecomment-2714788716)
For pinholing could you encourage people to test against their router at home and share the result along with the model of their router at https://github.com/bitcoin/bitcoin/issues/31663?

💬 glozow commented on pull request "validation, fix: Use wtxid instead of txid in `CheckEphemeralSpends`":
(https://github.com/bitcoin/bitcoin/pull/32025#discussion_r1989585146)
Interestingly, the effect of inserting by the child's txid is that you get "missing inputs" instead of the slightly more correct "did not spend parent's ephemeral dust" from the `submitpackage` results. There is a result for both wtxid and txid in the map: we put "missing inputs" when we tried the child initially, and then failed to overwrite it (because we're using the wrong key here) the second time. The RPC code copies the result from a query by wtxid.

Here is the diff for `mempool_ephemer
...

💬 glozow commented on pull request "validation, fix: Use wtxid instead of txid in `CheckEphemeralSpends`":
(https://github.com/bitcoin/bitcoin/pull/32025#discussion_r1989591603)
Btw I'm not suggesting you add this exact diff to the PR (I had to comment out a part of the test). But it can be adapted into a regression test later.

💬 janb84 commented on issue "29.0 RC Testing Guide Feedback":
(https://github.com/bitcoin/bitcoin/issues/32026#issuecomment-2714960286)
> For pinholing could you encourage people to test against their router at home and share the result along with the model of their router at [#31663](https://github.com/bitcoin/bitcoin/issues/31663)?

@darosior
Thank you for your feedback! I've made several improvements:

- Added text with a link to the issue mentioned with a request to test and report.
- Implemented the missing successful PCP logging that was mentioned in the issue
- Added a clarifying statement to enable PCP if an attempt fa
...

💬 marcofleon commented on pull request "validation, fix: Use wtxid instead of txid in `CheckEphemeralSpends`":
(https://github.com/bitcoin/bitcoin/pull/32025#discussion_r1989708089)
Makes sense, thanks

💬 instagibbs commented on pull request "validation, fix: Use wtxid instead of txid in `CheckEphemeralSpends`":
(https://github.com/bitcoin/bitcoin/pull/32025#issuecomment-2715039398)
ACK https://github.com/bitcoin/bitcoin/pull/32025/commits/e637dc2c01c3b566e6c51c911c5881a8d206c924

Places the result in the map under txid, improving the reported error in certain cases, and typing future proofs against regressions automagically.

💬 hebasto commented on issue "build: ccache doesn't hit across build dirs":
(https://github.com/bitcoin/bitcoin/issues/31994#issuecomment-2715048334)
> > This interpretation of the Ccache documentation does not describe the actual behaviour on my different systems. I read "base_dir matches the CWD" as "base_dir equals the CWD". However, I might be wrong.
>
> You are probably right but this behavior does not seem to make sense or correspond to documentation of base_dir. It is probably ok for us to force CCACHE_NOHASHDIR, but it seems like it would be safer if ccache just detected conditions it should and shouldn't hash CWD correctly itself. C
...

💬 furszy commented on pull request "Wallet: "listreceivedby*" fix":
(https://github.com/bitcoin/bitcoin/pull/30972#discussion_r1989789588)
Since the `mapTally` loading procedure already performs the `IsMine` check, why can't we just use that instead of executing it again?

It seems to me that if an element exists in `mapTally`, we can be certain that everything inside it belongs to the wallet. Additionally, this element also includes an `nAmount` field. So, ideally, we could decouple the `mapTally` existence check from the "include empty" check, which would eliminate the second `IsMine()` call.

💬 achow101 commented on pull request "qt: 29.0 translations update":
(https://github.com/bitcoin/bitcoin/pull/32004#discussion_r1989790658)
This file has a bunch of these parentheticals that I think are also the pronunciations.

⚠️ BullishNode opened an issue: "Allow sending untrusted utxos in the sendtoaddress api"
(https://github.com/bitcoin/bitcoin/issues/32034)
### Please describe the feature you'd like to see added.

We would like to be able to send untrusted utxos via the sendtoaddress API.

Currently, we have to go through the createrawtransaction flow to achieved this.

While I understand why it may be a sane default to have not to allow that, there is also very good reasons. Bitcoin Core may assume that a coin is "untrusted" because it is unconfirmed and is not change, but it doesn't know that this coins is actually coming from a separate wallet t
...

💬 hebasto commented on pull request "Require sqlite when building the wallet":
(https://github.com/bitcoin/bitcoin/pull/31961#issuecomment-2715136288)
Building depends with `NO_SQLITE=1` makes no sense now, doesn't it?