ICPWatch
Get alerts

ICPEx Dapp #6 Healthy

arfmo-qqaaa-aaaaj-az7ta-cai
Get alerts
Cycle balance
20.66 T
Measured
Burn per day
8.85 B
observed from our readings
0.1 M/s · 369 M/hr · 61.9 B/wk · 265 B/mo
Runway
~6.4 y
freezes around Mar 19, 2033
Projected deletion
Apr 18, 2033
in 6.5 y if nothing changes
Run status
running
probed 41 min ago
Freezing threshold
92.6 B
30 days of idle burn
Idle burn
3.09 B / day
reported by controller
Memory
83.0 MiB
measured SNS root canister statusRole: Dapp · discovered via sns-aggregator on Sep 21, 2026

Community funding

Fund this canister

no community top-ups yet

This canister is running with a healthy balance. Balance 20.66 T, idle burn 3.09 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.

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

fd7935a9e22cefc5d7cd344f0841c0b9e561a7e8008a406c536ac3ea9b0f483f
Subnet qdvhd-os4o2...yqe

Upgrade and controller history

checked management canister canister_info

Controllers changed

Same controller set as before.

· by canister jpz24-eqaaa...cai · version 276,526

Module upgraded

5d423a1ef5...a7565e → fd7935a9e2...0f483f

· by canister jpz24-eqaaa...cai · version 106,864

Module upgraded

1ef705d9cf...f954be → 5d423a1ef5...a7565e

· by canister jpz24-eqaaa...cai · version 22,050

Module upgraded

84dda48780...ca14a1 → 1ef705d9cf...f954be

· by canister jpz24-eqaaa...cai · version 4,372

Module upgraded

3c1d677650...edf484 → 84dda48780...ca14a1

· by canister jpz24-eqaaa...cai · version 2,608

Module upgraded

26745e7894...16659e → 3c1d677650...edf484

· by canister jpz24-eqaaa...cai · version 1,963

Controllers changed

- ycldc-nqlnq-2a6wb-dvwww-l27id-nk26e-keoth-kjhnb-fexsm-znjvf-yae
· by canister jpz24-eqaaa...cai · version 22

Module upgraded

dd666987f1...129d32 → 26745e7894...16659e

· by principal ycldc-nqlnq...yae · version 13

Code reinstalled (state wiped)

70109892c5...eab8e6 → dd666987f1...129d32

· by principal ycldc-nqlnq...yae · version 9

Controllers changed

+ jpz24-eqaaa-aaaaq-aaexq-cai
· by principal ycldc-nqlnq...yae · version 8

Code installed

earlier module not on record → 70109892c5...eab8e6

· by canister piwiu-wiaaa...cai · version 1

Canister created

piwiu-wiaaa-aaaaj-azzka-cai
· by canister piwiu-wiaaa...cai · version 0

Incidents

Resolved: ICPEx Dapp #6

Burning 0.32 T per day, 39.0x its own 13-day baseline of 0.01 T. Busy canisters do not trip this, spikes do.

· fired once per incident · open for 43 h

Same token group

CanisterTypeCyclesBurn / dayRunwayStatusData
ICX Ledgerlvfsa-2aaaa-aaaaq-aaeyq-caiLedger17.88 T267 B~66 dHealthyMeasured
ICX Indexl3h7i-bqaaa-aaaaq-aaezq-caiIndex19.19 T557 B34 d to freezeAt riskMeasured
ICX Archive #1ljbir-naaaa-aaaaq-aae2q-caiArchive10.04 T9.00 B~3.0 yHealthyMeasured