Skip to content
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

Porto Network Problem with Wallets starting with 0x0 not being identified #894

Open
OneOfArslan opened this issue Nov 21, 2024 · 1 comment

Comments

@OneOfArslan
Copy link

Transactions of wallets starting with 0x0 are still not processed in the Porto network. I experienced this on Yuzuswap in the past weeks, and now on Mosaic dex. When we look at Movement Explorer regarding the transaction, you can see that it does not read the second zero at 0x0 in the Sender section.

My Porto Address: 0x04a74a38e9fdfa3e412c89a2f7f6e2a5feef05080f175510934b0881b5d32f97

mos1
As you can see, I made a 100 USDT/Move transaction and it says the transaction was completed. This is the transaction tx : https://explorer.movementnetwork.xyz/txn/0x25eef995b6569f34edfe3bc00de3965ce12fd84f627d60a1e832089f3baa0bb2?network=porto+testnet

When we look at the transaction result form, my wallet, which should be seen as 0x04 in the Sender section, starts with 0x4 and there is no change in the balances in my wallet. I made many transactions during the day today and it happened like this in all of them.

In the 0.01 Move/ Usdt transaction, the transaction is completed, but in the sender section, the wallet address appears as 0x4 instead of 0x04. Additionally, when I traded this parity during the day, the Move balance was decreasing, but the USDT balance was not changing.

https://explorer.movementnetwork.xyz/txn/0xaf561db0c00e5f36257b046e45a30a061f07ed4ed4f612f42dcda00dfba80be2?network=porto+testnet
ewe

When I make a 20 USDT/Move transaction, although there is no change in the USDT and Move parities in the wallet balance, the transaction is said to have been completed and a tx is created and again, in the Sender section, the wallet address is written as 0x4 instead of 0x04.

https://explorer.movementnetwork.xyz/txn/0x632e19168342710a8e705570f449fccd300937648bca230d61d517fcc3fb0a80?network=porto+testnet
sssss

As a result, the network is not working stable and therefore the Okx Mosaic Galxe task on the testnet cannot be performed.

Twitter: @OneOfArslan
Discord: arslan48
Mail: [email protected]

@0xhiro00
Copy link

Hi @OneOfArslan ,

This is Harry from Mosaic. Thank you for bringing this issue to our attention. It’s a somewhat tricky problem related to the two different asset standards on the Move Aptos network: Coin and FungibleAsset.

Here’s what happened: the output of your swap was USDT in the Coin standard. However, at that time, Mosaic was only displaying balances for USDT as a FungibleAsset. This is why your USDT balance didn’t update, and it also explains the issue you encountered with Interest. As Mosaic and Interest are currently the only platforms supporting the FungibleAsset standard, this discrepancy caused some confusion.

In response to your feedback, we’ve improved our UI to display balances for both Coin and FungibleAsset. Additionally, we’ve introduced a feature allowing users to migrate from Coin to FungibleAsset with just one click.

In the image below (improved Mosaic), you can see the same asset can have both Coin and FungibleAsset stores:

image

Please give it a try! Mosaic is proud to be the first platform enabling seamless swaps between Coin and FungibleAsset across the Move Aptos networks. While this innovation may lead to some unexpected experiences, we deeply value your feedback and are committed to continuously improving our product.

Thank you!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants