TechFlow news, Husky.io, Chief Security Officer of Solana-based DePIN protocol Io.net, released an update this morning regarding the recent io.net metadata API attack incident. As previously announced, zero-trust authentication (OKTA) at the device level has been accelerated to prevent future occurrences. This requires all nodes to restart and upgrade to the latest client. Unfortunately, this coincided with the rewards program snapshot timing, exacerbating the expected reduction in supply-side participants. Even genuinely existing, proof-of-work-verified GPUs that did not restart and update lost access to the runtime API and could no longer send heartbeats to io.net, causing the number of active GPU connections to drop sharply from 600,000 to just 10,000.
In response, Season Two of Ignition Rewards launched in May to incentivize supply-side participation. The team is working directly with suppliers to complete upgrades, restarts, and reconnections to the network. Security vulnerabilities have been fixed, and self-service clusters have been re-enabled. Development of self-service large-scale clusters is now underway. The browser interface is being updated to more clearly display devices that recently connected but are unverified, those verified via proof-of-work, and those both verified and actively sending heartbeats.
Husky.io stated: "There are many bugs to fix, the user interface needs improvement, and demand must grow. Despite these challenges, the network continues to deliver hundreds of thousands of compute hours each month—and it's growing. We're still in the early stages, and there will be bumps along the way."
