pythcoiner

> Using Liana's scheme will work for any wallet policy that does not have duplicate public keys. However, if choosing a policy that contains duplicate public keys in the template,...

What i mainly wondering is: signing devices that have already followed Liana's approach will now have to mantain both. The only way i can imagine for having this standard being...

> when using wallet policies it's desirable to be able to derive the chaincode only from the BIP388 list of xpubs, without the wallet policy template. what about the case...

> Having the same key in some scenarios is acceptable. I think it's still better to avoid if we can > What is unacceptable is a descriptor or policy that...

Note: args for passing the log level seems to be different ont mempool implementation (maybe also esplora?), i need figure it out

afaik silent-payments work only w/ the taproot internal key not the taptree and a liana taproot "wallet"/account will always have a taptree. i've spend some time to wrap my head...

not clearly on the roadmap afaik, I personally think no user should use hot keys for other purpose than test networks

@scgbckbone how the wallet name is expected to be passed when importing a miniscript descriptor via sdcard or QR code?

unconfirmed means they are not count into balance?

@nondiremanuel should we close this in favor of #1375?