The latest release from the Internet Computer ecosystem, icptopup-ts, is setting a new standard for handling decentralised compute resources. Designed as a TypeScript package, it streamlines the process of sending cycles to multiple canisters simultaneously, making it significantly easier for developers to manage large-scale applications. With a single command—npm install icptopup-ts—developers can integrate atomic, ICRC-compatible cycle top-ups into their dApps in just a few minutes.
Efficiency is at the core of icptopup-ts. The package provides both synchronous and asynchronous methods for transferring cycles, catering to different user experience requirements. Whether operating on the frontend or in a NodeJS environment, it slots in seamlessly, eliminating unnecessary friction in development.
Over the past few weeks, developers have already leveraged icptopup-ts to mint and send over 30,000T cycles across more than 21,000 individual canister top-ups. This level of adoption underscores its ability to simplify a previously complex and error-prone process.
Before icptopup-ts, converting ICP to cycles posed several challenges. The process involved multiple steps—first transferring ICP, then submitting a separate request to burn it in exchange for cycles. This non-atomic approach meant that if an issue arose mid-process, users could find themselves in an inconsistent state, where funds had been sent but no cycles were received.
Another long-standing issue was the lack of ICRC compatibility within the Cycles Minting Canister (CMC). Without native support for ICRC transfers, developers had to perform an extra step—moving funds to a non-ICRC account before sending them to the CMC. This not only increased complexity but also introduced additional points of failure.
Batch processing was yet another limitation. The CMC lacked an API for minting cycles in bulk, meaning developers had to individually handle each cycle minting transaction. The additional complexity led to inefficiencies and increased costs, as separate transactions incurred unnecessary fees.
Icptopup-ts addresses all these concerns by offering a streamlined, atomic, ICRC-compatible API for topping up multiple canisters in parallel. The package utilises ICRC-2 approvals, allowing it to handle ICP transfers and cycle top-ups in a two-step process. First, the developer grants approval for icptopup-ts to mint cycles. This approval doesn’t transfer ICP but simply authorises the process. Then, a single API call executes both the ICRC-2 transfer and the cycle minting action.
Behind the scenes, icptopup-ts is built on the ICPTopup Service, which integrates with a dedicated backend canister. This ensures that every top-up is executed atomically, reducing risks and making the process far more reliable. By unifying the ICP transfer, cycle minting, and batch distribution steps into a single API, it provides a more efficient alternative to previous methods.
The launch of icptopup-ts is expected to enhance developer productivity, making it easier to manage decentralised applications on the Internet Computer. The team behind the package is eager to see how the community adopts it and welcomes feedback. With a robust API and a focus on simplicity, icptopup-ts is another step toward refining the way developers interact with on-chain resources.
