Polkadot faces usage decline, bridge fallout and governance disputes

Polkadot’s once‑promising Layer 0 ecosystem is now confronting a mix of technical setbacks and governance friction, according to a former insider and recent reporting [1]. The Hyperbridge bridge exploit and rejected treasury payments have highlighted deeper operational challenges, even as the network readies a major “JAM” upgrade and new developer tools [2].

Key takeaways

• Hyperbridge, labeled by some as Polkadot’s official bridge, suffered an exploit that underscored governance and funding issues [1].
• Polkadot’s treasury allocated nearly $6 million to Snowbridge and later $795,000 DOT to Hyperbridge, but subsequent funding requests were rejected by voters [1].
• The Web3 Foundation has been scaling back direct support, winding down grant programs and official support channels in early 2025 [1].
• Polkadot plans a “JAM” scaling upgrade that aims to increase processing capacity tenfold and introduce a simplified DevContainer for developers [2].
• Governance disputes over retroactive compensation for the Polkassembly platform resulted in a 99 % rejection, reflecting tension between contributors and token holders [1].

Bridge turmoil and treasury strain

Polkadot’s bridge ecosystem has become a flashpoint for criticism. Hyperbridge, which received a seed round of $2.5 million in September 2024 led by the Web3 Foundation (W3F) and VC firm Scytale, was later elevated to “native bridge” status with a 795,000 DOT liquidity allocation worth about $3.8 million at the time [1]. However, Parity’s chief of staff Stuart Macdonald contested the “official” label, describing Hyperbridge as an independent parachain rather than a foundation‑endorsed bridge [1]. The recent exploit of Hyperbridge has been portrayed by former Polkassembly CEO Jaskirat Singh as symptomatic of broader missteps, including costly bridge funding and “insane fees” on Snowbridge, which received nearly $6 million in combined USDC and DOT in a 2024 governance vote before a later $3.4 million request was rejected [1].

Treasury payment disputes have further strained community trust. Polkassembly, which tracked over 1,700 referenda and served 250 000 participants, operated for eight months without compensation and later sought retroactive payment of 62,700 USDT. The proposal was overwhelmingly rejected, with roughly 0.2 % in favour and the W3F abstaining [1]. Parity noted that Polkassembly was never mandated by the foundation and that the community voted against the payment request [1].

Upcoming upgrades amid operational pullback

While governance frictions persist, Polkadot is preparing a substantial technical overhaul. The “JAM” (Join Accumulate Machine) upgrade, described by the Web3 Foundation as “Polkadot 3.0,” is expected to multiply the network’s computing power by ten, offering a more flexible and faster platform for applications [2]. Alongside JAM, a new DevContainer feature will allow developers to launch a Polkadot development environment with a single command, aiming to lower entry barriers and attract more builders [2].