-
Notifications
You must be signed in to change notification settings - Fork 94
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[BUG]: Recipients displaying not properly for transaction to segwit addresses. Tx history is requested for legacy address. #1055
Comments
This is definitely a bug as Segwit was not implemented for tx history.
I can see the problem is in https://github.com/KomodoPlatform/atomicDEX-API/blob/41170748db961f23aa8a10fffc3de09a2bd81aa9/mm2src/coins/utxo/utxo_common.rs#L1909 where WitnessScript has not been implemented yet for Also, there will be a problem when using Will work on solving this this week |
@tonymorony Could you please test if the problems are fixed in the dev branch? |
@smk762 could you please help with re-testing it on the latest dev? approx test-plan:
|
I loaded up a wallet which already had some tx for both segwit and legacy - both showed correct tx history for type out of the box. Activating segwit address, I sent to both a legacy and a different segwit address - both were added to the history when segwit activated, and not shown when legacy activated. Amounts, fees, and addresses in tx history all matching what is shown on explorer 👍 |
@artemii235 Is further testing required here or can we close this issue? |
I think no further testing is required, thanks! I'm closing the issue. |
I've sent funds to
ltc1q5x0h4gj5mnks59ujp2cu9t8knzzp7elkrw5uhr
https://blockexplorer.one/litecoin/mainnet/tx/9bcf7736e4cc46551a137ebda5e53f3bfd6f775b92c1155afcae7b77947cf33c
but app displaying change (sending) address as a recipient:
it comes from API response, so transferred here:
am I need to have segwit enabled to see segwit addresses in tx history?
The text was updated successfully, but these errors were encountered: