ICPWatch
Get alerts

PIKO Ledger Healthy

56aad-fiaaa-aaaaj-qsefa-cai
Get alerts
Cycle balance
68.28 T
Measured
Burn per day
60.7 B
observed from our readings
0.7 M/s · 2.53 B/hr · 425 B/wk · 1.82 T/mo
Runway
~3.0 y
freezes around Nov 5, 2029
Projected deletion
Dec 5, 2029
in 3.1 y if nothing changes
Run status
running
probed 9 min ago
Freezing threshold
n/a
not readable
Idle burn
n/a
Memory
51.6 MiB
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 68.28 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)
dce68610cd6d13cd20ecd2f826811bc72681109094ae5aa0a967d57b3599db34
Memo (required)
1347768404 ("TPUP" as a number)
Amount
1.0813 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

ba3f17bacfe92e418efc7b348954a4ad97716164c447cfe72313fc69e7d2a31a
Subnet jtdsg-3h6gi...nqe

Upgrade and controller history

checked management canister canister_info

Upgraded with the same module

ba3f17bacf...d2a31a → ba3f17bacf...d2a31a

· by principal yz6zu-pruo6...sae · version 33

Code installed

earlier module not on record → ba3f17bacf...d2a31a

· by principal yz6zu-pruo6...sae · version 1

Canister created

yz6zu-pruo6-qm4aj-k5fl5-pxe2d-ej2ew-avucl-usfze-mohit-3pt7n-sae
· by canister rkp4c-7iaaa...cai · version 0

Incidents

Resolved: PIKO Ledger

Burning 0.07 T per day, 19.6x its own 11-day baseline of 0.00 T. Busy canisters do not trip this, spikes do.

· fired once per incident · open for 2 d

Resolved: PIKO Ledger

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

· fired once per incident · open for 4 d

Resolved: PIKO Ledger

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

· fired once per incident · open for 16 h

Resolved: PIKO Ledger

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

· fired once per incident · open for 8 h

Resolved: PIKO Ledger

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

· fired once per incident · open for 19 h

Resolved: PIKO Ledger

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

· fired once per incident · open for 3 h