ICPWatch
Get alerts

ICX Archive #1 Healthy

ljbir-naaaa-aaaaq-aae2q-cai
Get alerts
Cycle balance
10.04 T
Measured
Burn per day
9.00 B
observed from our readings
0.1 M/s · 375 M/hr · 63.0 B/wk · 270 B/mo
Runway
~3.0 y
freezes around Nov 12, 2029
Projected deletion
Dec 12, 2029
in 3.1 y if nothing changes
Run status
running
probed 9 min ago
Freezing threshold
109 B
30 days of idle burn
Idle burn
3.65 B / day
reported by controller
Memory
19.6 MiB
measured canister /metrics endpointRole: Archive · 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 10.04 T, idle burn 3.65 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)
1304ec037a8fa2de8ee34d3e4307b84bca7df2d5b16c366d99d40a991f54d036
Memo (required)
1347768404 ("TPUP" as a number)
Amount
0.1936 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

f7f48f402a128cbd18dc7734c7f149f2814c8181766f39897a66d514d47ccf11
Subnet x33ed-h457x...gae

Upgrade and controller history

checked management canister canister_info

Module upgraded

cd78959e48...031f93 → f7f48f402a...7ccf11

· by canister jpz24-eqaaa...cai · version 238,702

Module upgraded

186697235c...ae21a9 → cd78959e48...031f93

· by canister jpz24-eqaaa...cai · version 231,783

Module upgraded

cb3f2ecc54...b69e1c → 186697235c...ae21a9

· by canister jpz24-eqaaa...cai · version 210,839

Module upgraded

50adf54483...e55fae → cb3f2ecc54...b69e1c

· by canister jpz24-eqaaa...cai · version 163,849

Module upgraded

bd21de14ad...4f4d3d → 50adf54483...e55fae

· by canister jpz24-eqaaa...cai · version 140,869

Module upgraded

2962d99c14...0f9744 → bd21de14ad...4f4d3d

· by canister jpz24-eqaaa...cai · version 997

Module upgraded

28955c4f27...da83de → 2962d99c14...0f9744

· by canister jpz24-eqaaa...cai · version 193

Module upgraded

9bb1d4c401...d59d4a → 28955c4f27...da83de

· by canister jpz24-eqaaa...cai · version 176

Controllers changed

+ jpz24-eqaaa-aaaaq-aaexq-cai
- lvfsa-2aaaa-aaaaq-aaeyq-cai
· by canister lvfsa-2aaaa...cai · version 2

Code installed

earlier module not on record → 9bb1d4c401...d59d4a

· by canister lvfsa-2aaaa...cai · version 1

Canister created

lvfsa-2aaaa-aaaaq-aaeyq-cai
· by canister lvfsa-2aaaa...cai · version 0

Same token group

CanisterTypeCyclesBurn / dayRunwayStatusData
ICX Ledgerlvfsa-2aaaa-aaaaq-aaeyq-caiLedger17.92 T267 B~66 dHealthyMeasured
ICX Indexl3h7i-bqaaa-aaaaq-aaezq-caiIndex19.28 T558 B34 d to freezeAt riskMeasured
ICX Archive #1ljbir-naaaa-aaaaq-aae2q-caiArchive10.04 T9.00 B~3.0 yHealthyMeasured