ICPWatch
Get alerts

BITTYICP Ledger Healthy

qroj6-lyaaa-aaaam-qeqta-cai
Get alerts
Cycle balance
26.39 T
Measured
Burn per day
13.1 B
observed from our readings
0.2 M/s · 547 M/hr · 91.9 B/wk · 394 B/mo
Runway
~5.4 y
freezes around Apr 7, 2032
Projected deletion
May 7, 2032
in 5.5 y if nothing changes
Run status
running
probed 60 s 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 26.39 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)
7c43fbe4879dc26d2179abfe3486aa088e850db51359a4ce03b03c81480d5a02
Memo (required)
1347768404 ("TPUP" as a number)
Amount
0.2995 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

b60487873e58beda2fe7a02cfdf3c741bc48a30d3485aeec8a69a991d7807d4b
Subnet yinp6-35cfo...jqe

Upgrade and controller history

checked management canister canister_info

Code installed

earlier module not on record → b60487873e...807d4b

· by canister h7uwa-hyaaa...cai · version 1

Canister created

h7uwa-hyaaa-aaaam-qbgvq-cai
· by canister h7uwa-hyaaa...cai · version 0

Incidents

Resolved: BITTYICP Ledger

Burning 0.07 T per day, 4.1x its own 31-day baseline of 0.02 T. Busy canisters do not trip this, spikes do.

· fired once per incident · open for 4 h

Resolved: BITTYICP Ledger

Burning 0.07 T per day, 3.5x its own 29-day baseline of 0.02 T. Busy canisters do not trip this, spikes do.

· fired once per incident · open for 6 h

Resolved: BITTYICP Ledger

Burning 0.09 T per day, 3.7x its own 8-day baseline of 0.02 T. Busy canisters do not trip this, spikes do.

· fired once per incident · open for 6 h

Resolved: BITTYICP Ledger

Burning 0.07 T per day, 3.2x its own 7-day baseline of 0.02 T. Busy canisters do not trip this, spikes do.

· fired once per incident · open for 7 h

Same token group

CanisterTypeCyclesBurn / dayRunwayStatusData
BITTYICP Ledgerqroj6-lyaaa-aaaam-qeqta-caiLedger26.39 T13.1 B~5.4 yHealthyMeasured
BITTYICP Archive #1fy5jx-yiaaa-aaaam-qetca-caiArchive341 B1.31 B~231 dHealthyMeasured