URGENT: Transfer stuck 19+ hours - 'transfer not found' error

[longlongcao2-cmd]

URGENT: Transfer stuck 19+ hours - "transfer not found" error

Issue Summary

cBridge transfer from Arbitrum to Polygon has been stuck for 19+ hours. API returns "transfer not found" (error 500) despite successful on-chain transaction.

Transaction Details

• TX Hash (Arbitrum): 0x1c00f8c9c99f7009665c10317ff76ddeccd01f11f1e48ad52e933d2a4049acbc
• Transfer ID: 0x5d0f1081f46df1fb14aa21131af52d159f98bfd80daec9d8768aa70a3fac382c
• Amount: 864 USDC
• Source: Arbitrum (42161)
• Destination: Polygon (137)
• Wallet: 0x0C038E47e82EC77e1FeDBe1038225371907E7F23
• Time Stuck: 19+ hours (initiated 2026-04-21 13:07 HKT)

What Worked

✅ Transaction confirmed SUCCESS on Arbitrum: https://arbiscan.io/tx/0x1c00f8c9c99f7009665c10317ff76ddeccd01f11f1e48ad52e933d2a4049acbc
✅ USDC transferred to cBridge contract (0x1619DE6B6B20eD217a58d00f37B9d47C7663feca)
✅ Contract holds $967.55 USDC (includes our $864)

What Failed

❌ cBridge API returns: {"err": {"code": 500, "msg": "transfer not found"}}
❌ Relay validators never registered the transfer
❌ Funds never arrived on Polygon
❌ No auto-refund after 19+ hours

Expected vs Actual

• Expected completion: 5-20 minutes
• Expected auto-refund: 1-2 hours if failed
• Actual status: 19+ hours stuck, no completion, no refund

Impact

Time-critical operation requiring these funds within 16 hours.

Request

Need immediate manual intervention to either:

1. Trigger relay completion to Polygon, OR
2. Issue refund to Arbitrum, OR
3. Explain system failure

Verification

• Arbiscan: https://arbiscan.io/tx/0x1c00f8c9c99f7009665c10317ff76ddeccd01f11f1e48ad52e933d2a4049acbc
• Polygon wallet: https://polygonscan.com/address/0x0C038E47e82EC77e1FeDBe1038225371907E7F23
• cBridge Explorer: https://cbridge.celer.network/status/0x5d0f1081f46df1fb14aa21131af52d159f98bfd80daec9d8768aa70a3fac382c

Contact: @longlongcao (Telegram)

[Jason7298423]

Hi, thank you for reporting this, and we sincerely apologize for the inconvenience caused.

We’ve already started looking into your case based on the information provided. From our initial review, it seems the transfer may not have gone through the standard cBridge flow, which can occasionally occur depending on how the contract is called or the parameters used. We’ll continue to investigate this on our end.

To help us proceed, we would appreciate it if you could provide a few additional details. Could you please join our Telegram group for quicker communication？

https://t.me/celernetwork

Thank you very much for your patience and understanding.

[Jason7298423]

Hi, thank you for your patience while we completed the investigation.

After a detailed review with our engineering team, we’ve confirmed that this transaction was initiated via a direct contract call rather than through the cBridge frontend.

For this route, USDC is expected to be processed through our Circle CCTP proxy. In this case, the transaction was sent directly to the bridge contract instead, which caused it not to be registered within the standard cBridge flow.

This indicates the issue is related to how the transaction was constructed and submitted, rather than a failure in the cBridge system itself. As such, it falls outside the supported usage scope, and unfortunately, we’re unable to process a refund or recovery for this transfer.

To avoid similar situations in the future, we strongly recommend initiating transfers via the cBridge frontend, which ensures correct routing and parameter handling.

[longlongcao2-cmd]

This response is unacceptable.

The Facts:

1. ✅ Transaction hash: 0x1c00f8c9c99f7009665c10317ff76ddeccd01f11f1e48ad52e933d2a4049acbc
2. ✅ Transaction confirmed SUCCESS on Arbitrum (block 454708162)
3. ✅ 864 USDC successfully transferred to YOUR contract: 0x1619DE6B6B20eD217a58d00f37B9d47C7663feca
4. ✅ Your contract currently holds $967.55 USDC (including my $864)
5. ❌ Funds never arrived on Polygon after 26+ hours
6. ❌ No auto-refund despite your documented 1-2 hour policy

Your Response:

"Transaction was sent directly to bridge contract... falls outside supported usage scope... unable to process refund or recovery"

My Response:

You have my money. I want it back.

Your contract ACCEPTED my transaction. If your contract cannot safely handle direct calls, that is YOUR engineering failure, not mine.

Saying "you should have used our website" is not a valid reason to confiscate $864.

What happens next:

Option 1: You manually relay this transfer or refund to my wallet within 24 hours.

Option 2: I pursue this through:

• Public disclosure (Twitter, Reddit, crypto forums) about cBridge keeping user funds over technicalities
• Legal action (small claims court - I have clear blockchain evidence)
• Reporting to relevant regulatory bodies

The blockchain proves:

• I sent 864 USDC to your contract
• Your contract accepted it
• You control that contract
• You refuse to return it

This is not a "technical limitation" - this is a choice.

I am requesting one final time: Return my 864 USDC.

Wallet: 0x0C038E47e82EC77e1FeDBe1038225371907E7F23
Arbitrum or Polygon - I don't care which.

You have 24 hours before I make this public and pursue legal action.

@Jason7298423

[Jason7298423]

https://arbiscan.io/tx/0x5e3b233afe7dce0c9ae0b19735f358f91529961b52d9b5fe2942de279e6976f6

The refund has already been completed manually.