ICPWatch
Get alerts

Motoko Dapp #2 Frozen

hhce5-bqaaa-aaaak-qtt3q-cai
Cycle balance
unknown
Probed
Burn per day
n/a
needs more readings
Runway
frozen
Projected deletion
n/a
Run status
frozen
probed 66 s ago
Freezing threshold
6.87 T
30 days of idle burn
Idle burn
229 B / day
reported by controller
Memory
8.31 GiB
measured query probeRole: Dapp · discovered via sns-aggregator on Sep 21, 2026

Community funding

Fund this canister

no community top-ups yet

This canister is frozen: it rejects calls and burns only storage cost until it hits zero and is deleted. Balance unknown, idle burn 229 B/day.

Top-ups cannot be refunded or withdrawn, by you, by ICPWatch, or by anyone else. The cycles belong to the canister.

Revive: enough to bring it above the freezing threshold and running again. A revived canister burns at its normal rate again, so it needs a controller or a community that keeps funding it.

The balance or the freezing threshold is not readable from outside, so the amount needed to unfreeze it cannot be computed. You can still send a custom amount.
Top-up account (ICP account id)
39c451376b8c76932ff6e38e358f798bbd1f14707cff3ba71289540b6bd7aa09
Memo (required)
1347768404 ("TPUP" as a number)
Amount
n/a

This is the canister's own top-up account on the Cycles Minting Canister, not an ICPWatch address. The memo is what tells the CMC which canister to credit: a transfer without it is refunded automatically by the CMC (minus the ledger fee), so exchanges that cannot set a memo will not work. Once ICP lands, ICPWatch asks the CMC to convert it; nothing else is needed.

Waiting: the account is checked every few minutes for a day after you click.

Non-custodial and non-refundable: ICP goes to the canister through the CMC and becomes that canister's cycles. ICPWatch never holds it and cannot reverse it. Anyone may top up any canister; that is how the Internet Computer works. Top-ups appear in the public record below once the CMC has credited them.

Cycle balance over time

Controllers

read_state, certified by the subnet

Module

c3b620fd79912a3a276c59618dc369f74ec6a52c2a7baee68626966f18c0f80d

Upgrade and controller history

checked management canister canister_info

Controllers changed

· by principal uebn2-6maen...mae · version 7,268,015

Controllers changed

· by principal ufwij-jggzv...gae · version 7,267,809

Controllers changed

· by principal ufwij-jggzv...gae · version 6,884,088

Module upgraded

5b574caf07...da2a4f → c3b620fd79...c0f80d

· by principal ufwij-jggzv...gae · version 6,874,113

Module upgraded

48c57cd648...1464c5 → 5b574caf07...da2a4f

· by principal ufwij-jggzv...gae · version 6,874,112

Module upgraded

ffcbeff280...d2d684 → 48c57cd648...1464c5

· by principal ufwij-jggzv...gae · version 6,872,417

Module upgraded

56d07071a1...7916a8 → ffcbeff280...d2d684

· by principal ufwij-jggzv...gae · version 6,871,132

Module upgraded

c3546ef7d3...7deabf → 56d07071a1...7916a8

· by principal ufwij-jggzv...gae · version 6,870,992

Module upgraded

bcb344455e...ca9c9d → c3546ef7d3...7deabf

· by principal ufwij-jggzv...gae · version 6,869,615

Module upgraded

924a791ac5...995ceb → bcb344455e...ca9c9d

· by principal ufwij-jggzv...gae · version 6,869,413

Module upgraded

fedd273f40...b995d9 → 924a791ac5...995ceb

· by principal ufwij-jggzv...gae · version 6,869,410

Code installed

earlier module not on record → fedd273f40...b995d9

· by canister 7lben-uqaaa...cai · version 1

Canister created

· by canister 7lben-uqaaa...cai · version 0

Incidents

Frozen: Motoko Dapp #2

The canister is rejecting calls because its balance is below the freezing threshold.

· fired once per incident

Resolved: Motoko Dapp #2

The canister is rejecting calls because its balance is below the freezing threshold.

· fired once per incident · open for 8 d

Resolved: Motoko Dapp #2

Burning 50.6 T per day, 225.4x its own 31-day baseline of 0.22 T. Busy canisters do not trip this, spikes do.

· fired once per incident · open for 38 h

Low cycles: Motoko Dapp #2

83.5 T left, about 6 days until it freezes at the current burn of 13.3 T per day.

· fired once per incident

Resolved: Motoko Dapp #2

Burning 60.0 T per day, 267.0x its own 31-day baseline of 0.22 T. Busy canisters do not trip this, spikes do.

· fired once per incident · open for 16 h

Resolved: Motoko Dapp #2

89.2 T left, about 9 days until it freezes at the current burn of 9.60 T per day.

· fired once per incident · open for 18 h

Resolved: Motoko Dapp #2

Burning 57.7 T per day, 257.1x its own 31-day baseline of 0.22 T. Busy canisters do not trip this, spikes do.

· fired once per incident · open for 17 h

Resolved: Motoko Dapp #2

84.2 T left, about 14 days until it freezes at the current burn of 5.57 T per day.

· fired once per incident · open for 16 h

Resolved: Motoko Dapp #2

Burning 48.1 T per day, 213.4x its own 31-day baseline of 0.23 T. Busy canisters do not trip this, spikes do.

· fired once per incident · open for 18 h

Resolved: Motoko Dapp #2

51.8 T left, about 12 days until it freezes at the current burn of 3.62 T per day.

· fired once per incident · open for 2 h

Same token group

CanisterTypeCyclesBurn / dayRunwayStatusData
MOTOKO Ledgerk45jy-aiaaa-aaaaq-aadcq-caiLedger137.2 T305 B~450 dHealthyMeasured
MOTOKO Indexks7eq-3yaaa-aaaaq-aaddq-caiIndex308.4 T586 B~526 dHealthyMeasured
MOTOKO Archive #1j6iuh-qyaaa-aaaaq-aadjq-caiArchive22.82 T11.0 B~5.7 yHealthyMeasured