CryptoTwitter(CT) is overrun with degens that are harvesting your engagement and turning it into cult followings and large sums of money.  They talk about life-changing money.  It probably is.  But you’re still kinda a dirtbag for siphoning money from your followers and everyone else.

I loved influencing him.  I did my normal thing, hopped on CT throughout the day, looked at the news, boring stuff.  Check the Pepe insider’s wallet and sure enough, more ERC-20 tokens being bought before being announced.

I hopped on this wallet: 0x46ac53a531c2D915e4D5E3c0d6805c8DdEa773dE and grabbed the Smart contract ID, did the normal buy from Uniswap.  Oh shit, it worked.  Tried again.  Tried again with a different, similarly named crapcoin, it worked.  Now I have 30ish tokens for one and a few billion crapcoin of the other.  The one that’s only ever going to have 11,000 tokens, if it had any utility, should be worth billions during a short squeeze.  Looking around at other things in the wallet, I check the token list.  The new coin that I just bought has been “spent”.

The 30ish I just bought are gone.  Wtf?

Ohh, this has happened to me before.  When I found the new coin, grabbed the smart contract ID and made the buy, I “accepted” the tokens configuration on chain.  This included all the associated smart contracts and one of them includes a function that does not allow me to “spend” those tokens, like you would need to dump them with Uniswap.  It also included a function that allowed them, some wallet they control, to use my already signed Metamask cert to transact with the chain programmatically.  That could be done from anywhere.  The transaction hits the blockchain all the same.  It’s a loophole for Uniswap’s V2 smart contract, so that they, Uniswap, can “spend” on your wallet’s behalf, while completing your real order.  It’s so Uniswap doesn’t have to prompt you at each step of the transaction.  Sign the cert, give them a timeframe that’s good to use it, usually short, then use it to transact.  But I couldn’t remember if I had seen how long this signed cert action was good for on this new token smart contract.  Hmm, the other coins were still there.

Shit, so they were waiting to find my new address transacting for both tokens, which can probably only be intentional.  If the same wallet held both tokens, they knew it was me, and they could kick off their next scripts.  And shit shit, if they knew my wallet address, and they got my cert, this wallet could be owned by them, maybe forever, they could try and gain access, or use the cert to spend or sign an Arb transaction on Arbitrum and get the liquidity back.  Time to exit the wallet.  I sent out the last remaining transactions and waited a few seconds.  I shit you not, my MetaMask wallet extension started firing thousands of notifications.  They were DDOSing my wallet so it couldn’t transact again until they were ready, they finally caught up.  I’m out.  Disabled and removed the extension.  Because I didn’t have the recovery key to the wallet, this was the event that locked the real PSYOP tokens (Orig Smart Contract address: 0xfdC83eb69d20eD562Ca45B5Ca48f3b1aFe378a1E) on Arbitrum chain forever.

I checked recently added tokens and I saw that LAMA and HARAM BSC (Binance Smart Chain-another Ethereum clone) tokens were launched.  Just going to keep tryin’ huh guys.

I created a CT burn account and messaged ben.eth around May 16, 2023.  Can’t remember exactly.  I named it ‘HATE-HATEv3-LAMA-HARAM---RUGPULL’, and tweeted the smart contract address and that they were scams.  I then DM’d ben.eth from the same account and sent him the message: “I love that you called the new coin HATE and I’m the one laughing.  What’s cooler than a million dollars?  A billion, buahahahahahaha”.  Deactivated the account, hopefully before the automation built an ad profile and stored it, but even if it did, there’s nothing of value there, just another burner duck.com address.

Anything I posted to r/Loopring after the initial post was being deleted, this happened at least a couple times.  Because the first entry was a few days old, it was probably 100% indexed and backed up and would be noticed because it had already been talked about amongst mods.

Mole on the mod team.  They’re scared.  I’m getting close.

Here’s one that was removed about LRC fees, because it’s negative and they can tell it’s “me”: (

I get it now. RE: #2

They don't want you to be able to adjust the claim fee, because then you'd know that you're paying 30 times the value of the token to claim it. If you could, they couldn't charge you a "minimum on-chain transaction gas fee", which is bullshit. It costs no more to transfer Pepe than any other coin, it's smoke and mirrors.

).

I knew I had to message the mods of r/Superstonk.  If a mole got it, it would do the viral sharing work for me-good and bad.  I don’t need to see it to know what’s happening, CT is so predictable.

I crafted the next mod message with a brief breakdown of tracking the Pepe insider and 9-10 of the new burner wallet addresses they were transferring 100ETH each to.  I made it seem like they were on my tail and I was soooooo worried.  I loaded up telegram, changed my username, then left the username in the mod message and sent the entire message over a series of 5 messages.  I stayed logged into Telegram for a few hours, no messages.  Set the account to auto delete and remove Telegram from my device.

Literally hitting them from all sides now.  Twitter, Reddit, their wallets, their moles, everyone was fired up and moving the machine along.

It’s going to be a lot harder to get rid of it in the logs when there’s 5 entries in the table instead of just one.  With just one, there’s a single point of failure, the message could be deleted before others get to see it or it gets replicated (like for a large distributed DocumentDB), indexed or backed up.  There’s 4 less notifications per message, 4x10ish mods maybe, 40ish less chances someone sees it, too many.  I need this to get the authorities involved before they launch.  Shotgun blast, not a snipe for this one.

Went back to Twitter and because I had used an account that had already passed whatever ridiculous check that was in place for new accounts, I was still using the same browser session that crafted the cookie where the flag was checked, so I used it to my advantage.  I could browse freely to ben.eth’s page.  Still launching, jfc.  Okie dokie