RUGGY Ledger Healthy
0.1 M/s · 524 M/hr · 88.0 B/wk · 377 B/mo
Community funding
Fund this canister
no community top-ups yetThis canister is running with a healthy balance. Balance 9.24 T.
Keep alive: the minimum that prevents deletion while keeping the canister frozen and cheap. It stays below its freezing threshold on purpose.
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 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.
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
Module
Upgrade and controller history
checked management canister canister_infoCode installed
earlier module not on record → b60487873e...807d4b
· by canister h7uwa-hyaaa...cai · version 1Incidents
Resolved: RUGGY Ledger
Burning 0.11 T per day, 3.6x its own 31-day baseline of 0.03 T. Busy canisters do not trip this, spikes do.
· fired once per incident · open for 33 hResolved: RUGGY Ledger
Burning 0.10 T per day, 3.9x its own 30-day baseline of 0.03 T. Busy canisters do not trip this, spikes do.
· fired once per incident · open for 35 hResolved: RUGGY Ledger
Burning 0.11 T per day, 5.7x its own 24-day baseline of 0.02 T. Busy canisters do not trip this, spikes do.
· fired once per incident · open for 6 dResolved: RUGGY Ledger
1.85 T left, about 13 days until it freezes at the current burn of 0.04 T per day.
· fired once per incident · open for 11 dResolved: RUGGY Ledger
Burning 0.07 T per day, 3.6x its own 24-day baseline of 0.02 T. Busy canisters do not trip this, spikes do.
· fired once per incident · open for 7 hResolved: RUGGY Ledger
Burning 0.15 T per day, 7.4x its own 23-day baseline of 0.02 T. Busy canisters do not trip this, spikes do.
· fired once per incident · open for 3 hResolved: RUGGY Ledger
Burning 0.07 T per day, 3.6x its own 21-day baseline of 0.02 T. Busy canisters do not trip this, spikes do.
· fired once per incident · open for 11 hResolved: RUGGY Ledger
Burning 0.08 T per day, 3.8x its own 21-day baseline of 0.02 T. Busy canisters do not trip this, spikes do.
· fired once per incident · open for 6 hResolved: RUGGY Ledger
Burning 0.08 T per day, 4.0x its own 20-day baseline of 0.02 T. Busy canisters do not trip this, spikes do.
· fired once per incident · open for 8 hResolved: RUGGY Ledger
Burning 0.09 T per day, 4.4x its own 13-day baseline of 0.02 T. Busy canisters do not trip this, spikes do.
· fired once per incident · open for 6 dSame token group
| Canister | Type | Cycles | Burn / day | Runway | Status | Data |
|---|---|---|---|---|---|---|
| RUGGY Ledgericaf7-3aaaa-aaaam-qcx3q-cai | Ledger | 9.24 T | 12.6 B | ~705 d | Healthy | Measured |
| RUGGY Archive #1lfa3d-oyaaa-aaaam-qdb4q-cai | Archive | 4.02 T | 1.94 B | ~5.6 y | Healthy | Measured |