David Dal Busco, the creator of Juno, has announced that the next major version of the open-source serverless platform will move away from direct ICP token usage and rely solely on cycles. The change was shared in a post on X alongside a short demo showing a successful deployment using Juno’s command-line tools.
Juno operates on the Internet Computer and positions itself as a developer-friendly backend platform, offering services such as authentication, storage and hosting in a model often compared with Firebase. By removing direct interactions with the ICP token, Dal Busco says the platform’s workflow becomes simpler and easier to reason about for developers building decentralised applications.
Cycles act as the computation fuel of the Internet Computer and are created by converting ICP tokens. Once converted, they are used to pay for compute and storage in a way that resembles traditional cloud billing, where developers focus on usage rather than token mechanics. By standardising on cycles alone, Juno removes the need for developers to think about token conversions during deployment and operation.
According to Dal Busco, the shift is aimed at reducing friction rather than changing the economic foundations of the platform. Existing ICP holdings connected to Juno will still be visible and manageable through the Mission Control dashboard, which is intended to preserve continuity for current users. The underlying process of converting ICP into cycles remains part of the system, but it is pushed further into the background.
For developers, the practical impact is a more streamlined experience. Deployments, updates and ongoing operations can be handled without direct exposure to token balances, which may appeal to teams coming from traditional web development backgrounds. This aligns with Juno’s broader goal of making decentralised infrastructure feel familiar and accessible, particularly for those building consumer-facing applications.
The decision also reflects wider design choices within the Internet Computer ecosystem, where cycles are promoted as a way to abstract costs and reduce volatility concerns tied to token prices. Supporters argue that this model allows developers to plan and budget more predictably, while critics sometimes point out that cycles still depend on ICP market dynamics at the point of conversion.
From an adoption perspective, the move may lower the barrier for experimentation. Developers evaluating Juno no longer need to manage token flows directly, which could make early testing and prototyping more straightforward. At the same time, the change does not alter the underlying trust or execution model of the Internet Computer, which continues to rely on WebAssembly canisters and on-chain governance.
As with any platform-level adjustment, the longer-term effects will depend on how developers respond once the new version is released. Some may welcome the cleaner separation between application logic and token economics, while others may prefer more direct control over how resources are funded.
For now, Dal Busco’s announcement signals a continued effort to refine developer experience within the ICP ecosystem. By leaning fully into cycles, Juno is placing simplicity and usability at the centre of its next iteration, while leaving open questions about how developers balance abstraction with transparency as decentralised infrastructure matures.
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
🪙 BTC Wallet: bc1pp5kuez9r2atdmrp4jmu6fxersny4uhnaxyrxau4dg7365je8sy2q9zff6p
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
