pull down to refresh

(Reposted to fix missing negation.)
Anyway, you shouldn't reuse addresses, so you should not be too worried about being able to keep the same one. Address reuse is one of the most prevalent and easiest to avoid privacy faux pas.
The exception would be if you're taking about a static address scheme like Silent Payments, where you use the static information to generate a fresh output script based on your inputs, but that's a completely different story in the first place, and I'd reckon it won't be for a while before anyone tries to combine that with multisig.
Thx for the explaination.
One more question:
If you have a multisig setup, do you have xpub as well, which can create new addresses?
reply
1045 sats \ 1 reply \ @Murch 5 Oct 2023
You usually would have multiple xpubs. For each participating key one, and you’d derive one subkey further down for each subsequent key. I.e. your first address would be key 0 on all three keychains, the second would be key 1 on all three keychains, etc.
I would suggest using a ranged output script descriptor instead, that way you could encode the entire output script template in one thing.
reply
Much appreciated @Murch
reply