0

maybe you can help me. If this is not the correct avenue for customer service please direct me to the correct place.

I made a conversion within Coinbase Wallet and there is an error. Their customer service has explained to me that the error is actually with the exchange rate from Ox Protocol.

Transaction Hash:

0x164a35251c3ba060bf3afcaedd673c38381b203d300c9901d74185b0406f3dee

On 5/2/2022, I attempted to convert PYR (in my own Coinbase wallet) to USDC coin (in my Coinbase wallet). The amount was 243.50 PYR (roughly $2250 at the time). The transaction was completed. However, I only received $2 of the $2250.

The system miscalculated the conversion severely wrong, using the wrong price for PYR.

The correct conversion should have been roughly:

243 PYR x $9.25 each =$2247 (i understand that it won’t be exactly these numbers depending on the variables.)

The incorrect conversion that did happen on Coinbase:

243PYR x $0.00001 each token = $2.43

This weird transaction has cost me over $2000 and I believe it to be an error completely out of my control. I hope this issue can be resolved.

1 Answer 1

0

Thank you for your patience while we investigated what occurred in this trade. PYR is not traded on any mainnet DEXs, so the trade was filled via a limit order. Unfortunately, at this instance, there was an open limit order at the rate you received which was the “best” price.

You can see the Exchange options available for PYR here in CoinGecko (note there are no Dex options on mainnet).

You can check the full details on the trade route here, specifically note the LimitOrderFilled function in line 33 of Emitted Events, and the values in “Token transfers” section.

In this case, the api logic functioned as expected, unfortunately, we understand not financially favorably. We would recommend reaching out to Coinbase about ways to improve their UI/UX, possibly adding warnings when such a drastic trade is about to be executed.

2
  • Coinbase has pawned off all responsibility. Citing that I should have somehow realized (even though I had no opportunity to do so) that I was about to lose 99% of my investment on a trade that was essentially supposed to be “cashing out” into USDC. If I may ask, why do neither of you (Coinbase or 0x) have a rejection system that would reject this exact scenario where the “best” rate is actually the worst possible rate imaginable. There is no limit to how much your api will allow a user to lose on one given transaction? Commented May 19, 2022 at 19:20
  • I am not an expert in this area at all but from my POV, the api of both CB Wallet and 0x failed to realize that “working as expected” is clearly not working as expected (especially in this transaction using a 1-for-1 stable coin) When the exchange rate that is used for the given transaction is 99% different than the exchange rate for the two tokens in use, something somewhere is wrong. But neither party is accepting responsibility and I will have to lose all this money even though I did nothing wrong. Retrospectively, i actually did everything right, looking at how the market has turned since. Commented May 19, 2022 at 19:31

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service and acknowledge you have read our privacy policy.

Not the answer you're looking for? Browse other questions tagged or ask your own question.