(Have a question that isn’t answered here? Let us know at [email protected])

How often do you check cycles balances?

Currently CycleOps checks cycles balances once every 6 hours and performs top-ups accordingly.

Want more frequent top-ups? Let us know at [email protected] or on Twitter.

Why do I need to add the CycleOps Balance Checker as a controller of my canister in order to have my canister cycles balance monitored?

CycleOps provides a no-code integration for monitoring your canisters. This means that you do not need to add a single line of code to your canister or application.

In order to do this, the Balance Checker calls the Management Canister’s canister_status API, which allows only the controller of a canister to call it.

The Balance Checker canister, canister id 5vdms-kaaaa-aaaap-aa3uq-cai is black-holed (has 0 controllers), and only contains code that allows it to check the status of other canisters it controls. To verify the wasm binary running in the Balance Checker and black-hole status of the canister for yourself, check out the source code at https://github.com/CycleOperators/BalanceCheckerVerification

How can I trust the code that the CycleOps Balance Checker is running won’t change?

The CycleOps Balance Checker is black-holed, and the source code for it is public at https://github.com/CycleOperators/BalanceCheckerVerification.

There, you can follow the steps listed in the repository to:

• Verify that the wasm hash of the canister code is the same as the Balance Checker canister 5vdms-kaaaa-aaaap-aa3uq-cai running on main net
• Review the Balance Checker code, to ensure it is not able to do anything except check the statuses of other canisters.

What is a Black-holed Canister?