What Mihailo Bjelic’s Polygon exit means for founder-led crypto projects

Mihailo Bjelic’s departure from Polygon in May 2025 mattered because it reduced the network’s visible founding team to Sandeep Nailwal, who remained the sole original founder publicly associated with the project after the exit, according to CoinDesk and Yahoo Finance. The practical significance is not that Polygon stopped operating, but that governance, messaging, and continuity now rely more heavily on a narrower leadership base as the network continues to compete in the Layer 2 market.

What changed on May 24, 2025?

CoinDesk reported on May 24, 2025 that Bjelic announced his departure from the network, while Yahoo Finance described him as one of Polygon’s four co-founders exiting the project. IQ.wiki later summarized the move as Bjelic stepping down from the Polygon Foundation board on May 23, 2025. Taken together, the reporting points to a founder-level transition rather than a protocol shutdown or a formal business sale.

For readers tracking crypto infrastructure, the key detail is the difference between a leadership change and an operational break. Polygon remained Polygon, but the departure removed one of the names most closely tied to its original strategy and public identity.

Why does this matter for users, builders, and treasury teams?

Founder exits can affect how a project communicates roadmap priorities, resolves disputes, and maintains confidence among partners and developers. In practice, that means exchanges, wallets, payment teams, and treasury operators should watch for any changes in governance cadence, ecosystem messaging, or technical direction after a high-profile departure.

This is especially relevant for businesses that settle or move value across chains. When a network’s leadership profile changes, the technical risk may not change immediately, but the decision-making context around upgrades, incentives, and ecosystem support can become less predictable.

What are the limitations and failure modes?

The source material does not show a protocol failure, and it does not prove that Bjelic’s exit caused any specific operational disruption. That is the main limitation: the event is real, but the market consequences are still interpretive. Yahoo Finance also noted Polygon’s token was down 5% in the 24 hours around the report, but short-term price moves are not enough to establish causation. The practical response is to separate governance monitoring from price watching and assign that review to the team that owns chain selection or treasury exposure.

A second caveat is that public reporting differs slightly on the exact framing, with some sources describing a board departure and others describing a broader exit. Operators should treat the confirmed fact as a reduction in Bjelic’s involvement and avoid assuming any unreported internal restructuring.

What should operators do next?

Teams that depend on Polygon should review whether their internal assumptions rely on founder continuity, especially for long-horizon integrations, ecosystem grants, or roadmap confidence. If a business uses multiple chains, this is a good moment to refresh chain-risk checklists and escalation paths rather than react to headlines alone.

For payment and finance teams evaluating whether a network still fits their operational needs, the useful questions are simple: who is accountable for upgrades, how stable is governance, and how quickly can the team adapt if leadership changes again? That is the lens that matters more than the departure itself.

Radom covers this kind of infrastructure change because leadership shifts can influence how crypto rails are assessed in real payment operations. See related analysis of network costs and operating trade-offs.