ghost43
ghost43
> My thinking was slightly different than what you're proposing: namely restricting the existing scheme in BIP173 to just length 20 and 32, and then (either later or at the...
re "The sign path is unusual" with Electrum, please see https://github.com/spesmilo/electrum/pull/6512#issuecomment-677643302 As in that comment, ideally we would need small changes in the firmware.
You probably need to increase the fee even more? Also, I guess EPS returns errors differently than e-x. e-x would trigger this line https://github.com/spesmilo/electrum/blob/570c0aeca39e56c742b77380ec274d178d660c29/electrum/network.py#L865 while it seems EPS triggers https://github.com/spesmilo/electrum/blob/570c0aeca39e56c742b77380ec274d178d660c29/electrum/network.py#L872...
Any idea how to reproduce?
I think I've seen a similar refresh bug recently but failed to reproduce it a second time then. I cannot reproduce this either now :/ I've tried on macOS 10.15...
Commits https://github.com/spesmilo/electrum/commit/444dc7fb7f6792450ce2ad89df26cca89d46940e and https://github.com/spesmilo/electrum/commit/60e2ad43161a39607276a76695f6628175b46fd3 fix a similar refresh bug, although it does not match exactly the description in the OP. > After restarting electrum it shows up in Coins tab,...
https://github.com/spesmilo/electrum/blob/4.0.3/electrum/address_synchronizer.py#L236 looks like the tx has zero inputs.
> if a request R1 is paid with lightning, its address will be reused in another payment request R2. if R2 is paid onchain, you will see the tx hash...
There is another related bug/weirdness pre-existing on master: if we get paid onchain, for an expired request, we still progress that to paid. And as we reuse addresses for requests...
https://github.com/spesmilo/electrum/blob/ae15bccb8192532afc4908b43f68797cd6239fd6/electrum/gui/qt/main_window.py#L2530