App: DEX Swap Failure

Created on 1 Jun 2021  Â·  12Comments  Â·  Source: DeFiCh/app

Actual behavior: No Swap happend

Expected behavior: DEX Swap (DEFI -> USDT)

logs.zip

How to reproduce it (as minimally and precisely as possible): -

What are your environment parameters?

  • DeFi Wallet Version: 2.4.1
  • Operating System (OS): windows 10
    – Current free storage capacity: 200gb

Anything else we need to know?

I swapped 141 DEFI to USDT but I got no usdt out.
Transaktion: https://mainnet.defichain.io/#/DFI/mainnet/tx/7d49278f8a35534c1eeb31b096b5b82f7df410fd76996e3bc2e83a1e4d506395
Reddit post:
https://www.reddit.com/r/defiblockchain/comments/npq9j0/dex_swap_error/
logs.zip

kinbug needtriage owin versio2.4.1

All 12 comments

@happydayxxl: Thanks for opening an issue, it is currently awaiting triage.

The triage/accepted label can be added by foundation members by writing /triage accepted in a comment.

In the meantime, you can:

  1. Checkout DeFiChain’s Github issue page to see if your issue has already been reported
  2. Submit any logs if you have them, this will greatly expedite the process for us.
  3. You can also join our Telegram or Reddit community channels.

Details

I am a bot created to help the DeFiCh developers manage community feedback and contributions. You can check out my manifest file to understand my behavior and what I can do. If you want to use this for your project, you can check out the DeFiCh/oss-governance-bot repository.

image
Screenshot no output is shown

Hi @happydayxxl , v2.4.2 is out, this is a mandatory update. 
Please read through the release notes before updating.

Regarding your issue, the transaction went through, so there was not a dex failure. I also checked on the DeFi Explorer that your dUSDT was sent to dLkq..., can you check via CLI that the balance is reflected correctly? It could be just the UI tx history that's missing.

gettokenbalances
[
  "0.XXXXXXXX@0",
  "0.XXXXXXXX@1",
  "0.XXXXXXXX@2",
  "7.XXXXXXXX@3", — dUSDT
  "0.XXXXXXXX@4"
]

Hello izzycsy
Thanks for your response!
I also saw that this address: dLkq.. received it but this address not refleced my receiver addresses in my wallet.
I checked the cli with gettokenbalances and the 419.18350021 USDT are still missing.
I also checked the command "listaccounthistory" and not found this address.
But how could i swap when the address dLkq.. not mine?

Do you have any other ideas to solve the problem?

Hi @happydayxxl , can you try adding back dLkq... to your receive address?

Receive   Manually add address

In DEX, you've to state where to receive your tokens at.

DEX

Based on your logs, dLkq... does belong to you.
{"address":"dLkq...","label":"DEFI","id":"9XXX","ismine":true,"time":"2021-03-14T09:39:36.000Z","hdSeed":true},

Hi @happydayxxl , alternatively, you can update to v2.4.2, this is a mandatory update anyway. Please read through the release notes before updating. In this build includes a fix for any missing address issue that some users were facing.

Go to Settings > Rescan

Rescan

Hello thanks for responsing again :)
I tried to add the address but an error occours:
Invalid address. Please check this belongs to you.
image

hi, @izzycsy i also rescan the node with the newest version of the app but unfortunately without success. After that I tried again to add the address, but again "invalid address".

Hi @happydayxxl , can you backup your current wallet, and try another wallet.dat?

Menu bar   Backup Wallet

Now see the exchanged values! I haven't looked into the second wallet for a while...
I've been using the two wallets for half a year, but this never happens.
THANKS A LOT @izzycsy !

THANKS AGAIN FOR THE SUPPORT!

Hi @happydayxxl , make a new backup and continue using the new backup. Please keep your wallet.dat safe. Thank you.

Was this page helpful?
0 / 5 - 0 ratings

Related issues

RobinTorque picture RobinTorque  Â·  7Comments

jpressler picture jpressler  Â·  7Comments

gabriello79 picture gabriello79  Â·  4Comments

Rocky-81 picture Rocky-81  Â·  8Comments

RobinTorque picture RobinTorque  Â·  3Comments