Home
/
Community insights
/
Trader experiences
/

Lost usdt and dai in eth swap on bnb network: a shocking case

Users Voice Frustration | Swapped DAI and USDT for ETH, Ended Up Empty Handed

By

Oliver Smith

Jul 13, 2026, 03:52 PM

Edited By

Alice Wong

2 minutes reading time

A person looking at a computer screen with a worried expression, frustrated over a failed ETH swap on the BNB network. There are graphics of USDT and DAI tokens, with a question mark above them, symbo...

A recent incident involving transactions in the BNB network left users feeling frustrated and confused. A person reported swapping 200 DAI and USDT for ETH tokens only to receive nothing in return. The complaint drew attention from various forums as others shared similar experiences.

What Happened?

On July 8, a user attempted to swap 200 DAI and USDT into ETH tokens on the BNB network. After the first transaction, the user noticed the transaction was marked as "unlimited" but did not receive any ETH. They presumed the network was just slow and closed the app, having swapped tokens before without issue.

Upon reviewing the wallet later, the user found 196 DAI became 96 DAI and was still without any ETH. The situation led to many questions among fellow crypto enthusiasts regarding the network's processes.

"I havenโ€™t got any ETH in return! Anyone can help?" - User

User Reactions

Users rallied around the issue, offering suggestions and advice. Key points made in the user discussions include:

  • Reporting Issues: Many advised reporting the incident to support teams but emphasized the importance of sharing transaction hash details for better assistance.

  • Transaction Understanding: Some pointed out that the first transaction might have been just an approval to swap, not the actual token exchange. "You need to actually swap it now that it's approved to swap," one user noted.

  • Frustration Levels: The overall sentiment in responses reflected confusion and irritation, with some requesting clearer processes from the exchanges.

Key Points from the Discussion

  • โ—‡ Many transactions are confusing; clarity is needed.

  • โ—‡ Users suggest contacting support quickly for unresolved issues.

  • โ—‡ "That was just the approval you signed" - Reminder from a respondent.

What's Next?

As the incident unfolds, users continue to seek answers about the functioning of the BNB network. Crypto enthusiasts are asking if this scenario reveals deeper issues within transaction processes. Will exchanges provide improved transparency before another such mishap occurs?

The overall community remains engaged, with many keeping a close eye on developments regarding transaction reliability and support response times.

Possible Outcomes on the Horizon

Looking ahead, it seems likely that exchanges will need to address this confusion quickly. There's a strong chance that clearer communication protocols will be implemented, especially around transaction types and statuses. Given the current landscape of reporting frustrations, experts estimate around 60% of users may demand support reforms to ensure transparency during transactions. Additionally, if incidents like this continue without resolution, it could prompt more widespread calls for regulatory oversight. Such developments may shift how crypto platforms operate, compelling them to streamline processes with greater clarity to avoid alienating their core user base.

A Historical Echo from Beyond

Reflecting on the evolution of digital payments, a fitting analogy can be drawn to the tumultuous transition from cash to credit cards in the late 20th century. Just as frustrations arose with novel payment systems that weren't fully understood, many experienced pitfalls while adapting to credit card technology. The struggle to navigate approvals and limits mirrored the crypto users today grappling with token exchanges. This similarity underscores the innate human challenge when adapting to new financial technologies: initial bumps can lead to improved systems, often out of necessity for customer trust and education.