ICPWatch
Get alerts

iDoge Ledger Frozen

eayyd-iiaaa-aaaah-adtea-cai
Get alerts
Cycle balance
93.23 T
Measured
Burn per day
3.17 T
observed from our readings
36.7 M/s · 132 B/hr · 22.21 T/wk · 95.17 T/mo
Runway
29 d to deletion
freezes around Nov 5, 2026
Projected deletion
Dec 5, 2026
in 29 d if nothing changes
Run status
running
probed 66 s ago
Freezing threshold
n/a
30 days of idle burn
Idle burn
n/a
Memory
10.7 MiB
measured blackhole controller statusRole: Ledger · discovered via seed 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 93.23 T, idle burn 3.17 T/day (estimated from its own decline), deletion in about 29 d.

Nobody outside this canister's controllers can read its idle burn, so 3.172 T per day is our own estimate from watching it burn while frozen. Every amount and date below is approximate.
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.

A revived canister answers calls again and goes back to burning at its normal rate: about 3.172 T per day. Of each amount below, 2.228 T only lifts the balance over the freezing threshold (95.171 T) and the rest is runway.
We have no record of what this canister burned while it was running, so the runway uses its storage cost alone. Real usage burns more: expect the runway to be shorter than shown.
Reviving does not give you or ICPWatch any control. Its controllers may have let it freeze on purpose, and they can change its settings at any time.
Top-up account (ICP account id)
164bbb17983a9258561810c3ee538780f6944daf86974ac623959ee35fd6a12b
Memo (required)
1347768404 ("TPUP" as a number)
Amount
55.2308 ICP

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

67d928a0605b5b230f7f8d564878b5bc6c799657d1b77898ef27fe66e02e4c3d
Subnet gmq5v-hbozq...3ae

Upgrade and controller history

checked management canister canister_info

Code reinstalled (state wiped)

67d928a060...2e4c3d → 67d928a060...2e4c3d

· by principal oggmb-y3ymj...gqe · version 14

Code reinstalled (state wiped)

67d928a060...2e4c3d → 67d928a060...2e4c3d

· by principal oggmb-y3ymj...gqe · version 12

Code reinstalled (state wiped)

67d928a060...2e4c3d → 67d928a060...2e4c3d

· by principal oggmb-y3ymj...gqe · version 10

Code reinstalled (state wiped)

67d928a060...2e4c3d → 67d928a060...2e4c3d

· by principal oggmb-y3ymj...gqe · version 4

Code reinstalled (state wiped)

67d928a060...2e4c3d → 67d928a060...2e4c3d

· by principal oggmb-y3ymj...gqe · version 3

Code installed

earlier module not on record → 67d928a060...2e4c3d

· by principal oggmb-y3ymj...gqe · version 1

Canister created

oggmb-y3ymj-k6gww-jpegb-uossk-k5ocm-dav4p-jkoig-sudlb-gotak-gqe
· by canister aanaa-xaaaa...cai · version 0

Incidents

Burn-rate anomaly: iDoge Ledger

Burning 3.17 T per day, 8.1x its own 31-day baseline of 0.39 T. Busy canisters do not trip this, spikes do.

· fired once per incident

Resolved: IDOGE Ledger

Burning 1.87 T per day, 4.8x its own 31-day baseline of 0.39 T. Busy canisters do not trip this, spikes do.

· fired once per incident · open for 3 d

Resolved: iDoge Ledger

Burning 2.63 T per day, 6.7x its own 31-day baseline of 0.39 T. Busy canisters do not trip this, spikes do.

· fired once per incident · open for 5 d

Resolved: iDoge Ledger

Burning 1.79 T per day, 4.6x its own 31-day baseline of 0.39 T. Busy canisters do not trip this, spikes do.

· fired once per incident · open for 35 h

Low cycles: iDoge Ledger

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

· fired once per incident

Resolved: iDoge Ledger

3.30 T left, about 0 days until it freezes at the current burn of 0.23 T per day.

· fired once per incident · open for 10 d

Resolved: iDoge Ledger

6.77 T left, about 1 days until it freezes at the current burn of 0.22 T per day.

· fired once per incident · open for 8 d

Resolved: iDoge Ledger

9.62 T left, about 0 days until it freezes at the current burn of 0.39 T per day.

· fired once per incident · open for 7 d

Resolved: IDOGE Ledger

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

· fired once per incident · open for 22 h