WOJAK OG Community
Migration Analysis Report
February 11, 2026
All data sourced from on-chain records, Etherscan, DexTools, and public announcements
TL;DR
A group operating as @wojakcto is running a hostile “migration” from the original WOJAK contract to a new token they control. Every migration is a sell order on the OG token — this is likely why market cap dropped from ~$29M to ~$2M. Both contracts are now renounced, but they are NOT the same: the new contract (0x8D) was deployed with blacklist, setRule, and trading control functions that were active before ownership was renounced — any settings or blacklisted wallets from that period are now permanently locked in. The OG contract (0x50) is a clean OpenZeppelin ERC-20 that never had ANY admin functions — no blacklist was ever possible, no trading controls ever existed. OG LP is locked until 2100. 14,000+ holders have not migrated. Do your own research and verify everything on-chain before taking any action.
What Is Happening
A group operating under @wojakcto on X is running a “migration” from the original WOJAK contract (0x50) to a new token (0x8d). They claim the OG token is dead and everyone must migrate within a 2-week window via migrate.wojakcto.com at a 1:958 swap ratio. This report breaks down why the OG community should be cautious, backed by on-chain facts.
The Two Contracts — Side by Side
| Metric | OG WOJAK (0x50) | New wojak (0x8d) |
|---|---|---|
| Token Name | Wojak Coin (WOJAK) | wojak (wojak) — lowercase |
| Supply | 69,420,000,000 | 420,690,000,000,000 (6,057x more) |
| Holders | ~19,000+ | ~5,580 |
| Market Cap | ~$2.04M | ~$14.76M |
| Liquidity | $932K (100% locked) | $513K (100%) |
| LP Lock | Until year 2100 (~75 yrs) | Unknown |
| Contract | RENOUNCED — clean ERC-20, zero admin functions | RENOUNCED — deployed with blacklist + setRule, now locked |
| Volatility | 0.3066 | 0.7371 (2.4x higher) |
| Pool Created | April 17, 2023 | Recent |
| Total TXs | 100K+ | ~45K |
| Code | Clean OpenZeppelin ERC-20 | blacklist + setRule (owner renounced, functions locked) |
Contract Design Concerns (0x8D)
Ownership of the new contract has been renounced (owner = 0x0). However, the contract was originally deployed with the following owner-controlled functions. While these can no longer be called, their presence reveals the contract's design philosophy:
- 1.
blacklist(address, bool)This function allowed the owner to freeze any wallet. Now that ownership is renounced, no NEW wallets can be blacklisted. However, any wallets that WERE blacklisted before renouncing remain permanently frozen — there is no way to remove them.
- 2.
setRule(bool, address, uint256, uint256)This function allowed the owner to set trading limits, max/min holding amounts, and control trading conditions. These settings are now locked in whatever state they were in when ownership was renounced.
- 3.
_beforeTokenTransfer overrideEvery transfer still checks the blacklist and trading rules. These checks are hardcoded and permanent — they cannot be removed even with ownership renounced.
- 4.
Ownership renounced to 0x0Ownership has been renounced to
0x0. The onlyOwner functions (blacklist, setRule) can no longer be called by anyone.
The OG contract (0x50) was deployed as a clean ERC-20 with ZERO admin functions from day one. No blacklist was ever possible. No trading controls were ever possible. The contract was designed to be trustless from the start — not made trustless after the fact.
How the Migration Works — And Why It Hurts OG Holders
The portal describes: “Send, receive, swap, buy, and burn done automatically.” Based on this, the most likely sequence:
- 1
Your OG 0x50 tokens are SOLD on Uniswap for ETH — direct sell pressure on OG.
- 2
ETH is used to BUY new 0x8d tokens — buy pressure on new token.
- 3
New 0x8d tokens sent to your wallet. Some portion may be burned.
EVERY MIGRATION IS A SELL ORDER ON THE OG TOKEN. This is likely why OG market cap dropped from ~$29M to ~$2M. Whoever controls the new token's LP catches the buy pressure. Every migration enriches 0x8d LP holders at OG holders' expense.
The migration portal does NOT disclose the migration contract address. Without it, nobody can verify what happens to your tokens. This alone is a massive red flag.
What They Have Done to the OG Token
Etherscan: Submitted CTO update request, got OG logo/branding changed or removed.
DEX Screener / DexTools: Spam/warning banner added to OG token's page, misleading migration notices.
CoinMarketCap: Listed new 0x8d contract under WOJAK name with their branding.
CEXs: MEXC (Feb 3) and BitMart (Feb 2) announced contract swaps, calling 0x50 "former."
X/Twitter: migrate.wojakcto.com flagged by Twitter safety as "potentially spammy or unsafe."
The Numbers Don't Add Up
14,000+ holders have NOT migrated (19,000+ OG vs ~5,580 new).
OG has $932K liquidity vs new's $513K — nearly 2x more.
OG has 100K+ transactions. Battle-tested for 2+ years.
New token volatility is 2.4x higher (0.7371 vs 0.3066) — more speculative.
Supply ballooned from 69.42B to 420.69T — 6,057x dilution.
What the OG Contract Has Going For It
Clean from Day One
LP locked until 2100
Zero taxes
19,000+ holders
~$1M liquidity
Clean ERC-20 code
100K+ transactions
@WojakToken on X
What You Should Do
We are not saying the new token is a scam. We are saying the OG token is fundamentally cleaner by design, and the migration creates unnecessary sell pressure on OG holders. Make informed decisions.
DO NOT connect your wallet to migrate.wojakcto.com
DO NOT approve any unknown contracts to spend your WOJAK tokens
Already approved? Revoke immediately at etherscan.io/tokenapprovalchecker
Continue to hold OG WOJAK (0x5026F006B85729a8b14553FAE6af249aD16c9aaB)
Report @wojakcto for misleading content
Contact CoinGecko, Etherscan, CMC to dispute CTO claims and restore OG branding
Spread this information to the community
Contract Addresses for Reference
| OG WOJAK | 0x5026F006B85729a8b14553FAE6af249aD16c9aaB |
| New wojak | 0x8De39B057CC6522230AB19C0205080a8663331Ef |
| OG Uniswap Pool | 0x0f23...496e (created April 17, 2023) |
| OG Website | wojak.io |
| OG X/Twitter | @WojakToken |
| CTO Website | wojakcto.com |
| CTO X/Twitter | @wojakcto |
DYOR. Verify everything on-chain. The blockchain doesn't lie.