[Bug]: Merge will take all positions even if only some of them were selected
Cosminauh opened this issue · 1 comments
Contact Details
Description
Merge will take all positions even if only some of them were selected
Node version
No response
Host machine
No response
Steps to reproduce
Merge will take all positions even if only some of them were selected.
Hash 27652c3a9ec62f754070ef08a4f2fba260e878b3005af500d93ceb5cce09a155
Steps to reproduce:
- After conversion multiple XMEX positions existed.
- Selected with checkbox to MERGE only 4 positions out of 5
- The transaction merged all 5 possition without permission
Target was to have a XMEX position to be unlocked in 2024 and other in 2025.
Now, a single position was created in to be unlocked in 2025.
Kindly correct the defect and repair the material loss. Now all my XMEX positions are merged to a single position instead of 2
with 2 different unlock dates.
On which network is the bug manifesting itself?
Mainnet
Relevant log output
No response
Code of Conduct
- I agree to follow this project's Code of Conduct
Thank you for the notification. Your report will be forwarded to the exchange team and investigated as soon as possible.
In hindsight, we always strongly recommend users to be wary and critic of the transactions they sign that they're always conforming the operations they are trying to perform.
This is not stated as an excuse for the team not to maintain a high standard of quality in the products we're developing. We are constantly striving for the best products that work without issues, but we want to remind users that they bear responsibility as well when signing and consenting to operations they want to perform.
Later edit:
Investigations show that your mentioned transaction was correctly processed for only 4 XMEX positions, as it can be seen in explorer:
371,974.31 XMEX-fda355-01
7,108,787.29 XMEX-fda355-07
59,747.97 XMEX-fda355-09
26,259,440.83 XMEX-fda355-0C
And resulted into one position of XMEX-fda355-20 in amount of 33,799,950.41
Due to the fact that you already had an existing position of XMEX-fda355-20 before merging, the new tokens that you received were added to those that existed, but this is not merging. This is pure balance addition for a token with similar properties, in this case, similar unlock schedule for XMEX.
On a side note, this is the repo for "The official implementation of the Elrond protocol, written in golang", it doesn't have anything to do with the Exchange. For future assistance, please reach out to the telegram support groups or the exchange related repos, such as sc-dex-rs.