ICPWatch
Get alerts

FUNNAI Ledger Healthy

vpyot-zqaaa-aaaaa-qavaq-cai
Cycle balance
200.3 T
Measured
Burn per day
194 B
observed from our readings
2.2 M/s · 8.08 B/hr · 1.36 T/wk · 5.82 T/mo
Runway
~2.7 y
freezes around Aug 4, 2029
Projected deletion
Sep 3, 2029
in 2.8 y if nothing changes
Run status
running
probed 5 min ago
Freezing threshold
n/a
not readable
Idle burn
n/a
Memory
52.4 MiB
measured canister /metrics endpointRole: Ledger · discovered via seed on Sep 21, 2026

Community funding

Fund this canister

no community top-ups yet

This canister is running with a healthy balance. Balance 200.3 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)
c16b0c697e0286b8c98ce7477611111f403777e4e332cadf3a6c0ffa298fa800
Memo (required)
1347768404 ("TPUP" as a number)
Amount
3.2975 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

Module

3b03d1bb1145edbcd11101ab2788517bc0f427c3bd7b342b9e3e7f42e29d5822

Upgrade and controller history

checked management canister canister_info

Controllers changed

· by principal chfec-vmrjj...2ae · version 7,635,399

Controllers changed

· by principal chfec-vmrjj...2ae · version 7,532,378

Controllers changed

· by principal cda4n-7jjpo...yqe · version 4,401,922

Controllers changed

· by canister r7inp-6aaaa...cai · version 3,866,788

Controllers changed

· by principal chfec-vmrjj...2ae · version 3,355,754

Controllers changed

· by principal cda4n-7jjpo...yqe · version 169,978

Upgraded with the same module

3b03d1bb11...9d5822 → 3b03d1bb11...9d5822

· by principal cda4n-7jjpo...yqe · version 37,493

Upgraded with the same module

3b03d1bb11...9d5822 → 3b03d1bb11...9d5822

· by principal cda4n-7jjpo...yqe · version 31,692

Controllers changed

· by principal chfec-vmrjj...2ae · version 3

Controllers changed

· by principal cda4n-7jjpo...yqe · version 2

Code installed

earlier module not on record → 3b03d1bb11...9d5822

· by principal cda4n-7jjpo...yqe · version 1

Canister created

· by canister rkp4c-7iaaa...cai · version 0

Incidents

Same token group

CanisterTypeCyclesBurn / dayRunwayStatusData
FUNNAI Ledgervpyot-zqaaa-aaaaa-qavaq-caiLedger200.3 T194 B~2.7 yHealthyMeasured
FUNNAI Archive #16vmdw-wyaaa-aaaaa-qbjca-caiArchiveunknownn/acode and state goneUninstalledProbed