Luke Dashjr

Agree with @mzumsande and @naumenkogs. Maybe not the same PR if it's substantially different, but the new eviction logic should be merged before this fix.

Should we perhaps add (and recommend, for non-GUI users), a `-resetguisettings` for non-GUI?

I'm not sure there's a reason to ever set +w either... maybe it should just be -rpccookieaccess user/group/all or something

Actually, why wouldn't fs::permissions work on Windows?

For your consideration, I have pushed a variant with some recommended changes here: https://github.com/luke-jr/bitcoin/commits/rpccookieperms-26%2Bknots/ Feel free to cherry-pick or squash into your PR as you deem best.

Knots 26.1 included this (with a few modifications). A user got stuck with a `.cookie.tmp` file that was read-only, and couldn't start Knots because the file couldn't be opened for...

My point was more that we should probably not be making cookie files read-only to begin with. So only `rw-r--r--`, `rw-r-----`, and `rw-------` should be supported. Bringing us back to...

QA failed

Feels like this could be confused with real/beancounter accounts like we used to support years ago. Maybe `hd_account` or something?

>BIP text here: https://github.com/instagibbs/bips/blob/ephemeral_anchor/bip-ephemeralanchors.mediawiki Node policy is not a subject matter for standardization in itself. It's the transaction format that the BIP (if there is one) should focus on, not...