A proposal to create the first test cloud engine on the Internet Computer is moving through governance with strong early backing from voters.
The proposal would create a cloud engine made up of four cloud nodes hosted across AWS, Google Cloud Platform and Azure. According to the proposal text, the aim is to test protocol changes including areas such as subnet shielding, firewall isolation and registry replication.
Early voting figures show more than 94 per cent support for the proposal, with participation already well above the threshold required for adoption.
Unlike traditional nodes on the network, cloud engine nodes would not receive fixed payments. Instead, operators would earn a share of the revenue generated by the engine itself. Under the proposal, 80 per cent of revenue would go to the nodes in the engine, while the remaining 20 per cent would be used to burn ICP.
Supporters argue that the model could give the Internet Computer a new way to test cloud-based infrastructure while also creating a deflationary mechanism tied to network activity. Burning ICP reduces the total supply of the token, which some community members see as beneficial if usage of cloud engines expands over time.
The proposal comes as blockchain projects continue to look for new ways to balance network rewards with token supply. Revenue-sharing models tied to real usage have become increasingly common across decentralised infrastructure projects, particularly as communities push for systems that can support themselves without relying entirely on inflation.
At the same time, the use of large cloud providers such as AWS, Google Cloud Platform and Azure may attract debate from those who favour fully decentralised infrastructure. Critics of cloud-hosted blockchain systems often argue that dependence on major providers can create concentration risks, even when nodes are spread across several platforms.
For now, the proposal appears to be positioned as an experiment rather than a permanent shift in how the Internet Computer network operates. The focus is on testing how cloud engines could work, how they generate revenue and whether the model can support future infrastructure without fixed network payouts.
Dear Reader,
Ledger Life is an independent platform dedicated to covering the Internet Computer (ICP) ecosystem and beyond. We focus on real stories, builder updates, project launches, and the quiet innovations that often get missed.
We’re not backed by sponsors. We rely on readers like you.
If you find value in what we publish—whether it’s deep dives into dApps, explainers on decentralised tech, or just keeping track of what’s moving in Web3—please consider making a donation. It helps us cover costs, stay consistent, and remain truly independent.
Your support goes a long way.
🧠 ICP Principal: ins6i-d53ug-zxmgh-qvum3-r3pvl-ufcvu-bdyon-ovzdy-d26k3-lgq2v-3qe
🧾 ICP Address: f8deb966878f8b83204b251d5d799e0345ea72b8e62e8cf9da8d8830e1b3b05f
Every contribution helps keep the lights on, the stories flowing, and the crypto clutter out.
Thank you for reading, sharing, and being part of this experiment in decentralised media.
—Team Ledger Life
Community Discussion