ICPWatch
Get alerts

DAO Index At risk

j57nf-iaaaa-aaaaq-aaeuq-cai
Cycle balance
3.01 T
Measured
Burn per day
174 B
observed from our readings
2.0 M/s · 7.23 B/hr · 1.21 T/wk · 5.21 T/mo
Runway
16 d to freeze
freezes around Nov 22, 2026
Projected deletion
Dec 22, 2026
in 46 d if nothing changes
Run status
running
probed 32 min ago
Freezing threshold
177 B
30 days of idle burn
Idle burn
5.89 B / day
reported by controller
Memory
51.8 MiB
measured SNS root canister statusRole: Index · discovered via sns-aggregator on Sep 21, 2026

Community funding

Fund this canister

no community top-ups yet

This canister is running but low on cycles. Balance 3.01 T, idle burn 5.89 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.

Top-up account (ICP account id)
f790bb7b23b69e5df789a58a6909879aac1ba2c80fde4c3d2762e8f60b86d87d
Memo (required)
1347768404 ("TPUP" as a number)
Amount
2.8916 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

cf3bf8f87dc908be156f314fae3b83aae56d1f63e74a63c32994c4e02babdb2d

Upgrade and controller history

checked management canister canister_info

Module upgraded

73eb5d98d6...1265e5 → cf3bf8f87d...abdb2d

· by canister izscx-raaaa...cai · version 41,670,405

Module upgraded

b2795770be...0801f4 → 73eb5d98d6...1265e5

· by canister izscx-raaaa...cai · version 9,190,435

Module upgraded

bb73b53320...03d560 → b2795770be...0801f4

· by canister izscx-raaaa...cai · version 7,087,138

Module upgraded

2e98628c89...0565f7 → bb73b53320...03d560

· by canister izscx-raaaa...cai · version 7,086,372

Module upgraded

511f16457d...e01d2e → 2e98628c89...0565f7

· by canister izscx-raaaa...cai · version 6,983,655

Module upgraded

58c682f5a2...41b64f → 511f16457d...e01d2e

· by canister izscx-raaaa...cai · version 3,630,141

Module upgraded

e155db9d06...12935f → 58c682f5a2...41b64f

· by canister izscx-raaaa...cai · version 3,629,636

Controllers changed

· by canister qaa6y-5yaaa...cai · version 156

Controllers changed

· by canister qaa6y-5yaaa...cai · version 39

Code installed

earlier module not on record → e155db9d06...12935f

· by canister qaa6y-5yaaa...cai · version 1

Canister created

· by canister qaa6y-5yaaa...cai · version 0

Incidents

Resolved: DAO Index

Burning 4.34 T per day, 2263.8x its own 31-day baseline of 0.00 T. Busy canisters do not trip this, spikes do.

· fired once per incident · open for 9 h

Resolved: DAO Index

3.54 T left, about 11 days until it freezes at the current burn of 0.31 T per day.

· fired once per incident · open for 11 h

Resolved: DAO Index

Burning 4.31 T per day, 2250.3x its own 31-day baseline of 0.00 T. Busy canisters do not trip this, spikes do.

· fired once per incident · open for 7 h

Resolved: DAO Index

3.52 T left, about 11 days until it freezes at the current burn of 0.31 T per day.

· fired once per incident · open for 10 h

Resolved: DAO Index

Burning 4.28 T per day, 2234.5x its own 31-day baseline of 0.00 T. Busy canisters do not trip this, spikes do.

· fired once per incident · open for 7 h

Resolved: DAO Index

3.49 T left, about 10 days until it freezes at the current burn of 0.32 T per day.

· fired once per incident · open for 10 h

Resolved: DAO Index

Burning 4.33 T per day, 2258.2x its own 31-day baseline of 0.00 T. Busy canisters do not trip this, spikes do.

· fired once per incident · open for 7 h

Resolved: DAO Index

2.55 T left, about 13 days until it freezes at the current burn of 0.18 T per day.

· fired once per incident · open for 16 h

Resolved: DAO Index

Burning 4.32 T per day, 2254.9x its own 31-day baseline of 0.00 T. Busy canisters do not trip this, spikes do.

· fired once per incident · open for 7 h

Resolved: DAO Index

3.45 T left, about 10 days until it freezes at the current burn of 0.32 T per day.

· fired once per incident · open for 13 h

Same token group

CanisterTypeCyclesBurn / dayRunwayStatusData
DAO Ledgerixqp7-kqaaa-aaaaq-aaetq-caiLedger2.22 T1.26 T39 h to freezeLow cycles FundMeasured
DAO Indexj57nf-iaaaa-aaaaq-aaeuq-caiIndex3.01 T174 B16 d to freezeAt riskMeasured
DAO Archive #1loaof-ayaaa-aaaaq-aae2a-caiArchive11.37 T9.26 B~3.3 yHealthyMeasured