1/ While I'm not yet fully back from my extended break, I felt this day needed a little bonus thread. The past 2 chapters have been quite lenient on @TheGlitchFather and even absolved him of some conspiracies. The truth is what matters, not flinging accusations for the sake of it
2/ So while $ARC has been the dominant theme lately, we're heading back to $GLCH now. There are still some huge fans around that has labelled me a liar, and they might find this one interesting as it's easy to follow and do not require much research or critical thinking.
3/ One of the most prominent fans had a post on telegram the other day that I found funny. I had almost forgotten about @GlitchProtocol's ambition of being blockchain agnostic and bridge friendly.
4/ While $GLCH was launched on @ethereum, it's bridgeable to both @0xPolygon and @BinanceChain. The bridge to $BSC was launched by the team themselves and has an interesting setup.
5/ From my perspective, a person not in any way an expert on bridges, it seems like $GLCH is running somewhat of a manual bridge, or maybe more likely through a botted wallet. The tokens sent to #BSC from the #ERC side rests in a regular wallet, not a smart contract.
6/ Likewise on the #BSC side. There is a smart contract minting and burning the $GLCH tokens going back and forth across the chains, but those transactions are triggered from an ordinary wallet.
7/ This led me to believe that the bridge setup was running from the home of one or several $GLCH team members. Could I prove that when we first discussed this internally? No, it just seemed likely.
8/ And it's easy to see why people fall in love with $GLCH. It's at a very low market cap at the moment, and an L1 blockchain with only 90.5 million supply must be bound to have huge upside, right?
9/ At this moment some of you readers are probably thinking something along the lines of "Hang on stupid, $GLCH can never exceed 88,888,888 coins."
Or can it?
10/ Truth to be told, it already did. Thanks to an alert member of #TheFUDpit it came to our attention there have been some shenanigans going on over at the bridge. The token contract on #BSC doesn't have a mint limit, meaning anyone having control of the trigger wallet can mint.
11/ The google sheet below contain all transactions on the $ETH - $BNB bridge. The "Quantity" column shows the number of tokens received. The "FROM ERC" column shows the number of tokens that were actually sent from the $ETH side.
12/ The sheet is sorted on highest differential, meaning if the far right column is above 0, the wallet received this many more tokens than it bridged.
You think this is fake? Check the wallet number on both @bscscan and @etherscan to confirm yourself.
13/ It could appear like our work to expose these people have made them nervous. They know we watch their usual routes and deposits, and there's no more money coming in from $GPOOL launches. Best case scenario this is a core team member gone rogue, either way $GLCH is compromised
14/ This started in a small scale back in November, but the pace have drastically increased for the past 10 days. So I'm sorry to say to all you $GLCH maxis out there. The supply is growing fast, and no matter what your opinion on the team and my work may be - this is undeniable.
• • •
Missing some Tweet in this thread? You can try to
force a refresh
1/ It's still less than a day since the first information on the mint exploit on @GlitchProtocol's #BSC bridge was published. And boy, has it been an eventful time since then. You know that hell is about to freeze over when yours truly is allowed to enter $GLCH tg without a ban
2/ So what do we know so far? @TheGlitchFather made an appearance after a few months of watching from the sidelines and had some interesting things to say. First of all, they have caught one of the bad actors.
3/ So is this true? In my view, yes. The movement of the tokens minted does not suggest it was performed by any of the team members we have followed, this might have taken them by surprise.