I guess it's a little unnecessary to also do this from dash electrum but OTOH maybe these extra privacy features bring a certain type of user to dash electrum? I mean, the more dash electrum differentiates itself from the DCG wallet, the more users it's going to get. Or maybe there is a way to simplify the atomic swap process further, like some kind of automatic pairing? - I haven't really thought that part through but maybe it gives you some ideas.
Anyway, I'd be interested to see extra privacy features that DCG is unwilling to put in their own wallet.
Dash Electrum 220.127.116.11 released
Available at https://github.com/akhavr/electrum-dash/releases/tag/18.104.22.168 or via your usual update method (Ubuntu PPA, Google Play, f-droid)
# Release 22.214.171.124
* kivy: fix history screen tx_type processing (#207)
* qt: pass InvoiceExt data to do_pay_invoice (#209)
* kivy/qt: fix tx_type handling (#210)
I've thought about this. This won't be an easy effort, even taking into account that heavy lifting was done by Bitcoin Electrum team. So first we'd do some work on alternative ways to do coinswap (see https://github.com/akhavr/electrum-dash/issues/197 for example) and then will proceed with lightning.Any thoughts on porting Payment Channels / Lightening Network to work with Dash Electrum?
- increased privacy
- demonstrating that dash is not entirely dependent on masternodes
- potential for cross chain swaps via LN on other networks