Have you ever scrolled through a crypto investigation and wondered whether the people mapping those wallet clusters might have skin in the game? I certainly have. A few days ago an accusation landed that forced exactly that question into the open: Bubblemaps, the platform many traders rely on to spot coordinated activity, was alleged to have quietly taken $45,000 a month from Proxima while still publishing public analytics. The company immediately called the document a forgery. What followed mixed French corporate filings, an address that appeared two months too early, a competitor’s pre-suit notice, and a string of skeptical investigators. The whole episode feels less like a clean scandal and more like a stress test for how much trust we place in on-chain detectives.
How the Alleged Agreement First Surfaced
The story began with an account named JuJudog that described itself as a former Bubblemaps employee. On social media it posted what it claimed was a signed consulting agreement dated 11 April 2025 between Bubblemaps and Proxima. According to the post, Proxima would pay a flat $45,000 every month plus $1,800 per hour for extra work. The supposed scope covered private reviews of wallet-clustering parameters, transaction-bundle detection methods, and techniques for linking trading accounts. In plain language, the analytics firm that helps outsiders see coordinated buying would have been helping one client see those same patterns first.
JuJudog said the arrangement created an obvious conflict of interest and that the discovery prompted an exit from the company. The post spread quickly among traders who already treat Bubblemaps maps as a kind of weather report for new tokens. Within hours a competing analytics project, Trap Map, amplified the claims and announced it had privately served Bubblemaps and its CEO Nicolas Vaiman with formal pre-lawsuit notice. The notice demanded a response by 16 November and invited anyone who believed they had lost money on undetected bundles to register potential claims.
What a pitiful attempt at forgery.
Bubblemaps answered the next day with a pointed public reply. The company listed three concrete problems: the email address attributed to its CEO was not one he has ever used, the registered office on the document was the address the firm only adopted months later, and the team is small enough that every past employee is known by name. They also noted that the account pushing the document appeared to be promoting a rival bubble-map tool. In short, they treated the contract as fabricated rather than merely unwelcome.
The Address Timeline That Undercuts the Document
French business registries are public and surprisingly precise. At the time the alleged contract was supposedly signed, Bubblemaps was still registered at 7 Rue Pablo Neruda in Levallois-Perret. The company only changed its official address to 9 Rue des Colonnes in Paris on 20 June 2025—more than two months after the date on the document. The forged paper, if that is what it is, used the later address for an earlier period. That single mismatch is hard to explain as a simple clerical error; someone who had genuine access to an April contract would have known the correct registered office.
Readers quickly added a Community Note to the original post that highlighted the same discrepancy. In my experience, corporate-registry timestamps are among the least romantic but most reliable pieces of evidence in these disputes. You cannot backdate a French filing the way you can edit a PDF. The fact that the document got the address wrong in the direction of “future knowledge” is the detail that keeps bothering people who have watched similar leaks before.
- 11 April 2025: alleged contract date
- 20 June 2025: actual address change recorded in French filings
- Early November 2026: document circulated with the later address
Bubblemaps also rejected the employment claim. A company of that size does not forget a developer who worked on clustering logic. One of their own analysts, Deebs, replied publicly and mocked the technical language in the supposed agreement—“LIQUIDITY DISTRIBUTION TELEMETRY”—as something no one on the team would have written. The tone was dismissive, almost amused, which is itself a signal. When a small team treats an accusation as amateur rather than threatening, it usually means they believe the source is outside the building.
Trap Map’s Legal Notice and What It Actually Means
Trap Map’s public statement used formal language: “formal pre-suit notice of a class action.” It named both the company and the CEO and set a 14-day deadline. Yet a pre-suit notice is not a lawsuit. No court docket has been cited, and Bubblemaps has not confirmed it even received the private version of the notice. In many jurisdictions a demand letter is cheap to send and expensive to ignore only if the underlying facts hold up. Here the underlying facts are precisely what Bubblemaps disputes.
The competitor also compared the two platforms’ handling of a token called GATO, claiming its own maps revealed developer concentration and linked wallets that Bubblemaps had missed. Those side-by-side screenshots were never independently audited against the same data set, so they function more as marketing than as evidence. Still, the episode shows how quickly an allegation can be weaponized by a rival product. Analytics tools live or die on perceived neutrality; the mere suggestion of a paid relationship is enough to make some traders hesitate.
| Claim | Bubblemaps Response | Public Record Check |
| April 2025 consulting contract | Forgery, wrong email and address | Address change recorded June 2025 |
| Former employee author | No such person on small team | Unverified identity |
| Conflict of interest | No commercial relationship with Proxima | No independent confirmation |
Why Wallet Clustering Tools Matter So Much
To understand why this fight feels personal to many traders, it helps to remember what Bubblemaps actually does. The platform visualizes clusters of wallets that appear to move in concert—same funding sources, similar timing, overlapping token holdings. When a new meme coin launches, a dense cluster around the deployer wallet is often the first red flag. Traders have come to treat those maps the way equity traders treat short-interest reports: imperfect, sometimes lagging, but better than pure guesswork.
If a firm providing those maps were simultaneously consulting for a company that sells trading tools or promotes tokens, the incentive problem is obvious. The consultant might soften certain parameters, delay a public map, or simply share insights privately before they hit the timeline. That is the classic information-asymmetry problem. Perhaps the most interesting aspect of the present dispute is that Bubblemaps has itself published investigations into coordinated activity, including an October report on a Pump.fun influencer accused of benefiting from linked wallets. The company is not shy about naming patterns. That track record makes the sudden forgery claim more plausible to some observers and more disappointing to others.
We would never hire a dev this stupid.
– Bubblemaps analyst responding to the technical language in the document
Other investigators entered the conversation quickly. One account, dethective, claimed the same JuJudog handle had previously run a similar “leaked contract” promotion for an unrelated token. The earlier campaign allegedly involved misleading material and trading activity; the identity and any profits remain unconfirmed. Whether or not that history is accurate, the pattern is familiar in crypto: an anonymous account appears, drops a dramatic document, and funnels attention toward a competing product. Reputation systems on social platforms are still weak, so the same tactic can be reused with only a username change.
How Communities Try to Verify These Claims
In the absence of a court filing or a leaked internal email that survives scrutiny, traders fall back on the same methods they use for tokens. They check timestamps, cross-reference public records, and watch who amplifies the story. The address mismatch is the strongest single piece of evidence so far. The email mismatch is harder for outsiders to verify but easy for anyone who has corresponded with the CEO. The employment claim is the weakest; a small team can simply say “we know everyone who worked here.”
I’ve found that the most reliable early signal is often the quality of the technical language. When a supposed internal document uses awkward or invented terminology, people who actually work in the field notice. Deebs’s public mockery of “liquidity distribution telemetry” is an example. Real clustering work talks about funding graphs, temporal correlation, and common-input-ownership heuristics. It does not invent marketing-sounding phrases. That linguistic tell is not courtroom proof, but it is the kind of detail that makes experienced analysts lean toward skepticism.
- Compare document date against official registry changes
- Check whether named email addresses are known to be used
- Look for independent corroboration beyond the original poster
- Watch whether a competing product is the main beneficiary of attention
None of these steps prove innocence or guilt. They simply raise the cost of a successful forgery. In a market where a single viral post can move token prices or destroy a tool’s reputation overnight, that cost still looks too low to many participants.
Broader Risks for Crypto Analytics Platforms
Even if the present contract is fabricated, the episode highlights a structural tension. Analytics firms sit between retail traders who want free or cheap maps and professional clients who will pay for private insight. The moment a firm takes money from one side while serving the other, trust erodes. Some platforms try to solve this by publishing clear commercial relationships or by refusing paid consulting altogether. Others stay silent until an accusation appears. Silence is cheaper until it is not.
French corporate transparency actually helped Bubblemaps here. Many crypto companies are incorporated in jurisdictions with slower or less public registries. Had the address change been harder to verify, the document might have survived longer. That is an argument, perhaps, for more analytics firms to keep their legal entities in places where filings are both timely and searchable. It is also a reminder that on-chain data is only half the story; off-chain corporate records still matter when money and reputation are involved.
Looking ahead, the 16 November deadline set by Trap Map will be the next concrete date. If no lawsuit materializes, or if any filing rests on the same disputed document, the forgery narrative gains strength. If new evidence appears—an email chain, a payment record, a second witness—the picture changes. Until then, most observers are left with a document that fails basic consistency checks and a company that has every incentive to deny it.
For traders the practical takeaway is simpler and older than any of these tools: treat every map as a hypothesis, not a verdict. Cross-check with raw block explorers, watch funding flows yourself, and remember that the people drawing the bubbles are also running businesses. The Bubblemaps–Proxima dispute may turn out to be nothing more than a clumsy attempt to damage a competitor. Or it may be the first public crack in a relationship that was never disclosed. Either way, the speed with which the address mismatch was spotted shows that at least some corners of the community still know how to read a filing. That skill remains useful long after any single contract has been forgotten.
In the end the episode is less about one alleged $45,000 monthly fee and more about the fragile social contract that lets anonymous accounts, public registries, and commercial analytics tools coexist. When that contract frays, the maps we rely on become just another narrative. The current evidence points toward a forgery, but the market will keep watching the next filing, the next reply, and the next token cluster all the same.
