ICPWatch
Get alerts

ND64 Ledger Healthy

esbhr-giaaa-aaaam-ac4jq-cai
Get alerts
Cycle balance
1.78 T
Measured
Burn per day
16.0 B
observed from our readings
0.2 M/s · 666 M/hr · 112 B/wk · 480 B/mo
Runway
~82 d
freezes around Jan 26, 2027
Projected deletion
Feb 25, 2027
in 112 d if nothing changes
Run status
running
probed 2 min ago
Freezing threshold
n/a
not readable
Idle burn
n/a
Memory
n/a
measured canister /metrics endpointRole: Ledger · discovered via dex:ICPSwap on Sep 21, 2026

Community funding

Fund this canister

no community top-ups yet

This canister is running with a healthy balance. Balance 1.78 T.

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)
e3c50759c9a213fe62660c96dc09c3913b9d8cceaa155bbf4ee23d9572a1c33d
Memo (required)
1347768404 ("TPUP" as a number)
Amount
0.4410 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

0bdcf000f840f93c7f7b115b6d245f6b6c12135766d6a1bcea5fbdc56a8bc3b6
Subnet 4ecnw-byqwz...sqe

Upgrade and controller history

checked management canister canister_info

Code installed

earlier module not on record → 0bdcf000f8...8bc3b6

· by canister 24gqi-uyaaa...cai · version 1

Canister created

24gqi-uyaaa-aaaam-ab5gq-cai
· by canister 24gqi-uyaaa...cai · version 0

Incidents

Resolved: ND64 Ledger

2.50 T left, about 9 days until it freezes at the current burn of 0.06 T per day.

· fired once per incident · open for 21 h

Resolved: ND64 Ledger

Burning 0.11 T per day, 4.1x its own 17-day baseline of 0.03 T. Busy canisters do not trip this, spikes do.

· fired once per incident · open for 22 h