ICP votes to upgrade 80% of its cloud engines
NNS Proposal 144100 passed with 88.5% support and not a single vote against, moving the bulk of the network’s cloud engines to a new replica version — infrastructure upgraded not by a vendor’s ops team, but by an on-chain vote that executed itself.
The Internet Computer has completed a network upgrade covering 80% of its cloud engines after NNS Proposal 144100 was adopted, moving the targeted engines to replica version 2c2c7c9. The vote recorded 88.501% support — 620,938,494 voting power in favour, none against — and executed automatically once it passed.
The NNS is the network’s on-chain governance system: ICP holders vote on proposals and adopted changes run themselves, with no central operator pushing the update. Here that machinery was aimed at infrastructure rather than protocol economics — a whole fleet of engines moved in one coordinated, recorded action.
Cloud engines are configurable private subnets: operators choose the underlying nodes, providers and geographic locations, giving organisations control over where applications run and how they’re spread. ICP pitches them as an alternative to traditional cloud for anyone worried about data location, regulation, or leaning on a single provider — the same argument Dominic Williams made in last week’s lead, drawing on the game he lost to one deleted database.
The caveat holds: the vote shows the network can coordinate an infrastructure upgrade on-chain, but claims about cloud engines replacing conventional providers or delivering full sovereignty remain part of ICP’s pitch rather than a settled outcome. Earlier this year a test engine spanning major cloud providers trialled subnet shielding, firewall isolation and registry replication.
