[0.7.0-beta.6] Canister cycle balance remains the same after update call

I upgraded my dfx to 0.7.0-beta.6 recently, and noticed that the canister cycle balance does not change after update call, anyone know why?

I’m using this example for testing: examples/motoko/calc at 9ef9b9a08c8f953a1488b4f488a3ba866fd0405e · dfinity/examples · GitHub

1 Like

Is that a canister running on mainnet, local replica (via dfx start) or local emulator (via dfx start --emulator)?

This has to be local development, since the wallet canister id is rwlgt (which is the registry on mainnet); and likely the replica too since emulator more random with the canister ids it generates.
@ccyanxyz The replica shipped with dfx is configured such that it runs in a “system” subnet configuration, and so, there is no cycle accounting (think of it like a canister running on the NNS subnet where there’s no cycle cost.) This issue has been discussed internally between the DX and execution team and we know about it! Previously, you could expect to see cycles deducted for update calls and such. Unfortunately, the configuration change is a bit more involved than expected; when we reintroduce cycle accounting to local development, it will be highlighted in the release notes

3 Likes

Thanks for the explanation!