611.76 XUSD stuck in a loan contract after a bridge misroute — looking for advice

General Commons
1

Hi everyone — first post, hoping for some advice.

A loan repayment on our BTC loan platform was bridged USDT→XUSD, but the destination was mistakenly set to the user’s loan contract (0xA48041f9c934456c6182275756d007291df2943F) instead of the user’s wallet (our bug). 611.76 XUSD is now stuck there. I’ve verified against the deployed bytecode that the contract has no function that can move its XUSD balance, and it can’t be upgraded — the funds are safe, but unreachable. The user’s Zero trove is still open, so their BTC collateral is stuck too.

The one fix I can see is a supply-neutral relocation by the Mynt mAsset owner: burn the 611.76 XUSD from the contract, mint the same amount to the user’s wallet — no supply change, no treasury cost, and the user can then close their loan normally.

Is that something the Mynt operators could do as an operational fix (like the manual FastBTC processing in the past), or should I draft a SIP?

Happy to share all tx refs and verification steps. Any help appreciated — thanks in advance.

2

Hi @charlesb27 , are you still stuck? If so, please reach out to the CMs on our discord and they’ll point you in the right direction. I’m also pinging @TJCloak to see this.

3

Hi @yago — yes, still stuck. Thank you for picking this up so quickly, I really appreciate it. I’ll reach out to the CMs on Discord right away. And thanks for looping in @TJCloak — I’m happy to post the full technical details (addresses, balances, verification steps, and the exact transaction sequence) here whenever it’s useful.