Key takeaways
- SunPump is TRON's pump.fun analog, launched by SUN.io in August 2024: ~20 TRX to create a token, a 1% trade fee on the bonding curve, and automatic graduation to SunSwap V2 with the LP burned.
- The boom was violent and brief. 94,000 tokens were created in 2024 by TRON DAO's own count, and 92% of all the fees SunPump had collected by mid-2026 came in that year. By then daily fees had decayed to a few hundred TRX.
- Every launch manufactures fresh wallets and high-velocity flows — deployer pre-buys, sniper fan-out from shared funders, burst activations. These are synthetic patterns, and an origin tracer who reads them as organic history will misattribute.
- The launchpad and its routers are scenery. The finding is always the EOA that funded the burst.
In August 2024 TRON got its own version of the machine that had been printing memecoins on Solana all year. SunPump, built by the SUN.io team behind SunSwap, let anyone mint and list a token for about 20 TRX, no code and no seed liquidity required. Within two weeks it was processing a quarter of a million trades a day.
For an origin tracer this matters less as market history and more as a pattern generator. A single memecoin launch spawns dozens to hundreds of wallets in minutes — the deployer, the snipers, the farming bots, the exit-liquidity buyers — most of them freshly activated and funded from a small set of sources. That is a fan-out signature, and it looks a lot like the deliberate funding structures TRONORIGIN is built to find.
The difference between a memecoin frenzy and a laundering operation is intent, and intent is not visible in the graph. What is visible is the mechanism. This article covers the mechanism.
Live three days before the announcement
The on-chain record and the press record disagree by three days, and the on-chain record wins. SUN.io’s launch announcement is dated August 12, 2024 (Singapore time). The LaunchpadProxy contract at TTfvyrAz86hbZk5iDpKD78pqLGgi8C7AAw was deployed on August 9, 2024, and the platform’s own fee feed shows revenue trickling in from August 10. SunPump ran quietly for a weekend before anyone announced it.
The contract itself is worth a minute of attention. TronScan tags it SUN: LaunchPadProxy under the SUN.io blue tag, and it is a proxy — the implementation behind it (currently TKYQmYdssV2UVjr7UmNNt4jti1mmm7ZWnX) can be swapped, and its exposed admin methods include setMintAndMinTxFee, setPurchaseFee, setSaleFee, and setVault. Fees and the fee-collection vault are operator-settable, which is a control fact: “fair launch” describes the token distribution, and the platform above it remains a centrally administered contract. By mid-2026 that one proxy had processed roughly 3.5 million transactions.
The bonding-curve machine
Creating a token costs about 20 TRX and one transaction: symbol, name, description, logo, done. There is no presale and no team allocation; every buyer, including the creator, purchases from a bonding curve — a contract that mints price algorithmically, charging more TRX per token as more of the supply is sold. SunPump takes a 1% fee on every curve trade, and sellers can dump back into the curve at any time.
One option deserves an investigator’s attention: at creation, the developer can pre-purchase a slice of their own token inside the same transaction. SUN.io’s docs frame this as front-running protection against bots — which is also an admission that launch-sniping bots are a routine part of the ecosystem. Either way, the effect on-chain is that the deployer frequently holds a meaningful bag from block one, bought with the same TRX that paid the creation fee.
| Parameter | Value | Source |
|---|---|---|
| Token creation fee | ~20 TRX | SUN.io docs (service fees) |
| Trading fee on the curve | 1% per trade | SUN.io docs (service fees) |
| Curve completion (“100%”) | ~$69,420 market cap | SUN.io docs (how it works) |
| Liquidity moved at graduation | SUN.io docs (service fees / how it works) | |
| Liquidity-addition fee | ~3,000 TRX deducted from the curve | SUN.io docs (service fees) |
| LP tokens after graduation | Burned | SUN.io launch announcement |
The numbers echo pump.fun deliberately, down to the $69,420 joke threshold. The fee parameters are “approximately” in SUN.io’s own documentation because, as the proxy’s admin methods show, they are settable.
Graduation to SunSwap
A token that pushes its market cap to roughly $69,420 completes the curve. At that point the launchpad contract acts on its own: it deposits about 100,000 TRX plus the remaining 200 million tokens into a new SunSwap V2 pair, deducts the ~3,000 TRX liquidity fee, and burns the LP tokens. The token stops trading on the curve and becomes an ordinary TRC-20 trading on SunSwap V2 — the same constant-product venue covered in the DEX field guide.
The LP burn is the load-bearing design choice. Because nobody holds the pool’s LP tokens, nobody can pull the pool. That closes off the classic liquidity-rug on graduated tokens — and it redirects extraction rather than eliminating it. More on that below.
SUNDOG, the flagship graduate, shows the pipeline working end to end: a fixed one-billion-token TRC-20 issued on August 15, 2024 — six days into the platform’s life — that graduated, listed, and by mid-2026 had accumulated over 500,000 holder addresses.
The surge, measured in fees
SunPump’s own fee feed — the same endpoint DefiLlama’s adapter reads — gives the boom its exact shape. Revenue began on August 10, 2024 with pocket change. Eleven days later, on August 21, the platform collected 3,656,176 TRX in fees (about $589,000) across 250,097 fee-paying trades in a single day. That was the all-time peak, eleven days in.
TRON DAO’s 2024 year-end review counts 94,000 tokens created on SunPump that year. The fee ledger says the same thing from another angle: of the 38.87 million TRX SunPump had collected by mid-2026, 35.9 million — 92% — was collected in 2024. The platform’s fee history since then is a long decay curve. On July 2, 2026, it recorded 405 TRX in fees across 32 trades: a rounding error against the peak. The DeFi summer pattern repeated itself at meme speed — an incentive-driven activity spike, a slow bleed, and a permanent residue of on-chain history.
| Moment | Figure |
|---|---|
| First fee revenue | August 10, 2024 |
| Peak day (Aug 21, 2024) | 3.66M TRX in fees / 250,097 trades / ~$589,240 |
| 2024 total | 35.9M TRX in fees; 94,000 tokens created |
| Cumulative through mid-2026 | 38.87M TRX (~$6.4M) across ~3.17M fee-paying trades |
| July 2, 2026 | 405 TRX in fees across 32 trades |
That residue is the part that outlives the trend. Tens of thousands of dead tokens, and the wallets that traded them, are permanently written into TRON’s transaction history — and they will keep surfacing in wallet investigations for years.
What a launch does to the wallet graph
A hot SunPump launch compresses months of ordinary wallet-graph growth into minutes, and everything it produces is synthetic.
The deployer cluster. The creator funds a wallet with TRX, pays the creation fee, and often pre-buys in the same transaction. Serial deployers — and at 20 TRX per token, 94,000 tokens implies many — reuse funding sources across launches. One EOA fanning TRX out to a series of short-lived deployer wallets is a textbook fan-out structure, identical in shape to deliberate wallet-farm funding.
The sniper fan. Bots watch the launchpad and buy within seconds of creation. A sniping operation runs many wallets to disguise its position size, and all of them trace back to a shared treasury through one or two hops. On TRON the activation of every one of those wallets is credited to an external account that signed for it — activation always names an external signer, never a contract — so the activation record itself names a funder.
The burst. Around a launch that catches attention, dozens of wallets activate and transact within a narrow window, then most go quiet forever once the token dies. High transaction velocity, uniform trade sizing, and machine-fast reaction times are the same signals used to separate bots from humans, and around a memecoin launch they fire constantly.
For an origin tracer the danger runs in both directions. Read a sniper fan as organic and you’ll miss a coordinated operation; read a memecoin gambler’s burst as sinister and you’ll manufacture a false positive. The launch context is the disambiguator: fresh activations that cluster around a LaunchpadProxy interaction, in the minutes after a token creation, are the memecoin economy doing what it does. The SunPump contracts, like the SunSwap routers, are infrastructure: a launchpad no more “originates” a wallet than a DEX router does, so for any analyst neither can ever be a wallet’s true origin — they are pass-through venues, not funders. The origin question is unchanged: which EOA activated and funded the wallet before it touched the curve?
Where the rug actually happens
SunPump’s burned LP forecloses the crudest exit. What remains are extraction paths that all leave the same trace shape: value concentrating back out of the many wallets into a few.
Pre-graduation, the curve itself is the exit. A creator or coordinated cluster pre-buys cheap, promotes the token, and sells into later buyers’ demand on the curve — the TRX flows out of the bonding contract to the sellers, and the token never graduates. Post-graduation, a deployer bag bought at curve prices gets dumped into the fresh SunSwap pool. Either way, the money moves from a crowd of small fresh wallets, through the launch contract or the pool, into a handful of wallets that then consolidate — often toward an exchange deposit address within a hop or two. That consolidation leg is ordinary flow-tracing work: the extraction wallets are short-lived by design, and the durable fact about them is who funded them and where the proceeds landed.
The pattern to internalize is symmetry. A launch fans TRX out from few wallets to many; an extraction fans value back in from many wallets to few. When both signatures appear around the same token within days, funded from overlapping sources, that is one operation wearing two shapes.
SunPump made wallet-mass production a 20-TRX consumer product, and 2024 wrote the result into the chain at a scale TRON had not seen before. The investigator’s discipline is unchanged by the noise: the launchpad is infrastructure, the burst is context, and the origin is the EOA holding the funding hose. Find the hose.
Sources
- SUN.io Support — Announcement on the Launch of SunPump on SUN.io (Aug 12, 2024) — primary; launch date, fair-launch framing, and the “deposited into SunSwap V2 and burned” graduation rule.
- SUN.io Docs — SunPump Service Fees — primary; ~20 TRX creation fee, 1% trading fee, ~100,000 TRX + 200M tokens moved at graduation, ~3,000 TRX liquidity-addition fee.
- SUN.io Docs — SunPump: How Does It Work? — primary; ~$69,420 curve-completion threshold and the ~$12,000 TRX liquidity deposit/burn.
- SUN.io Docs — SunPump: How to Launch — primary; same-transaction developer pre-purchase and its anti-bot rationale.
- SUN.io Docs — SunPump Contract Reference — primary; canonical LaunchpadProxy, PumpSwapRouter, and PumpSmartExchangeRouter addresses.
- TronScan contract API — LaunchpadProxy
TTfvyrAz86hbZk5iDpKD78pqLGgi8C7AAw— primary on-chain attestation; August 9, 2024 deployment, proxy structure, admin fee methods, ~3.5M transactions (as of July 2026). - SunPump fee-data API (openapi.sunpump.meme) — primary, the platform’s own fee feed; per-day TRX fees and trade counts, including the Aug 21, 2024 peak and the 2024-vs-all-time split (pulled July 2026).
- DefiLlama — SunPump fees adapter (GitHub) — primary methodology; shows DefiLlama’s figures are read from SunPump’s own fee endpoint.
- DefiLlama — SunPump protocol data (API) — primary data provider; USD conversions ($589,240 peak day, ~$6.4M all-time as of July 2026).
- TRON DAO Medium — 2024 TRON Network Review (Jan 15, 2025) — primary, TRON DAO’s own year-end review; the 94,000-tokens-created figure for 2024.
- TronScan TRC-20 API — SUNDOG
TXL6rJbvmjD46zeN1JssfgxvSo99qC8MRT— primary on-chain attestation; 1-billion fixed supply, August 15, 2024 issuance, holder count (as of July 2026). - TRONORIGIN attribution methodology (proprietary) — the project’s own analysis approach; excluding launchpad/router infrastructure from origin attribution, and the fan-out, burst-activation, and consolidation pattern definitions.