From e964a97d12e7554435e364a59f68363c13667b33 Mon Sep 17 00:00:00 2001 From: Raymond Khalife Date: Wed, 24 Jun 2026 19:13:57 -0400 Subject: [PATCH] fix: clarify consequences of canister delete --- docs/guides/canister-management/lifecycle.mdx | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) diff --git a/docs/guides/canister-management/lifecycle.mdx b/docs/guides/canister-management/lifecycle.mdx index 07d7454c..885ba169 100644 --- a/docs/guides/canister-management/lifecycle.mdx +++ b/docs/guides/canister-management/lifecycle.mdx @@ -264,6 +264,8 @@ This is useful during development when you want a clean slate. The canister ID i Deleting permanently removes a canister from the network. The canister ID cannot be reused. +> Note: Canisters are like real estate on the IC. Creating them costs cycles. Instead of deleting a canister, consider reusing it in a different project. Check the [cli reference](https://cli.internetcomputer.org/1.0/concepts/project-model/#canister-ids) for more information. + 1. Stop the canister first: ```bash @@ -276,7 +278,7 @@ icp canister stop my-canister -e ic icp canister delete my-canister -e ic ``` -Remaining cycles are refunded to the controller who made the delete request. +> **Warning** The remaining cycles in the canister are lost, see [github issue](https://github.com/dfinity/icp-cli/issues/431). ## Migrate a canister between subnets