Bubblemaps Alleges Cupsey Tied to $1.7M Wallet Operation

What did Bubblemaps allege?

Bubblemaps has alleged that crypto influencer Cupsey made $1.7 million through a side-wallet operation involving 30 connected wallets. According to the analytics firm, those wallets traded more than 27,000 tokens since May 7. The figure is an allegation, not a court finding: the account names no chain, token, transaction hashes, or year for the May 7 start date.

How did the trading sequence allegedly work?

Four wallets bought a token and distributed it to 12 side wallets, Bubblemaps said. Cupsey then bought through his public wallet, copy traders followed, and the side wallets began selling afterward. Bubblemaps presents this sequence as coordinated trading, although the account gives no token name, prices, execution times, or evidence that all 30 wallets joined every step.

Simple division puts the headline $1.7 million at about $56,700 per connected wallet, but that is only a scale comparison. Bubblemaps does not provide a per-wallet profit table, and the linked wallets may have had materially different balances and outcomes. In plain terms, the headline is not an average wallet result.

What does the 3z4vj link add?

Bubblemaps also linked Cupsey on-chain to 3z4vj, which it described as a 'serial token deployer.' The firm said 3z4vj launched and rugged thousands of tokens and made about $1.3 million. That separate figure equals roughly 76% of the $1.7 million headline, but the account does not say whether the amounts overlap, reflect gross or net proceeds, or reached Cupsey.

The relationship expands the alleged exposure beyond a single wallet sequence. It does not by itself prove common control of every linked address or explain the transaction that established the link. The account also names no court, prosecutor, regulator, exchange, or token issuer acting on the findings, so the two dollar figures should not be added without transaction-level reconciliation.

Can 30 addresses establish common control?

The cluster supports a sequencing claim, but attribution to one owner requires more evidence than on-chain adjacency alone. The report calls the addresses side wallets and says 12 received the token; it does not say how many Cupsey controls, whether other parties own them, or explain how the addresses became connected.

Copy traders bought after the public purchase, but the account does not say whether they were independent or coordinated. It provides no trader count or profit data, and it does not identify the reasons the linked wallets sold. In plain terms, transaction sequence does not prove common ownership or profit.

The absence of a named token and chain prevents readers from reproducing or contextualizing the trading results. The account quantifies no harm to traders and gives no reason for the side wallets' sales. In plain terms, the map shows timing more clearly than control.

Is there evidence of enforcement or legal wrongdoing?

No enforcement action is described. The account names no court, prosecutor, civil regulator, law-enforcement agency, exchange sanction, or legal finding that Cupsey violated a specific law. The label 'rugged' reflects Bubblemaps' characterization of thousands of 3z4vj launches, not a judicial determination.

Reputationally, the allegation creates a specific problem for Cupsey: his purchase through the public wallet precedes copy-trader entries and later side-wallet selling. Operationally, traders exposed to that sequence would need to distinguish a public signal from a trade coordinated through undisclosed related wallets.

The source does not quantify losses, identify affected traders, or report any response from Cupsey. It therefore does not show that followers lost money. In plain terms, this is a due-diligence warning, not a legal verdict.

What can be verified next?

Three disclosures would make the claims independently testable. Until Bubblemaps or another party supplies them, outside analysts cannot reproduce the wallet graph or recalculate either dollar figure from the available account.

These disclosures would include:

• The addresses and transaction hashes for the 30-wallet cluster.
• The criteria used to label wallets as connected and attribute them to Cupsey.
• The transaction-level calculation behind the $1.7 million and $1.3 million figures.

The May 7 date lacks a year, and the account gives no exact end date. That omission limits any precise comparison of the 27,000-token count with a defined reporting window. No deadline for a response or enforcement window appears in the findings.

Until those gaps are filled, the defensible conclusion is narrow: Bubblemaps has mapped an alleged $1.7 million wallet operation and a separate $1.3 million deployer record. The available account leaves the profit flow unverified.

In plain terms, independent transaction data remains the decisive test. With no enforcement window disclosed, the next concrete checkpoint is whether analysts can reproduce the wallet links and calculations from underlying transactions.