Jeremy Rand

> As an alternative, what do you think about just flipping the default address type to segwit and not bothering with adding a choice in the UI? As long as...

Hmm, that said, AFAIK the main reason upstream still supports giving the user a choice is because Alice may want to receive coins from Bob, but Alice supports Bech32 while...

> Would it be more Fluid to make the Tick box backwards. As in just flipping the code to make the Tick Box represent Old addresses while Bech32 be the...

> I'm not sure about this. While it certainly makes the flow a bit easier, `fundrawtransaction`'s main function is to choose coins using wallet logic, which is not trivial to...

> @yanmaani The reason is fee computation and upstream [bitcoin/bitcoin#7879](https://github.com/bitcoin/bitcoin/issues/7879). If we can get upstream to solve this, I would be very happy myself, but I doubt it. @domob1812 If...

According to https://github.com/bitcoin/bitcoin/blob/master/doc/psbt.md#overall-workflow , PSBT metadata includes: > information about the scripts and public keys involved in each of the inputs (and possibly outputs) of the PSBT Which sounds like...

> @JeremyRand Yes indeed, I think the data should be present in PSBTs. I do not know if `fundpsbt` works with imported addresses in Bitcoin Core - if you got...

CSV was activated in Namecoin at the same time as SegWit. The fact that both of them are missing for Namecoin's GBT output is interesting. @domob1812 Is this disparity likely...

Thanks for the explanation @DrHaribo . I'm going to check with Poolin and Slush to see whether they can confirm or refute whether that was the cause of the issues...

FYI I started implementing validation for names (not values) since I need that for the name management GUI. Haven't gotten very far yet, but should have something in a few...