Deep Dive
1. No Significant Commits Since 2021
Overview: OMG Network’s primary GitHub repository (elixir-omg) shows no meaningful code updates since March 2021, with the latest commit focused on minor Docker configurations.
The repository, which hosts core components like the Watcher and Plasma contracts, has not seen substantive changes in over four years. Developer activity metrics (commits, pull requests) are negligible, and the project’s documentation still references a “public testnet coming soon” despite no recent progress.
What this means: This is bearish for OMG because stagnant development erodes confidence in its Layer-2 scaling claims. Without updates, the network risks falling behind competitors like Optimism or zkSync. (GitHub)
2. KuCoin Delisting (November 2025)
Overview: KuCoin announced OMG’s delisting on 19 November 2025, citing “cessation of on-chain activities” and failure to meet platform standards for developer engagement.
The exchange highlighted inactive block generation and lack of protocol upgrades as key factors. Users were advised to withdraw tokens by 19 December 2025.
What this means: This is neutral-to-bearish for OMG because delistings reduce liquidity and visibility. However, it reflects broader market consensus about the project’s dormancy. (KuCoin)
3. Ghost Chain Label (August 2025)
Overview: Cointelegraph classified OMG as a “ghost chain” in August 2025, noting its GitHub had no meaningful commits, low transaction volume (~100 daily), and broken ecosystem links.
The report emphasized that even corporate-backed projects like OMG can fail without sustained development. Binance had previously delisted OMG in June 2024 for similar reasons.
What this means: This is bearish for OMG because the label deters new investors and developers, creating a negative feedback loop. (Cointelegraph)
Conclusion
OMG Network’s codebase has been inactive since 2021, with exchanges and analysts flagging its dormancy as a critical risk. While its Plasma-based scaling vision once held promise, the absence of updates and developer momentum suggests the project is functionally abandoned. How might renewed institutional interest or a community fork alter this trajectory?