Incomplete Txs on TRX -> USDT

[gomesalexandre]

Overview

Noticing incomplete Txs on TRX -> USDT

See the first swap here out of the two has only outbound part and is considered a receive, whereas the second test case (USDT -> TRX) has both parts

References and additional details

Spotted in 1.989.0 testing

Acceptance Criteria

• TRX → USDT swaps display both inbound and outbound components correctly

Screenshots/Mockups

https://jam.dev/c/58e509e5-5a12-455c-98c7-b9b6658bdcac

[coderabbitai]

📝 CodeRabbit Plan Mode

Generate an implementation plan and prompts that you can use with your favorite coding agent.

• Create Plan

Examples

• Example 1
• Example 2

---

🔗 Related PRs

#11283 - fix: implement proper TRON getTransaction and fix Sun.io status checking [merged]
#11309 - fix: cetus missing execution price [merged]
#11348 - fix: prevent Sun.io false transaction failures on Tron [merged]
#11449 - feat: tron parseTx() handle transfers [merged]
#11513 - fix: swap notification using stale rate amounts [merged]

👤 Suggested Assignees

• gomesalexandre

---

🧪 Issue enrichment is currently in open beta.

You can configure auto-planning by selecting labels in the issue_enrichment configuration.

To disable automatic issue enrichment, add the following to your .coderabbit.yaml:

issue_enrichment:
  auto_enrich:
    enabled: false

💬 Have feedback or questions? Drop into our discord or schedule a call!