ICPWatch
Get alerts

STK Ledger Healthy

5h55w-zaaaa-aaaal-qwzjq-cai
Get alerts
Cycle balance
10.06 T
Measured
Burn per day
8.95 B
observed from our readings
0.1 M/s · 373 M/hr · 62.7 B/wk · 269 B/mo
Runway
~3.0 y
freezes around Nov 4, 2029
Projected deletion
Dec 4, 2029
in 3.1 y if nothing changes
Run status
running
probed 8 min ago
Freezing threshold
n/a
not readable
Idle burn
n/a
Memory
51.7 MiB
measured canister /metrics endpointRole: Ledger · discovered via dex:ICPSwap on Sep 21, 2026

Community funding

Fund this canister

no community top-ups yet

This canister is running with a healthy balance. Balance 10.06 T.

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.

This canister is running and is not at risk right now. A top-up simply extends its runway.
Top-up account (ICP account id)
21dc22ba492ec3587884fabd0ca8374fbcbda2a201136004599994f00b957d8a
Memo (required)
1347768404 ("TPUP" as a number)
Amount
0.2720 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

26aa219301802d4d6342978247fda97123b33373e33310a8b8a6e2c8afa92835
Subnet e66qm-3cydn...5qe

Upgrade and controller history

checked management canister canister_info

Module upgraded

26aa219301...a92835 → 83b4eea2cb...56c22f

· by principal cmanb-aejth...3qe · version 235,746

Controllers changed

+ 2llw7-vw2z4-ekbj2-awmcs-ahjzo-okzqd-hbir7-a3yg2-cj4s7-5mpmr-mqe
· by principal cmanb-aejth...3qe · version 143,868

Upgraded with the same module

26aa219301...a92835 → 26aa219301...a92835

· by principal cmanb-aejth...3qe · version 95

Code reinstalled (state wiped)

26aa219301...a92835 → 26aa219301...a92835

· by principal cmanb-aejth...3qe · version 30

Code reinstalled (state wiped)

26aa219301...a92835 → 26aa219301...a92835

· by principal cmanb-aejth...3qe · version 29

Controllers changed

+ a6p2m-tiaaa-aaaal-qwxba-cai
· by principal cmanb-aejth...3qe · version 4

Code reinstalled (state wiped)

26aa219301...a92835 → 26aa219301...a92835

· by principal cmanb-aejth...3qe · version 3

Code reinstalled (state wiped)

26aa219301...a92835 → 26aa219301...a92835

· by principal cmanb-aejth...3qe · version 2

Code installed

earlier module not on record → 26aa219301...a92835

· by principal cmanb-aejth...3qe · version 1

Canister created

cmanb-aejth-shdoi-krt5o-ijy5p-tineu-7lrav-guzka-k4qxk-2f55o-3qe
· by canister rkp4c-7iaaa...cai · version 0

Incidents

Resolved: STK Ledger

Burning 0.07 T per day, 3.8x its own 31-day baseline of 0.02 T. Busy canisters do not trip this, spikes do.

· fired once per incident · open for 11 h

Resolved: STK Ledger

Burning 0.07 T per day, 3.9x its own 31-day baseline of 0.02 T. Busy canisters do not trip this, spikes do.

· fired once per incident · open for 6 h

Resolved: STK Ledger

Burning 0.10 T per day, 5.7x its own 28-day baseline of 0.02 T. Busy canisters do not trip this, spikes do.

· fired once per incident · open for 30 h

Resolved: STK Ledger

Burning 0.10 T per day, 5.6x its own 27-day baseline of 0.02 T. Busy canisters do not trip this, spikes do.

· fired once per incident · open for 20 h

Resolved: STK Ledger

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

· fired once per incident · open for 40 h

Resolved: STK Ledger

Burning 0.07 T per day, 3.9x its own 26-day baseline of 0.02 T. Busy canisters do not trip this, spikes do.

· fired once per incident · open for 24 h

Resolved: STK Ledger

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

· fired once per incident · open for 25 h

Resolved: STK Ledger

Burning 0.07 T per day, 3.9x its own 24-day baseline of 0.02 T. Busy canisters do not trip this, spikes do.

· fired once per incident · open for 22 h

Resolved: STK Ledger

Burning 0.07 T per day, 3.9x its own 23-day baseline of 0.02 T. Busy canisters do not trip this, spikes do.

· fired once per incident · open for 4 h

Resolved: STK Ledger

Burning 0.07 T per day, 4.0x its own 21-day baseline of 0.02 T. Busy canisters do not trip this, spikes do.

· fired once per incident · open for 4 h