ICPWatch
Get alerts

ICX Swap Healthy

l4gz4-miaaa-aaaaq-aaeza-cai
Get alerts
Cycle balance
6.37 T
Measured
Burn per day
38.5 B
observed from our readings
0.4 M/s · 1.61 B/hr · 270 B/wk · 1.16 T/mo
Runway
~162 d
freezes around Apr 16, 2027
Projected deletion
May 16, 2027
in 192 d if nothing changes
Run status
running
probed 42 min ago
Freezing threshold
140 B
30 days of idle burn
Idle burn
4.67 B / day
reported by controller
Memory
30.4 MiB
measured SNS root canister statusRole: Swap · 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 6.37 T, idle burn 4.67 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)
ff78835cb23f70fa770c07d9b4be746cb936f55b1e48bb16ee3d0b9bd2f9e3f8
Memo (required)
1347768404 ("TPUP" as a number)
Amount
1.0632 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

f3c9cd2a503f3136c91f1d44c5b4bac2d5f15a7d347731aaff03e5fa80df8c48
Subnet x33ed-h457x...gae

Upgrade and controller history

checked management canister canister_info

Module upgraded

dad7d70471...67bdd0 → f3c9cd2a50...df8c48

· by canister jpz24-eqaaa...cai · version 2,690,228

Module upgraded

ef16e47eed...9fc243 → dad7d70471...67bdd0

· by canister jpz24-eqaaa...cai · version 1,349,226

Module upgraded

65e7d78985...d99381 → ef16e47eed...9fc243

· by canister jpz24-eqaaa...cai · version 1,156,764

Module upgraded

eeaa883855...637497 → 65e7d78985...d99381

· by canister jpz24-eqaaa...cai · version 935,223

Module upgraded

ca1fca5a97...d1e131 → eeaa883855...637497

· by canister jpz24-eqaaa...cai · version 643,744

Module upgraded

9289cf5b79...a515f7 → ca1fca5a97...d1e131

· by canister jpz24-eqaaa...cai · version 316,551

Controllers changed

- qaa6y-5yaaa-aaaaa-aaafa-cai
· by canister qaa6y-5yaaa...cai · version 3

Controllers changed

+ jpz24-eqaaa-aaaaq-aaexq-cai
· by canister qaa6y-5yaaa...cai · version 2

Code installed

earlier module not on record → 9289cf5b79...a515f7

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

Canister created

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

Incidents

Module upgraded: ICX Swap

Module hash went from dad7d70471...67bdd0 to f3c9cd2a50...df8c48, by canister jpz24-eqaaa-aaaaq-aaexq-cai.

· fired once per incident

Same token group

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