[GUEST ACCESS MODE: Data is scrambled or limited to provide examples. Make requests using your API key to unlock full data. Check https://lunarcrush.ai/auth for authentication information.]

![aUselessChris Avatar](https://lunarcrush.com/gi/w:24/cr:twitter::53157951.png) UselessChris [@aUselessChris](/creator/twitter/aUselessChris) on x 3273 followers
Created: 2025-07-25 06:38:55 UTC

No lock and mint. The token contracts did support both minting and burning, but this wasn't used for bridging. They simply minted 1b $WTK on each on the official chains and put all of it in the bridge on XDC, and most of the 1b on the BSC bridge. On Polygon, the supposed hacker minted new tokens at will and bridged to the official chains over XX months.

The official explanation from the @wadzpay team is that the Polygon bridge was deployed by a 3rd party contractor but never put into use due to technical problems. They then claim to have discovered that the bridge, maintained by the 3rd party, was still live in 2024 following community concerns.

This doesn't explain why the Uniswap LP, announced by the team, only consisted of stolen supply or the involvement of other team wallets however.

Polygon bridge contract:
0x95525a88a3ef05a19fdDFB4B6b221B9991bB7f5d

Ethereum bridge contract:
0x8074210E3FB7E35a2D3837203729997F2E0eCDA0

BSC bridge contract:
0xBe9075556978c66286d7b0AC426F5Bb28ec486BF

XDC bridge contract:
0xB49369D8Ae1A3Fd8fe8ac1E9Bb94183D7462E0f0


XX engagements

![Engagements Line Chart](https://lunarcrush.com/gi/w:600/p:tweet::1948634049133556113/c:line.svg)

**Related Topics**
[bsc](/topic/bsc)
[xdc](/topic/xdc)
[$wtk](/topic/$wtk)
[token](/topic/token)
[mint](/topic/mint)
[wadzpay token](/topic/wadzpay-token)
[coins](/topic/coins)

[Post Link](https://x.com/aUselessChris/status/1948634049133556113)