---
name: cryptoguy112-wallet
description: The 12 Sep 2026 hunt for @cryptoguy112 (Profit Maxi, 1,445 followers, Melbourne) and his Robinhood Chain wallet, found by matching his dated $AI posts to on-chain entry price. Read before screening any coin he calls, or before running another caller-to-wallet hunt.
sources: [cowork]
aliases: [cryptoguy112, Profit Maxi, profitmaxi, cryptoguy]
---

# @cryptoguy112 / "Profit Maxi", wallet found 12 Sep 2026

[stated] Ben pasted three screenshots of the account and asked: "find his wallet. make sure to check all coins he mentions plus timestamp."

## THE WALLET
**`0xc1d4b5e64473fd90bf0390a1e0b61876064fd503`** on Robinhood Chain. EOA, EIP-7702 delegated (code 23 bytes), 0 ETH, so gas is sponsored by whatever app he trades through. Its one sale routed through the fomo settlement router `0xb92fe925dc43a0ecde6c8b1a2709c170ec4fff4f`, but **there is no fomo profile at fomo.family/profile/cryptoguy112** ("User not found"), so he is not a fomo poster.

**It is an AI-only wallet.** Full footprint scan (all ERC20 inbound, no address filter): 1,631 distinct tokens ever received, every one of them zero-balance airdrop spam except **AI 7,313,043 tokens = ~$2.3M**. His MOO, GG, YOLO, FRONG and TENDIES positions are NOT here and were never found; they are in another wallet or are much smaller than his posting implies.

## WHAT IDENTIFIED IT, and it was arithmetic, not overlap
- The account: Profit Maxi, @cryptoguy112, 1,445 followers, **created May 2018**, Melbourne, bio "Fartcoin saved my life", 1,891 posts.
- **The load-bearing claim, 12 Sep 12:33 UTC: "I thought I'd make a 10x on $AI but here I am sitting on a 70x from 5m to 350m. I've not sold a single AI."** Plus 11 Aug 12:33: "$AI is my next big bet on RH chain. At just 5m marketcap."
- AI `0x2E8c31162b855A2ffa90F6F8634643Ad6F111e18` (Artificial Inu, NVDA-paired) daily closes put it at **$5.43M cap on 10 Aug** and $7.87M on 11 Aug, so "5m" dates his entry to 10 Aug.
- **Wallet first AI buy 10 Aug 14:31 UTC, 22 hours before the post.** 21 buys, 1 sell, last buy 19 Aug.
- **Weighted average entry $6.37M cap, cost basis $48,304, now $2.28M = 49x on the book and ~65x on the first tranche.** Against AI's $350M top that is his "70x".
- **The decisive table.** Of the 11 wallets that bought 500k+ AI in the $5M window and still hold 70%+, the average entry caps were: **this one $6.37M**, then $20.1M, $23.0M, $29.0M, $41.3M, $52.3M. Every other candidate implies 6x to 16x. **Only one wallet on the chain can honestly say "70x from 5m", and this is it.**
- The blemish: 274,682 AI (3.6% of the position) sold on 13 Aug 15:45, which technically contradicts "not sold a single AI".

## HIS FULL CLAIM LEDGER, harvested with timestamps (twitterapi.io, 166 posts)
Robinhood Chain era, all UTC: **AI** 14 mentions from 11 Aug ("next big bet, 5m"), 20x on 28 Aug, 40x on 1 Sep, 70x on 12 Sep · **MOO** 9 mentions from 30 Aug, "I gave you $MOO at 2.5m" 31 Aug, "keep adding every time it dumps 10%" 3 Sep · **STONK** "filled a decent sized position at 6m" 22 Aug · **YOLO** "favourite coin of the entire PONS ecosystem" 24 Aug · **GG** "bought at 4m" 1 Sep 01:40 · **PAR** "very cheap at 3.5 mil" 5 Sep · **V4** 4 and 7 Sep · **FRONG** "seems cheap at 6.5m" 7 Sep 13:00, "sat through a decent drawdown but rewarded" 10 Sep · **NUDES** 4 Sep · **CASHCAT** "aped" 15 Jul · **TENDIES**, **CATE** Jul-Aug.
Earlier eras worth knowing he has history in: AVA (Apr-May 2025, "6 figures"), REKT, FARTCOIN, COPPERINU (Jan-Feb 2026), PENGUIN, ORGO+ACE, INFQ, UUUU, AMBA, INOD.

## METHOD NOTES, all learned the hard way this session
- **CORRECTION to [[rh-launchpad-sector]]: the Robinhood RPC is NOT limited to ~200k blocks for `eth_getLogs`.** It served logs 32 days / 27M blocks back without trouble. The real limits are (1) a hard **10,000-result cap per query**, which returns `logs matched by query exceeds limit`, and (2) aggressive **HTTP 429 rate limiting**. Both are handled by a recursive range-splitter plus backoff, and that combination replaces Blockscout entirely.
- **Blockscout is now fully Cloudflare-walled** for this chain: `/api/v2/tokens/{ca}/holders` and the v1 `getTokenHolders` both return the "Just a moment..." challenge from the container AND from the droplet. Do not plan a hunt around it.
- Block time measured **0.101822 s = 848,539 blocks/day**, head 61,279,169 at 12 Sep 17:22 UTC.
- **THE BIG TRAP, and it burned four separate attempts: intersecting "who bought coin A and coin B and coin C" on Robinhood Chain returns arbitrage bots, not people.** Every multi-coin intersection was dominated by wallets like `0x2cffed5d56eb6a17662756ca0fdf350e732c9818` (1,010 AI inbound legs, **median leg 2.24 tokens**, 871 of them under 100 tokens, holds a uniform 0.01-0.05% of ten different coins) and `0x636d3380a2742b090670a1a3160f6c30637b3d78` (in legs EXACTLY equal to out legs on all seven coins, every balance zero). **The tells are: in≈out, hundreds of legs, dust-sized median leg, and uniform tiny percentages across unrelated coins.** Filtering by "bought with size" does not remove them because market makers trade size.
- **What DID work: stop intersecting, and price the claim instead.** Take the single most quantitative thing the person said ("70x from 5m"), reconstruct the token's daily price history, compute every candidate's volume-weighted average entry, and keep the one whose arithmetic matches. One number separated the answer from ten near-identical whales when no amount of overlap-hunting could.
- Order that works: harvest the timeline with timestamps → pick the claim with a NUMBER in it → resolve the contract → pull buyers in the window that number implies → filter to EOAs → rank by average entry, not by size.
- Ticker collisions are live on this chain and matter: searching "AI" also returns Actual INU, "GG" returns two Golden Gooses, "STONK" returns a $20k impostor alongside StonkBrokers. Always take the highest-volume pair and sanity-check the market cap against what the caller said.
- twitterapi.io: `from:cryptoguy112` on **Latest returned 81 posts and Top another 85**, 166 unique. Query BOTH and dedupe by tweet id; neither alone is complete even on an eight-year-old account.