ERGO's Dispute with CoinMarketCap Spotlights Data Transparency Risks

Back in November 2023, the Ergo project got into a public fight with CoinMarketCap over something that sounds small until you actually run a project that depends on accurate listing data: circulating supply numbers. Almost two years later, the dispute is still worth revisiting, not because the drama matters anymore, but because the underlying problem (who controls how your token's history gets displayed, and what it costs to fix an error) hasn't gone away for smaller projects.

What actually happened

Ergo is a proof of work blockchain that launched in 2019. Its native token, ERG, had previously existed in a different form as EFYT, a marketing token tied to a separate network with a different supply. When Ergo completed a 1:1 token swap, the team asked CoinMarketCap to correct the circulating supply figure, which was stuck showing a static number that didn't reflect how Ergo's supply actually increases roughly every two minutes as new blocks are mined.

According to Ergo community member Glasgow (@ERG_Glasgow), the team had been trying to get this fixed for over a year: "$5k was the invoice they sent us to fix the circulating supply. A separate issue that has cost us 50 ranks or so over the 2 years we've been trying to get it sorted." CMC's CEO, who goes by Rush on Twitter/X, initially pushed back hard, writing publicly: "Your attempt to erase the historical price data is not acceptable." After the tweet from Ergo's account went semi-viral, CMC reversed course, called the $5,000 invoice a "mistake," and corrected the circulating supply to match Ergo's own API feed, which is what the team had been asking for the whole time.

Ergo's official account framed the aftermath this way, in a follow-up post: "You've now made a statement to other projects who want accurate data on CMC: 'Don't question us, or we will make it worse.'"

Why this is more than a Twitter spat

Here's the part that's easy to miss if you weren't following closely: this wasn't really about erasing history. Ergo never asked CMC to delete the pre-swap price chart. What the team wanted was for the supply figure, the number that feeds directly into market cap calculations, to reflect reality instead of a stale snapshot from before the swap. Market cap is literally price times circulating supply, so if the supply number is wrong, every ranking, every "top 100" list, every automated trading bot pulling from that API is working with bad math.

That's the non-obvious takeaway here: data aggregator disputes aren't really about optics or "chart appearance," even when that's how they get framed publicly. They're about whether the raw inputs other systems depend on are accurate. A $5,000 invoice to fix an input error is a governance problem, not a customer service hiccup.

Where things stand now

As of mid-2026, ERG trades with a circulating supply of roughly 83 million tokens and a market cap in the $19 to $26 million range depending on the day, according to CoinGecko and Bybit pricing pages. The CMC listing itself has stabilized and the supply figure now tracks Ergo's own reporting, so the immediate issue got resolved. What didn't get resolved industry-wide is the structural asymmetry: CoinMarketCap, which is affiliated with Binance, still functions as a gatekeeper that smaller projects have limited recourse against if a data error costs them ranking position.

For context on scale, CoinGecko, the most commonly cited alternative aggregator, currently tracks more than 21,700 cryptocurrencies and explicitly states in its listing methodology that "getting your token or exchange listed on CoinGecko is free and no CoinGecko representative will ever ask you for any form of listing fees." That's a direct, public contrast to the invoice Ergo says it received, and it's part of why projects increasingly treat having a presence on more than one aggregator as basic risk management rather than redundancy.

The practical lesson for anyone running a token or advising a project on this

• Don't assume your listing data is self-correcting. Static supply figures, especially after a swap, merger, or rebrand, can sit wrong for a long time if nobody is actively monitoring them.
• Screenshot and timestamp your correction requests. Ergo's public case only gained traction because the team had a documented, dated trail of support tickets going back over a year.
• Treat data aggregators as a single point of failure in your visibility stack. If your project's legitimacy is being judged partly on a CMC or CoinGecko ranking, you're exposed to decisions made by a private company with no formal appeals process.

None of this makes CoinMarketCap uniquely bad; data aggregation at that scale is a genuinely hard problem, and CMC's API is still used by "some of the largest crypto exchanges and financial institutions in the world," per its own site. But the Ergo case is a useful, concrete example of what happens when a data platform's incentives (engagement, partner relationships, perhaps advertising) aren't perfectly aligned with a listed project's interest in accurate representation. If you're building something that depends on third-party data platforms for legitimacy or discoverability, this is the risk you're carrying, whether or not you've had your own $5,000 invoice yet.