Luke Dashjr

>>If both are provided, I would expect both to be active in parallel, and complete even if the other succeeds... >Kindly add some rationale for that? If the user has...

Why is the option of loading it from a file even in dev builds, not considered?

Concept NACK on removal. Users shouldn't be forced to upgrade their wallets (especially not on such a short timeline).

2024 is very soon. Keep in mind we have literally never removed support for older wallets before.

In light of descriptor wallets not having an upgrade path for non-HD wallets, I don't think legacy wallet support can be reasonably removed.

>Why specifically do you see that as a problem? Mainly performance issues (a SPKM for every existing key) and lack of builtin seed rotation. But it's also a security change,...

Does this reduce our safety against memory corruption or similar?

Can we split the fixes from the C++20 stuff? The latter shouldn't be backported...

I agree this feels more like it should be a wallet option.

>I'm somewhat puzzled why Knots and Inquisition are not running into the same issues Maybe because I switch the self-hosted CI to not-self-hosted?