Bridge issue: 253 WGNK minted to BridgeContract instead of intended wallet #2192

Open @AkSwiss573 opened 2026-10-31 05:07 UTC 0 comments Updated 2026-10-31 05:07 UTC
bug

Problem

I accidentally received 253 WGNK at the BridgeContract address instead of my intended Ethereum wallet address during a GNK-to-WGNK bridge operation.

Transaction details

  • Transaction hash: "0xffcf0eec7058b01597ccf0ffb0d513ec1915fca04216d092e2a6779c437458ee"
  • Amount: 253 WGNK
  • Incorrect recipient (BridgeContract): "0x972a7A92D92796a98801A8818bcF91f1648f2F68"
  • Intended recipient (my wallet): "0xd0A76F94f432Ec4Fba3B701127bB0D47EEf00254"

Actual result

The transaction logs show that 253 WGNK were minted directly to the BridgeContract address.

Expected result

The 253 WGNK should have been minted to my intended Ethereum wallet address.

Request

Could the Gonka bridge developers please investigate whether the original transaction can be corrected or the 253 WGNK recovered through an authorized contract-level intervention?

Please escalate this issue to the developers responsible for the bridge smart contract.

I am not requesting a duplicate mint. I am requesting assistance with the original transaction.

Thank you.

🔄 Auto-synced from Issue #2192 every hour.