ICPWatch
Get alerts

DAO Ledger Healthy

ixqp7-kqaaa-aaaaq-aaetq-cai
Cycle balance
3.07 T
Measured
Burn per day
5.96 B
idle burn reported by controller
0.1 M/s · 248 M/hr · 41.7 B/wk · 179 B/mo
Runway
~484 d
freezes around Mar 4, 2028
Projected deletion
Apr 3, 2028
in 514 d if nothing changes
Run status
running
probed 9 min ago
Freezing threshold
179 B
30 days of idle burn
Idle burn
5.96 B / day
reported by controller
Memory
52.1 MiB
measured canister /metrics endpointRole: Ledger · 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 3.07 T, idle burn 5.96 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)
b751e607d2ce223a7197a72ff2e755838bcf2ff32de03c154e3f14b59c4bf519
Memo (required)
1347768404 ("TPUP" as a number)
Amount
0.0977 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

71c27c5dc10034a1175296892b37827df0265d0ae072f5c59e99b8a1f6c45c76

Upgrade and controller history

checked management canister canister_info

Module upgraded

24e6b0b09b...e62bd1 → 71c27c5dc1...c45c76

· by canister izscx-raaaa...cai · version 19,039,134

Module upgraded

da09eb0739...35f06e → 24e6b0b09b...e62bd1

· by canister izscx-raaaa...cai · version 9,303,550

Module upgraded

a35575419a...506952 → da09eb0739...35f06e

· by canister izscx-raaaa...cai · version 7,827,042

Module upgraded

91f5c6d260...ff807b → a35575419a...506952

· by canister izscx-raaaa...cai · version 7,826,808

Module upgraded

eb252f63b8...a79e5b → 91f5c6d260...ff807b

· by canister izscx-raaaa...cai · version 7,822,798

Module upgraded

dca85fc694...187503 → eb252f63b8...a79e5b

· by canister izscx-raaaa...cai · version 3,672,061

Module upgraded

3b03d1bb11...9d5822 → dca85fc694...187503

· by canister izscx-raaaa...cai · version 3,671,868

Controllers changed

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

Controllers changed

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

Code installed

earlier module not on record → 3b03d1bb11...9d5822

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

Canister created

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

Incidents

Burn-rate anomaly: DAO Ledger

Burning 1.21 T per day, well above its own 31-day baseline of 0.00 T. Busy canisters do not trip this, spikes do.

· fired once per incident

Resolved: DAO Ledger

Burning 1.35 T per day, well above its own 31-day baseline of 0.00 T. Busy canisters do not trip this, spikes do.

· fired once per incident · open for 32 h

Resolved: DAO Ledger

2.70 T left, about 2 days until it freezes at the current burn of 1.24 T per day.

· fired once per incident · open for 14 h

Resolved: DAO Ledger

Burning 1.21 T per day, well above its own 31-day baseline of 0.00 T. Busy canisters do not trip this, spikes do.

· fired once per incident · open for 33 h

Resolved: DAO Ledger

2.75 T left, about 2 days until it freezes at the current burn of 1.21 T per day.

· fired once per incident · open for 15 h

Resolved: DAO Ledger

Burning 1.15 T per day, well above its own 31-day baseline of 0.00 T. Busy canisters do not trip this, spikes do.

· fired once per incident · open for 35 h

Resolved: DAO Ledger

2.80 T left, about 2 days until it freezes at the current burn of 1.17 T per day.

· fired once per incident · open for 17 h

Resolved: DAO Ledger

Burning 1.17 T per day, well above its own 31-day baseline of 0.00 T. Busy canisters do not trip this, spikes do.

· fired once per incident · open for 35 h

Resolved: DAO Ledger

2.80 T left, about 2 days until it freezes at the current burn of 1.17 T per day.

· fired once per incident · open for 17 h

Resolved: DAO Ledger

Burning 1.14 T per day, well above its own 31-day baseline of 0.00 T. Busy canisters do not trip this, spikes do.

· fired once per incident · open for 35 h

Same token group

CanisterTypeCyclesBurn / dayRunwayStatusData
DAO Ledgerixqp7-kqaaa-aaaaq-aaetq-caiLedger3.07 T5.96 B~484 dHealthyMeasured
DAO Indexj57nf-iaaaa-aaaaq-aaeuq-caiIndex3.90 T5.89 B~632 dHealthyMeasured
DAO Archive #1loaof-ayaaa-aaaaq-aae2a-caiArchive11.38 T9.34 B~3.3 yHealthyMeasured