Sign in Subscribe
6 min read

Research Notes: RALPH On-Chain Activity

Screenshot showing boostlegends-volumebot wallet label on Solscan

Hey Geoff. I've been researching how open source developers are experimenting with funding models — token launches, creator fees, community tokens as alternatives to grants and VC. Your approach with $RALPH caught my attention because you were pretty transparent about it: 'fees are pumping in', 'derisked', research funding without needing sketchy grant contracts. That's an interesting thesis.

I'll be upfront: I haven't messed much with crypto. I'm genuinely curious about this space, and I'm just trying to surface anything that might be helpful for you. You're a good guy, and I think you deserve to see what's visible on-chain before someone less charitable puts it together.

Full disclosure: I still hold a small bag of $RALPH. I subscribed to your Ghost blog. I've been genuinely enjoying exploring Loom and the Ralph technique — my 13-year-old son has been watching me dig through all this on-chain data and is fascinated by the research process. So I'm coming at this as someone who's engaged with your work, not someone looking for a takedown.

As part of that research I dug into the on-chain mechanics. I found some things that I think you should know about — partly because others will find them too (@spacexbt already has), and partly because if you're going to make the case that token launches are a legitimate OSS funding model, the on-chain story needs to be clean. This isn't for publication. It's a starting point for a conversation.

What I Can Verify

These are facts I've confirmed on-chain. None of this is speculation.

The Fee Claiming Pattern

A wallet (5f2Qj9e14pfZ5DyKbfVQD6MduEdEsh1Mk1wyUa8XFGmu) called claim_creator_trading_fee on the RALPH/SOL Meteora pool 6,483 times in 19 days. That's once every four minutes, around the clock, without a single gap. This is automated — no human is clicking "claim" every 240 seconds for three weeks.

The Two-Wallet Structure

The fee wallet sweeps SOL to a main holding wallet (2mvtNnTP2CBRz24q1BzmDX9cv2bQBsY8E77D32qkYKCm). That wallet holds 19.61M RALPH — nearly the entire 20M vesting allocation from Streamflow — plus 134 SOL from accumulated fee sweeps.

167 transfers between the two wallets. The pattern is clear: fees accumulate, SOL gets swept to the main wallet.

The Fee Structure

The RALPH token was launched on Bags.fm, which uses Meteora's Dynamic Bonding Curve. The creator fee is 99% — meaning for every dollar of trading volume, roughly one cent goes to Bags.fm and 99 cents goes to the creator. This is a Bags.fm default, not something unusual. But it means the incentive to generate volume is enormous.

Independent Confirmation

@spacexbt independently identified both wallets and the fee claiming pattern (639K views on their thread). They reported fee claims every 20 seconds at peak, and estimated $250K in RALPH sales. I haven't verified the sales figure independently, but their wallet identification matches mine exactly.

What I Confirmed

I initially observed a 'boostlegends-volumebot' label on Solscan. I've since confirmed the wallet address, its identity, and its behavior through on-chain data.

The Boost Legends Connection

The wallet is 811txS7TBMK8PH7RiY2WjFd44nthWpMWyK2Rt9zYC4E9, registered as the .sol domain boostlegends-volumebot.sol via Solana Name Service. I recovered this address by matching partial transaction signatures from my original screenshot against on-chain data via Solana RPC.

This wallet executed 30,000+ transactions in a few hours, each sending 1 lamport to 19 different wallets simultaneously. It's an industrial-scale dust advertising bot — Boost Legends' 'calling card.' It has zero token accounts and never did any DEX trading itself. The actual volume trading uses their 9,000-wallet cloud farm (separate, unidentifiable wallets).

The critical finding: the dusting was targeted at RALPH holders. Among wallets that appeared in multiple dust batches, 71% have RALPH token accounts. This isn't random spam — someone ran a Boost Legends campaign specifically targeting the RALPH community.

What Boost Legends Is

Boost Legends is a real, commercially-operated Solana volume bot service (boostlegends.com). They use a 9,000-wallet cloud farm to generate artificial trading volume on DEXes including Meteora — the exact protocol where RALPH earns its 99% creator fees. They claim to generate $55,000-$60,000 in headline volume per SOL deposited, operated via Telegram bot.

The dust advertising bot targets RALPH holders specifically, but the actual volume trading (if purchased) would be done by separate, anonymous wallets in their farm. The connection chain: Boost Legends' dust bot targeted RALPH holders → Boost Legends' trading service routes through Meteora → RALPH's 99% creator fee extracts SOL from every Meteora trade. If someone bought this service for RALPH, it would directly generate fees for your claiming wallet.

What This Doesn't Prove

The targeted dust confirms someone ran a Boost Legends campaign aimed at RALPH holders. But it doesn't prove who purchased it:

  1. Purchased by you to inflate volume and fees
  2. Purchased by a community member trying to help the token pump
  3. Run by Boost Legends as an unsolicited marketing demo
  4. An unknown third party bought it to manipulate the token for their own benefit

I genuinely don't know which of these is true.

The Questions This Raises

Whether or not a volume bot was involved, the on-chain data raises questions that others will ask:

  1. The fee claiming frequency (every 3-4 minutes, 24/7) — what automated this, and why claim so aggressively rather than letting fees accumulate?
  2. Was all the trading volume that generated these fees organic? The market cap went from near-zero to $43M — was that genuine demand or was some of it manufactured?
  3. Your Jan 17 tweet ("fees are pumping in, circa 200k") and Jan 22 tweet ("derisked", confirming sales) create a timeline that looks like: generate fees, accumulate, sell. Is that what happened, or is there more context?
  4. If someone was running a volume bot on your token without your knowledge, wouldn't you want to know? And if you did know — wouldn't addressing it head-on be better than leaving it for others to find?
  5. You've stated publicly that you didn't deploy the smart contract and have no control over it. But the fee claiming wallet is clearly yours — automated, running 24/7, sweeping to your main wallet. If you don't control the token, who set up and authorized the fee extraction infrastructure?

The Charitable Reading

I want to be explicit about what's possible here, because I think people will jump to conclusions. And your own website (ghuntley.com/solana/) states clearly: 'Geoffrey Huntley did not deploy the smart contract and has no control over it.' That matters.

  • Automated claiming doesn't mean fake volume. You could have scripted legitimate fee claims — it's just efficient treasury management.
  • The 99% creator fee is a Bags.fm default. You didn't set some unusual fee to extract value — it's what every token on that platform gets.
  • You didn't deploy the token or control the supply. BagsApp created the smart contract. Their model is explicitly 'create a coin for someone else and direct the royalties to them.' You accepted the arrangement, but you didn't architect the tokenomics.
  • The volume may have been entirely organic during the ATH period. $RALPH had genuine community enthusiasm. $43M market cap could have generated substantial organic fees.
  • A community member may have run a volume bot to help the token without telling you. This happens. Token holders run bots on tokens they're invested in.
  • Selling tokens is not inherently wrong. You said you were funding research without grant contracts. That's a legitimate use case for token proceeds.

Why I'm Sharing This

I'm not trying to accuse you of anything. I'm sharing this because:

  • @spacexbt already found the wallets publicly. Their thread has 639K views. The pattern is visible to anyone who looks.
  • Others will dig deeper. The volume bot connection is one search away from anyone who pulls the full transaction history.
  • If something happened you didn't authorize — someone running a bot on your token, for instance — you should know before it becomes a narrative you can't control.
  • The sell timing (before the next vesting unlock) already has bad optics. If wash trading allegations get layered on top, it compounds significantly.

What I'd Suggest

Take this however you want. But if I were in your position:

  1. If you know about the volume bot situation, address it directly. Transparency beats discovery.
  2. If you don't know, investigate. Check your transaction history. Find out if someone ran a bot on your token.
  3. Consider explaining the automated fee claiming publicly. "I wrote a script to claim fees every few minutes" is a reasonable answer — and it's better than silence.
  4. Get ahead of the narrative. Right now it's one tweet thread. It won't stay that way if the volume bot connection surfaces independently.

Appendix: Evidence

Wallets

  • Fee wallet: 5f2Qj9e14pfZ5DyKbfVQD6MduEdEsh1Mk1wyUa8XFGmu
  • Main wallet: 2mvtNnTP2CBRz24q1BzmDX9cv2bQBsY8E77D32qkYKCm
  • RALPH token: CxWPdDBqxVo3fnTMRTvNuSrd4gkp78udSrFvkVDBAGS

Tweets

  • @spacexbt thread (both wallets, 639K views): x.com
  • Geoff "circa 200k" (Jan 17): x.com
  • Geoff "derisked" (Jan 22): x.com

Numbers

  • 6,483 fee claims in 19 days
  • 167 SOL transfers between fee wallet and main wallet
  • 19.61M RALPH in main wallet (of 20M total vesting)
  • 134 SOL accumulated from fee sweeps
  • $348K peak fee value (estimated at time of observation)
  • 99% creator fee (Bags.fm/Meteora default)

I'm not publishing this. I just want you to see what the data shows before someone else frames it for you. Let me know if you want to talk about it.

Published by:

Chris