# ICP Cloud Engines Plan Allocates 20% of Revenue to Token Burns

By Simon Yoon

Canonical URL: https://www.tokenpost.com/news/technology/29998
Published: 2026-10-12T02:49:10.000Z
Updated: 2026-10-12T02:49:10.000Z
Section: Technology

> DFINITY’s enterprise cloud initiative is linked to Mission 70, but large-scale adoption and measurable Cloud Engines burn data remain unproven.

DFINITY’s Cloud Engines program plans to direct 20% of enterprise cloud revenue toward buying and burning Internet Computer (ICP), linking customer adoption to Mission 70’s effort to reduce the network’s inflation rate.

Node providers would retain 80% of customer revenue, while the remaining 20% would fund ICP purchases and burns. Mission 70 targets a reduction in ICP’s inflation rate from 9.72% to 2.92% if its measures achieve their stated goals.

Cloud Engines allows companies to create private subnets on the Internet Computer using selected node providers, locations, hardware and replica counts. The private environments use the same underlying protocol, smart contracts and chain-key cryptography as the public network.

Companies can choose listed nodes and hardware through opencloud.org and create a subnet with at least four nodes. The structure is intended to address vendor lock-in and data-sovereignty needs, including potential use cases in financial, medical and government settings.

The program is in early access. Available functions include sovereign isolation, single tenancy, hardware selection and fixed costs. SEV-encrypted nodes and operator-controlled upgrades remain roadmap features rather than available capabilities.

Existing projects cited for Cloud Engines include Pakistan’s national Cloud Engine and a pilot involving the United Nations Development Programme. Pakistan’s ChatT sovereign communications application has entered a promotion phase. Those deployments show that the product can operate, but they do not establish large-scale enterprise adoption.

Mission 70 divides its proposed inflation reduction between supply and demand measures. Lower node rewards and a smaller minimum subnet size would provide 44% of the targeted reduction, while additional token burns would account for the remaining 26%.

The demand-side portion depends on Cloud Engines producing enough revenue to generate substantial additional burns. The current daily burn base is about $6,000, while the program would need additional burns in the tens of thousands of dollars per day to support that part of the plan.

ICP’s current network-wide cycle-burn rate is about 0.0689 TCYCLES per second. Mission 70 sets a target of 0.77 XDR per second, roughly 15 times the current rate.

The supply-side changes would require governance decisions, including a proposed 40% reduction in first-generation node rewards and a reduction in the minimum subnet size from 13 nodes to seven. Cloud Engines’ contribution would instead depend on customer adoption, revenue scale and the resulting burn activity.

The planned 20% allocation therefore remains a mechanism to be tested through operating data. The first quantifiable Cloud Engines burn figures will be needed to assess its effect on ICP’s supply dynamics.