Diesel’s Ballz token $DIESLBALLZ
Home REPORTS

Named dog. Research only. 7 Sep 2026.

One finding

Wallet BGASPyexYFLvAUEJVGcfvh9bymeCB1Xh34dLTRv5CKyL is long-running Coinbase Prime spray infrastructure. Diesel spoof capital rode that rail — not a named whale who popped up Sep 4.

One conclusion FOCUS BGASPyex First activity 2026-01-30 UTC ~113k signatures Not investment advice

Research only. Re-verify balances and labels. Not financial advice.

One finding — not two topics

This brief is a single research conclusion about one wallet. The so-called “Calvin PDF” is not a side quest. It is independent public language about the same address we traced for Diesel spoof funding.

The thought, compiled

Wallet BGASPyexYFLvAUEJVGcfvh9bymeCB1Xh34dLTRv5CKyL is long-running Coinbase Prime–linked SOL spray infrastructure. Our Solana work shows first activity 2026-01-30, ~113k signatures, repeated ~1 SOL distribution, and downstream peels that funded a Sep 4 CT $DIESLBALLZ spoof. Separately, a public forensic PDF written about another dispute names this exact address and describes it the same way: Coinbase Prime–funded automated bot, tens of thousands of ±1 SOL transfers. Those are not two stories. They are one characterization of one rail — our chain evidence + an independent written description of the same rail — then applied to Diesel brand-spoof risk.

How to read “Calvin” inside this brief

Role of the PDFCorroborating source on BGASPyex behavior (what the address does)
Role of our researchPrimary evidence: age, volume, Coinbase Prime tag, spray pattern, path into Diesel spoof peels
Combined claimDiesel spoof capital rode pre-existing industrial spray rails, not a named KOL/whale who “popped up” Sep 4
Not claimedBGASPyex did not “create CALVIN”; CALVIN and Diesel are not the same team; this is not “CALVIN’s wash trader attacked Diesel”

What is true

An unrelated project published a PDF that names the same Solana address. In that PDF they describe this address as a Coinbase Prime–funded automated bot that sends many ~1 SOL transfers. We cite that sentence only as public description of this wallet’s behavior.

What is not true

Analogy: two reports can discuss the same highway on-ramp without the two destinations being the same trip. BGASPyex is the on-ramp; CALVIN and Diesel spoofs are separate traffic that may use it.

Evidence stack (one wallet)

1. Identity of railSolscan funding tag: Coinbase Prime Hot; balance ~19.35 SOL (7 Sep 2026)
2. Lifetime / patternFirst sig 2026-01-30; ~113,343 txs; dense automated activity; ~1 SOL spray pattern
3. Independent write-up of same addressPublic PDF quote: funded by Coinbase Prime; ~73,600 transfers of ±1 SOL; automated bot (overlap with that PDF’s project argued as statistically meaningless — i.e. shared infrastructure)
4. Diesel relevanceSame rail sits upstream of Sep 4 CT throwaway peels → Fnrx spoof mint (spoof path closed in appendix)
5. Attribution ceilingNo public KOL/country; beneficial owner requires Coinbase process

Independent write-up (address-only citation): public PDF. Used while reading row 3 above. Not a CALVIN–Diesel team claim.

Base wallet findings

All questions below are about this wallet only. The Fnrx spoof / peel / deployer stack is closed scope (appendix).

Q1. Who / what entity? Social? KOL? Hedge fund?

QuestionFinding
Named humanNo public name
KOL / social linkedNo — Birdeye / Arkham / GMGN / web
Named hedge fund / VCNo
What it isAutomated SOL spray / distribution bot funded via Coinbase Prime
Independent PDF on this addressUnrelated project names this same address: ~73,600 ±1 SOL sprays as an automated bot. Behavior citation only — not a CALVIN–Diesel link
Coinbase as project “partner”Not supported — labels = exchange-linked bot rails, not a disclosed fund desk
Working description: long-running Coinbase Prime–tagged automated SOL distribution wallet. No public KOL, social, or hedge-fund identity. Independent PDF names this same address for spray-bot behavior only — not a CALVIN–Diesel team link.

Q2. When was this account created?

MethodSolana has no signup date — first signature = birth
True first activity2026-01-30 00:22:27 UTC (~Jan 29, 6:22 PM CT)
First signature4ozT1XWen58yevuNwhAosM1iDtPZK9xmBCodn62uSZin6BNLsjT2SUbmtNgzku9mxJyx2z9kbEUqvDCuJLJL2LKJ
Lifetime signatures113,343 (RPC history exhausted)
Birdeye age chip7mo (consistent)
Balance (7 Sep 2026)~19.35 SOL

Q3. Public calls?

None found. No X/Telegram linked. Behavior is high-frequency automated SOL sprays, not a calls channel. Birdeye trading PnL/volume show $0.

Q4. Can you research this with the wallet address?

Yes — that is the method. Paste BGASPyexYFLvAUEJVGcfvh9bymeCB1Xh34dLTRv5CKyL into Solscan, Birdeye, Arkham, GMGN, and Solana RPC. Every finding above came from that address.

Q5. Did it pop up on Sep 4?

No. Base wallet alive since late January 2026. Sep 4 CT evening only matters for downstream throwaways (appendix) that were fed from this older rail.

Q6. How to contact the holder?

DM the base58 addressNo — no inbox
Twitter / TG on explorersTried — none
On-chain tip / memoWon’t get a human reply from a spray bot
Beneficial ownerOnly via Coinbase (legal / LE / civil process on the Prime account) — off-chain

Country of origin & attention paths

No public geo/KYC. Coinbase Prime is not proof of a US operator. To figure it out: lawyer + Coinbase legal/compliance; law enforcement; preserve address, first tx, downstream txs, screenshots, and spoof evidence. What will not work: DMing base58, assuming US origin, calling the bot a KOL/HF, or sending a memo for a reply.

Spoof platform reports: report official versus spoof mint, copied branding, timestamps, deployer, and exact transaction IDs. Reports can close the spoof path; they do not identify the Prime customer.

X post drafts

Draft only. Not posted.

01 · Evidence-led
One finding: BGASPyexYFLvAUEJVGcfvh9bymeCB1Xh34dLTRv5CKyL is long-running Coinbase Prime spray infrastructure (first activity 2026-01-30, ~113k sigs). An independent PDF names the same address as an automated ±1 SOL bot. That is corroboration of the rail, not a CALVIN–Diesel team claim. Research only.
02 · Sep 4 clarification
The base wallet did not “pop up” on Sep 4. BGASPyex shows activity from Jan 30, 2026 and roughly 113k signatures. The Sep 4 CT event concerns downstream throwaways / a spoof mint. Different layer, different claim. Research only.
03 · Brand protection
Official mint: 7y853iHqgcqjjSnHem2yMbsc6TBAEsztGTRwEy7Gpump. Report a separate spoof path with exact mint + tx evidence. BGASPyex is a research lead, not proof of a named person or US operator. Keep attribution at the Coinbase Prime / legal-process ceiling.

Base wallet — summary visual

Coinbase Prime–tagged spray hub · first activity Jan 2026 · ~113k sigs · no KOL/fund name · not a Sep 4 pop-up.

Base wallet BGASPyex summary

Base wallet sources

Primary evidence URLs for BGASPyexYFLvAUEJVGcfvh9bymeCB1Xh34dLTRv5CKyL.

ClaimSourceOpen
Address / activity Solana RPC getSignaturesForAddress / getBalance; Solscan account Solscan
First signature RPC history walk, 113,343 sigs, history exhausted first tx
Coinbase Prime funding tag Solscan Funding UI (browser-verified earlier; Cloudflare blocked later re-check) Solscan funding
“Automated bot” / ±1 SOL sprays Unrelated project’s public PDF (3 Mar 2026) that happens to describe this same address as a Coinbase Prime–funded ±1 SOL spray bot. Used only as pattern evidence on BGASPyex. Not evidence that BGASPyex created CALVIN, or that CALVIN connects to Diesel. PDF (address-only citation)
No KOL / entity label Birdeye Wallet Analyzer; Arkham explorer (7 Sep 2026) Birdeye · Arkham

Appendix — spoof path (closed scope; kept for context)

A1. What the earlier analysis answered

Historical framing for the spoof investigation — not the current research focus.

What this analysis answers

A2. Official vs Solana spoof

Official mint 7y853iHq… vs spoof Fnrx2p3a…

Official vs spoof

A3. Solana spoof count

One Solana spoof

A4. Near-launch peel pattern

Sep 4 CT throwaways fed from older rails including this base wallet.

Peel pattern

A5. Pre-launch funding path

Funding path

A6. Funding stack

Funding stack

A7. Hub balances

Hub balances

A8. Interpretation

Interpretation

A9. Attribution ceiling

Attribution ceiling

A10. Conclusions (spoof-path era)

Conclusions