Anon Forge (@AnonForgeX) profile picture
Joined December 2023
Part 1 I went through the chain myself to check the questions in @vsuhov posts. I’m just a community member with no access to team records, so everything here is from public data anyone can check. Here’s what I found. First, the thing the posts leave out: 126 of the 199 ETH went right back into the same ETH pool about 4 hours after the pull. etherscan.io/tx/0x104568ee5f… So the ETH that actually left the pool was about 73 ETH, not 199. That’s a big part of the picture to skip. The team’s own announcement listed this re-add at the time (“Re-adding $206k to the eth pair”). More on that below. “Where is the verified BSC-side liquidity addition?” Right here. On Oct 4, 2023 at 15:30 UTC, the team wallet added 2,368 WBNB plus 31.4T tokens to the new PancakeSwap pool: bscscan.com/tx/0xf97feee1313… This is the “Add 505k liquidity into lp pool” transaction from the team’s announcement. Where that WBNB came from: - 1,813.93 WBNB from removing the old BSC pool on Oct 1 bscscan.com/tx/0xcd2c96ba7db… - 569.43 BNB that came in from a Bybit hot wallet at 14:44 UTC on Oct 4 bscscan.com/tx/0xbb6ac92ea68… It got wrapped to WBNB a minute later, right before going into the pool: bscscan.com/tx/0x5e447f8a543… “What happened to the ETH?” The 73.56 ETH went to a Coinbase deposit address at 11:09 UTC on Oct 4: etherscan.io/tx/0x8fbb0eccda… About 3.5 hours later, 569.43 BNB landed in the same team wallet on BSC from Bybit. 73.56 ETH was about $121k back then, and so was 569.43 BNB. That BNB went straight into the new BSC pool. That also matches what the team announced at the time: “122K in value was pulled from the ETH liquidity and added to BSC to balance the two pools.” resources.cryptocompare.com/… To be fair: you can’t see the exchange-to-exchange part on chain. The amounts and timing line up, but that step is an inference. Only the team’s Coinbase and Bybit records could prove it 100%. Also worth saying: sending funds to a centralized exchange isn’t suspicious by itself. Projects have to provide both sides of the pair on CEXs, so exchange transfers can be for market making or contractual obligations. In this case, the value that went in came back out as BNB and went into the BSC pool. “What happened to the withdrawn tokens?” All 34.58T went to the wallet Etherscan labels as the Treasury: etherscan.io/tx/0xf7fcde62cd… That wallet’s balance has never dropped below 34.58T since. It had 159T right after the transfer, its lowest point before the token was retired was 116T, and it holds about 116T today. Check it yourself: etherscan.io/address/0x1CDde… (Tokens are fungible, so nobody can point to “the exact same” tokens. But the balance never went below that amount.) The old BSC tokens from the Oct 1 removal (54.67T) also went to the same treasury, and it still holds 317.5T of the old BSC token: bscscan.com/token/0x88479186… “What were the terms of the ILO liquidity?” Here’s the original ILO announcement from Jan 21, 2023: teapaw.org/shibtoshi/status/16167… Read it. The terms were about contribution bonuses: a 5% bonus for contributing to the ILO through the Dapp, and 3% for swapping BSC tokens to ETH. Contributors got their tokens plus the bonus at launch. There’s nothing in it about locking the liquidity forever, keeping it in one pool, or how it would be managed afterwards. Think about how an initial offering normally works. A team sells tokens to the community, and the money it raises is the project’s to use however it sees fit. In this case, 100% of what was raised went into the liquidity pair. The ILO raised 540 ETH, and all 540 ETH went into the Uniswap pair along with 43.1T tokens on June 2, 2023. The LP was locked in UNCX the next day: etherscan.io/tx/0x74f6faa236…
Replying to @AnonForgeX @grok
We've examined the BSC side, including the original 2022 contract, audit, liquidity pools, and tax mechanisms. We also understand the difference between the 2022 BSC launch and the 2023 Ethereum expansion. Our investigation includes actual blockchain transactions, contract analysis, and historical project announcements. Where records remain incomplete, we've openly acknowledged that. Using AI to assist with forensic analysis doesn't invalidate blockchain evidence. The transactions are publicly verifiable. If you believe something is incorrect, point to the specific claim and provide the transaction hash or supporting evidence. I'll gladly review it and correct anything that's wrong. I'm interested in facts, not a competition over who uses better tools. 😃
2
3
3
8
1,277
Part 2 The team held that LP and the tokens it minted, and nothing in the ILO terms said otherwise, so rebalancing the pair was its call to make. What matters is whether liquidity was siphoned off or sent somewhere it shouldn’t go. Nothing on chain shows that. What left the ETH pool lines up with what went into the BSC pool. If someone thinks otherwise, the burden is on them to show the transaction. So what was the point of all this? After the rebalance, both the ETH and BSC pools had the same 31.4T tokens and about the same $505k of liquidity, so both chains traded at the same price. That’s what the announcement says too: liquidity was adjusted “to be equal on both ETH and BSC.” The ETH pool lost more tokens than ETH, which pushed the price up about 70%. To be clear, that came from reshaping the pool, not from buying. And it wasn’t hidden. The team’s “Migration Conclusion” post went out on X and Telegram on Oct 5, 2023. It listed the pull (199 ETH, $328k), the re-add ($206k back into the ETH pair) and the BSC add ($505k), with links: Saved copy of the announcement: resources.cryptocompare.com/… Bottom line: from what’s public, the rebalance adds up on chain and matches what the team announced at the time. 100% of the ILO raise (540 ETH) went into the liquidity pair, and the ILO terms were about contribution bonuses, not restrictions on the liquidity. There’s no on-chain evidence of liquidity being siphoned off. The one step the chain can’t show is Coinbase to Bybit, and the amounts and timing match there. Asking questions is fine, but the full picture should include the 126 ETH that went back in. You should probably manually check the on-chain records before posting about it on X. You just look like you didn’t do all the research, and if you did, you left some key details out to favor your story.
1
1
4
188