ICPWatch
Get alerts

OpenChat Dapp #10 Healthy

5cz5j-uiaaa-aaaaf-bsdda-cai
Cycle balance
199.9 T
Measured
Burn per day
6.37 B
observed from our readings
0.1 M/s · 265 M/hr · 44.6 B/wk · 191 B/mo
Runway
50+ y
Projected deletion
n/a
Run status
running
probed 3 min ago
Freezing threshold
28.1 B
30 days of idle burn
Idle burn
937 M / day
reported by controller
Memory
2.7 MiB
measured SNS root canister statusRole: Dapp · discovered via sns-aggregator on Oct 2, 2026

Community funding

Fund this canister

no community top-ups yet

This canister is running with a healthy balance. Balance 199.9 T, idle burn 937 M/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)
325102db09e85dd237f5fff6a98a2feaecf41100cea8e84864fdc90c8ee34336
Memo (required)
1347768404 ("TPUP" as a number)
Amount
0.1194 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

e37b803af964c69e6efd848134de9960e05de62df24482a1374df2ac5180c766

Upgrade and controller history

checked management canister canister_info

Module upgraded

44fad0f1dd...5f74a8 → e37b803af9...80c766

· by canister 3e3x2-xyaaa...cai · version 16,537

Module upgraded

8c9b13eb3b...29aa40 → 44fad0f1dd...5f74a8

· by canister 3e3x2-xyaaa...cai · version 14,526

Code installed

earlier module not on record → 8c9b13eb3b...29aa40

· by canister 3e3x2-xyaaa...cai · version 6

Controllers changed

Same controller set as before.

· by principal tu45y-p4p3d...pae · version 2

Controllers changed

· by principal tu45y-p4p3d...pae · version 1

Incidents

Same token group

CanisterTypeCyclesBurn / dayRunwayStatusData
CHAT Ledger2ouva-viaaa-aaaaq-aaamq-caiLedger140.2 T444 B~315 dHealthyMeasured
CHAT Index2awyi-oyaaa-aaaaq-aaanq-caiIndex187.6 T705 B~265 dHealthyMeasured
CHAT Archive #12sqpr-ciaaa-aaaaq-aaaoq-caiArchive189.1 T24.9 B~20.7 yHealthyMeasured