-
Notifications
You must be signed in to change notification settings - Fork 3
docs: add guide for deploying to specific subnets #314
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
|
|
||
| By default, `icp deploy` automatically selects a subnet for your canisters. You might want to target a specific subnet when: | ||
|
|
||
| - **Verified Application Subnets** — Deploy to subnets with additional security guarantees |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Verified application subnets are a retired concept. They still exist in code, but today are equal to standard app subnnets
|
|
||
| - **Verified Application Subnets** — Deploy to subnets with additional security guarantees | ||
| - **Geographic Requirements** — Target subnets in specific regions (e.g., European subnets for data residency) | ||
| - **Specialized Subnets** — Use subnets with specific capabilities (Bitcoin, Fiduciary, etc.) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Every subnet supports BTC, and fiduciary is not an understandable capability. This should explain e.g. fiduciary or eu/eea or point to an explanation
| | Type | Description | | ||
| |------|-------------| | ||
| | Application | General-purpose subnets for most canisters | | ||
| | Verified Application | Subnets with additional security measures for high-value applications | |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
| | Verified Application | Subnets with additional security measures for high-value applications | |
| | Application | General-purpose subnets for most canisters | | ||
| | Verified Application | Subnets with additional security measures for high-value applications | | ||
| | Fiduciary | Handles sensitive operations like threshold ECDSA signatures | | ||
| | Bitcoin | Provides Bitcoin integration capabilities | |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
| | Bitcoin | Provides Bitcoin integration capabilities | |
| | Verified Application | Subnets with additional security measures for high-value applications | | ||
| | Fiduciary | Handles sensitive operations like threshold ECDSA signatures | | ||
| | Bitcoin | Provides Bitcoin integration capabilities | | ||
| | System/NNS | Reserved for system canisters (not available for user deployment) | |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
| | System/NNS | Reserved for system canisters (not available for user deployment) | | |
| | System | Reserved for system canisters (not available for user deployment) | |
only called system. The dashboard is the only place that also calls them NNS
| - application | ||
| ``` | ||
|
|
||
| Available local subnet types: `application`, `system`, `verified-application`, `bitcoin`, `fiduciary`, `nns`, `sns` |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Not sure about the list, I thought only application and system are supported
Summary
Adds a new guide for deploying canisters to specific subnets on the Internet Computer.
--subnetflag foricp deployandicp canister create