ICPWatch
Get alerts

TACO DAO Dapp #16 Healthy

vzzhe-5aaaa-aaaad-qigla-cai
Cycle balance
0.00 T
Measured
Burn per day
n/a
needs more readings
Runway
50+ y
Projected deletion
n/a
Run status
running
probed 11 min ago
Freezing threshold
0.00 T
30 days of idle burn
Idle burn
0.00 T / day
reported by controller
Memory
0 B
measured SNS root canister statusRole: Dapp · 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 0.00 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 pays no cycles for storage or execution that we can observe (system subnet), so it does not need a top-up.
Top-up account (ICP account id)
5a44957cd009fae382e38ca7e52bb3044d177f373f76dec2aee03af64bc0bd78
Memo (required)
1347768404 ("TPUP" as a number)
Amount
n/a

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

Upgrade and controller history

checked management canister canister_info
The IC has no recorded changes for this canister.

Incidents

Frozen: TACO DAO Dapp #16

The canister is rejecting calls because its balance is below the freezing threshold.

· fired once per incident

Resolved: TACO DAO Dapp #16

The canister is rejecting calls because its balance is below the freezing threshold.

· fired once per incident · open for 10 d

Resolved: TACO DAO Dapp #16

The canister is rejecting calls because its balance is below the freezing threshold.

· fired once per incident · open for 8 h

Resolved: TACO DAO Dapp #16

The canister is rejecting calls because its balance is below the freezing threshold.

· fired once per incident · open for 8 d

Resolved: TACO DAO Dapp #16

The canister is rejecting calls because its balance is below the freezing threshold.

· fired once per incident · open for 5 d

Resolved: TACO DAO Dapp #16

The canister is rejecting calls because its balance is below the freezing threshold.

· fired once per incident · open for 5 d

Resolved: TACO DAO Dapp #16

The canister is rejecting calls because its balance is below the freezing threshold.

· fired once per incident · open for 11 d

Resolved: TACO DAO Dapp #16

The canister is rejecting calls because its balance is below the freezing threshold.

· fired once per incident · open for 6 h

Resolved: TACO DAO Dapp #16

The canister is rejecting calls because its balance is below the freezing threshold.

· fired once per incident · open for 20 h

Resolved: TACO DAO Dapp #16

The canister is rejecting calls because its balance is below the freezing threshold.

· fired once per incident · open for 10 min

Same token group

CanisterTypeCyclesBurn / dayRunwayStatusData
TACO Ledgerkknbx-zyaaa-aaaaq-aae4a-caiLedger12.01 T359 B33 d to freezeAt riskMeasured
TACO Indexkepm7-ciaaa-aaaaq-aae5a-caiIndex14.10 T590 B24 d to freezeAt riskMeasured
TACO Archive #1kdokl-pqaaa-aaaaq-aae5q-caiArchive10.94 T10.4 B~2.8 yHealthyMeasured