ICPWatch
Get alerts

CHAI Dapp #10 Stopped

d6dgo-aaaaa-aaaap-akpqq-cai
Cycle balance
unknown
Probed
Burn per day
n/a
needs more readings
Runway
n/a
Projected deletion
n/a
Run status
stopped
probed 49 min ago
Freezing threshold
37.5 B
30 days of idle burn
Idle burn
1.25 B / day
reported by controller
Memory
14.4 MiB
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 running with a healthy balance. Balance unknown, idle burn 1.25 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)
f04193df7c39ca7cdde0ab3df007c841c67636be304dc5615b25c73a00dc9995
Memo (required)
1347768404 ("TPUP" as a number)
Amount
0.0205 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

adb2cf82807bdf5e1cbc1fe99c2d6bd0f8b26be29a5db7e8ad44a278eb9590db

Upgrade and controller history

checked management canister canister_info

Code reinstalled (state wiped)

adb2cf8280...9590db → a9f5058396...dfcebd

· by principal 2b6nx-svnfk...nae · version 734

Module upgraded

9f714fc8b9...6a179c → adb2cf8280...9590db

· by canister xjngq-yaaaa...cai · version 719

Module upgraded

8bc506c3dc...2598fc → 9f714fc8b9...6a179c

· by canister xjngq-yaaaa...cai · version 387

Module upgraded

d4a5916185...e2d9f0 → 8bc506c3dc...2598fc

· by canister xjngq-yaaaa...cai · version 383

Module upgraded

b30f4a81bf...74a160 → d4a5916185...e2d9f0

· by canister xjngq-yaaaa...cai · version 302

Module upgraded

c40c21195f...65f8ca → b30f4a81bf...74a160

· by canister xjngq-yaaaa...cai · version 27

Module upgraded

4cd93e6ed6...78923f → c40c21195f...65f8ca

· by canister xjngq-yaaaa...cai · version 19

Module upgraded

277af36ceb...57af60 → 4cd93e6ed6...78923f

· by canister xjngq-yaaaa...cai · version 8

Controllers changed

· by principal 2ot7t-idkzt...zqe · version 5

Controllers changed

· by principal 2ot7t-idkzt...zqe · version 4

Module upgraded

878ae3c5fa...f22c47 → 277af36ceb...57af60

· by principal 2ot7t-idkzt...zqe · version 3

Code installed

earlier module not on record → 878ae3c5fa...f22c47

· by principal 2ot7t-idkzt...zqe · version 2

Controllers changed

· by principal 2ot7t-idkzt...zqe · version 1

Incidents

Same token group

CanisterTypeCyclesBurn / dayRunwayStatusData
CHAI Ledgervtrom-gqaaa-aaaaq-aabia-caiLedger45.73 T287 B~159 dHealthyMeasured
CHAI Indexv5tde-5aaaa-aaaaq-aabja-caiIndex33.21 T647 B~49 dHealthyMeasured
CHAI Archive #1r6akw-vqaaa-aaaaq-aabsa-caiArchive7.57 T32.8 B~205 dHealthyMeasured