Difference between revisions of "Deploy a Permissioned Subnet on Mainnet"
Jump to navigation
Jump to search
| (One intermediate revision by the same user not shown) | |||
| Line 3: | Line 3: | ||
| − | Permissioned Subnet. As such, you must specify which [[P-Chain]] addresses can control the Subnet. These addresses are known as <code>[[Control Keys]]</code>. | + | Permissioned [[Subnet]]. As such, you must specify which [[P-Chain]] addresses can control the Subnet. These addresses are known as <code>[[Control Keys]]</code>. |
== See also == | == See also == | ||
| + | * {{subnet-cli}} | ||
* {{avax}} | * {{avax}} | ||
Latest revision as of 15:16, 20 April 2023
Permissioned Subnet. As such, you must specify which P-Chain addresses can control the Subnet. These addresses are known as Control Keys.
See also[edit]
- Avalanche subnets:
subnet-cli [ create | status | wizard ] - Avalanche, AVAX token, Ava Labs, Avalanche subnets, SING token,
avalanche-cli, subnet-cli, avalanchego, AvalancheJS, Avalanche Network Runner, Fuji, 9650, 9651,/ext/, Exchange Chain (X-Chain), Contract Chain (C-Chain), Platform Chain (P-Chain), Avalanche Wallet, Explorers, Avalanche Cortina, Subnet EVM, apm, HyperSDK, Multiverse, Blockpay.mx, Core.app, BitNote
Advertising:
