[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 UselessChris UselessChris posts on X about $wco, $wtk, bsc, xdc the most. They currently have XXXXX followers and XX posts still getting attention that total XXX engagements in the last XX hours. ### Engagements: XXX [#](/creator/twitter::53157951/interactions)  - X Week XXXXX -XX% - X Month XXXXXX -XX% - X Months XXXXXX -XX% - X Year XXXXXXX +101% ### Mentions: XX [#](/creator/twitter::53157951/posts_active)  ### Followers: XXXXX [#](/creator/twitter::53157951/followers)  - X Week XXXXX +0.03% - X Month XXXXX +0.80% - X Months XXXXX -XXXX% - X Year XXXXX -XXXX% ### CreatorRank: XXXXXXXXX [#](/creator/twitter::53157951/influencer_rank)  ### Social Influence [#](/creator/twitter::53157951/influence) --- **Social category influence** [cryptocurrencies](/list/cryptocurrencies) XXXX% [exchanges](/list/exchanges) XXXX% **Social topic influence** [$wco](/topic/$wco) 13.7%, [$wtk](/topic/$wtk) 12.33%, [bsc](/topic/bsc) 4.11%, [xdc](/topic/xdc) 4.11%, [bitrue](/topic/bitrue) 2.74%, [token](/topic/token) 2.74%, [holders](/topic/holders) 2.74%, [files](/topic/files) 2.74%, [new tokens](/topic/new-tokens) 1.37%, [1b](/topic/1b) XXXX% **Top accounts mentioned or mentioned by** [@wadzpay](/creator/undefined) [@venomousinsect](/creator/undefined) [@xendpayments](/creator/undefined) [@reviewerc](/creator/undefined) [@fixedfloat](/creator/undefined) [@buckydunn](/creator/undefined) [@blockcdx](/creator/undefined) [@yieldrone](/creator/undefined) [@launchverseeth](/creator/undefined) [@jewelstecheth](/creator/undefined) [@devoerc](/creator/undefined) [@kittenfitech](/creator/undefined) [@beoblechat](/creator/undefined) [@globiance](/creator/undefined) [@thedavey92](/creator/undefined) [@acropoliserc](/creator/undefined) [@investfierc](/creator/undefined) [@irnerc20](/creator/undefined) [@sensorgpuerc](/creator/undefined) [@xenoncoin](/creator/undefined) **Top assets mentioned** [WadzPay Token (WTK)](/topic/$wtk) [XDC Network (XDC)](/topic/$xdc) [Ethereum (ETH)](/topic/ethereum) [Tether (USDT)](/topic/$usdt) ### Top Social Posts [#](/creator/twitter::53157951/posts) --- Top posts by engagements in the last XX hours "6/ As mentioned by the team most of the stolen $WTK was probably sold after being sent to Bitrue within the first few days after being bridged from Polygon. Not all however and much like with the old bridge contracts the hacker received a $WCO airdrop to XX wallets"  [@aUselessChris](/creator/x/aUselessChris) on [X](/post/tweet/1945776970060485010) 2025-07-17 09:25:55 UTC 3275 followers, XXX engagements "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"  [@aUselessChris](/creator/x/aUselessChris) on [X](/post/tweet/1948634049133556113) 2025-07-25 06:38:55 UTC 3274 followers, XX engagements "Started looking into some things regarding @globiance so anyone who got their $XDC or other assets stuck on there feel free to join the pit (link in my bio). Do note that this does not mean the $WTK / $WCO saga is done only that I've freed up some time on the on-chain side"  [@aUselessChris](/creator/x/aUselessChris) on [X](/post/tweet/1945219645142663310) 2025-07-15 20:31:18 UTC 3275 followers, 4201 engagements "1/ Bit of a longer break than I expected but as we now return to the @WadzPay historical journey we've reached the launch of $WCO. Today we'll do a narrow thread covering the airdrop of $WCO to the $WTK holders"  [@aUselessChris](/creator/x/aUselessChris) on [X](/post/tweet/1945776955711746129) 2025-07-17 09:25:51 UTC 3274 followers, XXX engagements "3/ As the drama following the bridge hack unfolded the $WCO team claimed they would blacklist the hacker wallets in order to recover stolen supply. According to the official statement released in 2025 375m $WCO / $WTK was recovered"  [@aUselessChris](/creator/x/aUselessChris) on [X](/post/tweet/1945776960522621080) 2025-07-17 09:25:52 UTC 3274 followers, XXX engagements "15/ 1.17b $WTK sold Possible. Let's just take the $WCO teams word on this"  [@aUselessChris](/creator/x/aUselessChris) on [X](/post/tweet/1937591889735172193) 2025-06-24 19:21:19 UTC 3274 followers, XXX engagements "4/ The $WCO token deployed on Ethereum BSC and XDC did indeed have a blacklisting function as well as the capability of burning blacklisted supply. Both of these functions were also called by the WCO owner wallet once on each chain before the contracts were renounced"  [@aUselessChris](/creator/x/aUselessChris) on [X](/post/tweet/1945776963689340941) 2025-07-17 09:25:53 UTC 3273 followers, XXX engagements "9/ As mentioned most of this $WCO never moved. No attempts to deposit to an exchange no attempt to migrate. The exception being X hacker wallets sending a combined 518239 $WCO to a fresh Bitrue deposit on BSC. This deposit is labeled WTK hacker Bitrue XX in The FUnD Files"  [@aUselessChris](/creator/x/aUselessChris) on [X](/post/tweet/1945776978428387505) 2025-07-17 09:25:57 UTC 3273 followers, XXX engagements "1/ As some $WCO supporters believe my claim that the $WTK LP provided by the team consisted of stolen supply only let's do a bit of a tutorial on how you can easily verify this information on your own. All you need is a few minutes of time polygonscan bscscan and etherscan"  [@aUselessChris](/creator/x/aUselessChris) on [X](/post/tweet/1942290577237635220) 2025-07-07 18:32:14 UTC 3273 followers, 2582 engagements "A few questions to add: - Did the team really never notice that all supply used by the team to create and increase the $WTK LP on Uniswap were stolen tokens bridged from Polygon - If the LP wallet with the stolen tokens were in control of the unnamed 3rd party contractor and they avoided you when contacted how did you get them to send the $USDT from the removed LP to a $WCO team wallet - If the team didn't notice the hack until late 2024 why did the team use the main supply wallet to burn tokens from the Polygon bridge hack in March 2023 - As the team spent X months using "advanced tools" to"  [@aUselessChris](/creator/x/aUselessChris) on [X](/post/tweet/1937873567183421550) 2025-06-25 14:00:37 UTC 3274 followers, 2863 engagements "2/ For this one we'll just need page X of The FUnD Files historical document which only contain a pretty simple spreadsheet detailing the hacker wallets airdropped"  [@aUselessChris](/creator/x/aUselessChris) on [X](/post/tweet/1945776958173839554) 2025-07-17 09:25:52 UTC 3274 followers, XXX engagements "5/ These blacklist and burn transactions did not target the hacker however. All supply blacklisted was airdropped $WCO that got stuck in the old $WTK bridge contracts. And no - the hacker had no way of accessing this as the bridge only allowed transfers of $WTK"  [@aUselessChris](/creator/x/aUselessChris) on [X](/post/tweet/1945776967027950058) 2025-07-17 09:25:54 UTC 3275 followers, XXX engagements "1/ Was requested to provide an update on $SYNTX yesterday. Obviously the timeline here did not play out as I expected and it saw some big price action after my warning. Was even more surprised to see them listed on MEXC but now it appears that may have been the end game here"  [@aUselessChris](/creator/x/aUselessChris) on [X](/post/tweet/1774391474584420760) 2024-03-31 11:01:08 UTC 3274 followers, 2740 engagements
[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 UselessChris
UselessChris posts on X about $wco, $wtk, bsc, xdc the most. They currently have XXXXX followers and XX posts still getting attention that total XXX engagements in the last XX hours.
Engagements: XXX #
- X Week XXXXX -XX%
- X Month XXXXXX -XX%
- X Months XXXXXX -XX%
- X Year XXXXXXX +101%
Mentions: XX #
Followers: XXXXX #
- X Week XXXXX +0.03%
- X Month XXXXX +0.80%
- X Months XXXXX -XXXX%
- X Year XXXXX -XXXX%
CreatorRank: XXXXXXXXX #
Social Influence #
Social category influence cryptocurrencies XXXX% exchanges XXXX%
Social topic influence $wco 13.7%, $wtk 12.33%, bsc 4.11%, xdc 4.11%, bitrue 2.74%, token 2.74%, holders 2.74%, files 2.74%, new tokens 1.37%, 1b XXXX%
Top accounts mentioned or mentioned by @wadzpay @venomousinsect @xendpayments @reviewerc @fixedfloat @buckydunn @blockcdx @yieldrone @launchverseeth @jewelstecheth @devoerc @kittenfitech @beoblechat @globiance @thedavey92 @acropoliserc @investfierc @irnerc20 @sensorgpuerc @xenoncoin
Top assets mentioned WadzPay Token (WTK) XDC Network (XDC) Ethereum (ETH) Tether (USDT)
Top Social Posts #
Top posts by engagements in the last XX hours
"6/ As mentioned by the team most of the stolen $WTK was probably sold after being sent to Bitrue within the first few days after being bridged from Polygon. Not all however and much like with the old bridge contracts the hacker received a $WCO airdrop to XX wallets"
@aUselessChris on X 2025-07-17 09:25:55 UTC 3275 followers, XXX engagements
"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" @aUselessChris on X 2025-07-25 06:38:55 UTC 3274 followers, XX engagements
"Started looking into some things regarding @globiance so anyone who got their $XDC or other assets stuck on there feel free to join the pit (link in my bio). Do note that this does not mean the $WTK / $WCO saga is done only that I've freed up some time on the on-chain side" @aUselessChris on X 2025-07-15 20:31:18 UTC 3275 followers, 4201 engagements
"1/ Bit of a longer break than I expected but as we now return to the @WadzPay historical journey we've reached the launch of $WCO. Today we'll do a narrow thread covering the airdrop of $WCO to the $WTK holders" @aUselessChris on X 2025-07-17 09:25:51 UTC 3274 followers, XXX engagements
"3/ As the drama following the bridge hack unfolded the $WCO team claimed they would blacklist the hacker wallets in order to recover stolen supply. According to the official statement released in 2025 375m $WCO / $WTK was recovered" @aUselessChris on X 2025-07-17 09:25:52 UTC 3274 followers, XXX engagements
"15/ 1.17b $WTK sold Possible. Let's just take the $WCO teams word on this" @aUselessChris on X 2025-06-24 19:21:19 UTC 3274 followers, XXX engagements
"4/ The $WCO token deployed on Ethereum BSC and XDC did indeed have a blacklisting function as well as the capability of burning blacklisted supply. Both of these functions were also called by the WCO owner wallet once on each chain before the contracts were renounced" @aUselessChris on X 2025-07-17 09:25:53 UTC 3273 followers, XXX engagements
"9/ As mentioned most of this $WCO never moved. No attempts to deposit to an exchange no attempt to migrate. The exception being X hacker wallets sending a combined 518239 $WCO to a fresh Bitrue deposit on BSC. This deposit is labeled WTK hacker Bitrue XX in The FUnD Files" @aUselessChris on X 2025-07-17 09:25:57 UTC 3273 followers, XXX engagements
"1/ As some $WCO supporters believe my claim that the $WTK LP provided by the team consisted of stolen supply only let's do a bit of a tutorial on how you can easily verify this information on your own. All you need is a few minutes of time polygonscan bscscan and etherscan" @aUselessChris on X 2025-07-07 18:32:14 UTC 3273 followers, 2582 engagements
"A few questions to add: - Did the team really never notice that all supply used by the team to create and increase the $WTK LP on Uniswap were stolen tokens bridged from Polygon - If the LP wallet with the stolen tokens were in control of the unnamed 3rd party contractor and they avoided you when contacted how did you get them to send the $USDT from the removed LP to a $WCO team wallet - If the team didn't notice the hack until late 2024 why did the team use the main supply wallet to burn tokens from the Polygon bridge hack in March 2023 - As the team spent X months using "advanced tools" to" @aUselessChris on X 2025-06-25 14:00:37 UTC 3274 followers, 2863 engagements
"2/ For this one we'll just need page X of The FUnD Files historical document which only contain a pretty simple spreadsheet detailing the hacker wallets airdropped" @aUselessChris on X 2025-07-17 09:25:52 UTC 3274 followers, XXX engagements
"5/ These blacklist and burn transactions did not target the hacker however. All supply blacklisted was airdropped $WCO that got stuck in the old $WTK bridge contracts. And no - the hacker had no way of accessing this as the bridge only allowed transfers of $WTK" @aUselessChris on X 2025-07-17 09:25:54 UTC 3275 followers, XXX engagements
"1/ Was requested to provide an update on $SYNTX yesterday. Obviously the timeline here did not play out as I expected and it saw some big price action after my warning. Was even more surprised to see them listed on MEXC but now it appears that may have been the end game here" @aUselessChris on X 2024-03-31 11:01:08 UTC 3274 followers, 2740 engagements