< bitcoin-git>
[bitcoin] practicalswift opened pull request #16726: tests: Avoid common Python default parameter gotcha when mutable dict/list:s are used as default parameter values (master...python-mutable-default-parameter-values) https://github.com/bitcoin/bitcoin/pull/16726
< instagibbs>
20 days, I'd like to get this merged for 0.19, it shouldn't be too much to carry it across the finish
< instagibbs>
the confTarget arg was deprecated, having this feature would largely allay concerns about feature being deprecated without suitable replacement
< promag>
in that case I think it's fine if you take over
< instagibbs>
kinda sucks, was a new contributor, seemed sharp, I'll keep his authorship at least
< luke-jr>
hmm, if someone doesn't know the address they want to verify a signed message with, only knows the signature, can someone change the message, replace the address to fit the new message, and then sign other messages with the same address? at face value, I think they would still at least need the original private key, right?
< achow101>
luke-jr: given a message and signature, you can get a pubkey and thus "forge" a signature for that pubkey. of course you don't know the private key for that pubkey.
< sipa>
if the message includes the address i believe this is not possible