From 031b06cdad7839999adc39839398beac1fc3abd5 Mon Sep 17 00:00:00 2001 From: Raymond Sukanto Date: Tue, 30 Jul 2024 12:05:07 -0400 Subject: [PATCH 1/6] remove elastic docs --- .../subnet/elastic/elastic-parameters.md | 310 ------------------ .../elastic/transform-to-elastic-subnet.md | 110 ------- 2 files changed, 420 deletions(-) delete mode 100644 docs/build/subnet/elastic/elastic-parameters.md delete mode 100644 docs/build/subnet/elastic/transform-to-elastic-subnet.md diff --git a/docs/build/subnet/elastic/elastic-parameters.md b/docs/build/subnet/elastic/elastic-parameters.md deleted file mode 100644 index 7d0fc699613..00000000000 --- a/docs/build/subnet/elastic/elastic-parameters.md +++ /dev/null @@ -1,310 +0,0 @@ ---- -tags: [Build, Subnets] -description: This reference describes the structural parameters of an Elastic (Permissionless) Subnet and illustrates the constraints they must satisfy. -sidebar_label: Parameters -pagination_label: Elastic Subnets Parameters -sidebar_position: 1 ---- - -# Elastic Subnets Parameters - -Avalanche Permissioned Subnets can be turned into Elastic Subnets via the -[`TransformSubnetTx`](/reference/standards/guides/banff-changes.md#transformsubnettx) transaction. -`TransformSubnetTx` specifies a set of structural parameters for the Elastic Subnet. -This reference describes these structural parameters and -illustrates the constraints they must satisfy. - -## Elastic Subnet Parameters - -### `Subnet` - -`Subnet` has type `ids.ID` and it's the Subnet ID. -`Subnet` is the ID of the `CreateSubnetTx` transaction that created the Subnet in the first place. -The following constraints apply: - -- `Subnet` must be different from `PrimaryNetworkID`. - -### `AssetID` - -`AssetID` has type `ids.ID` and it's the ID of the asset to use when staking on the Subnet. -The following constraints apply: - -- `AssetID` must not be the `Empty ID`. -- `AssetID` must not be `AVAX ID`, the Primary Network asset. - -### `InitialSupply` - -`InitialSupply` has type `uint64` and it's the initial amount of `AssetID` -transferred in the Elastic Subnet upon its transformation. Such amount is -available for distributing staking rewards. The following constraints apply: - -- `InitialSupply` must be larger than zero. - -### `MaximumSupply` - -`MaximumSupply` has type `uint64` and it's the maximum amount of `AssetID` that -Subnet has available for staking and rewards at any time. The following constraints apply: - -- `MaximumSupply` must be larger or equal to `InitialSupply`. - -A Subnet supply can vary in time but it should be no larger than the configured -maximum at any point in time, including at Subnet creation. - -### `MinConsumptionRate` - -`MinConsumptionRate` has type `uint64` and it's the minimal rate a validator can earn if the -`UptimeRequirement` is satisfied. If `StakingPeriod` == `MinStakeDuration`, the -validator will earn the `MinConsumptionRate`. -You can find more details about it in the [Reward Formula section](#reward-formula). -The following constraints apply: - -- `MinConsumptionRate` must be smaller or equal to `PercentDenominator`. - -See [Notes on Percentages](#notes-on-percentages) section to understand `PercentDenominator` role. - -### `MaxConsumptionRate` - -`MaxConsumptionRate` has type `uint64` and it's the maximal rate a validator can earn if the -`UptimeRequirement` is satisfied. If `StakingPeriod` == `MaxStakeDuration` == `MintingPeriod`, the -validator will earn the `MaxConsumptionRate`. -You can find more details about it in the [Reward Formula section](#reward-formula). -The following constraints apply: - -- `MaxConsumptionRate` must be larger or equal to `MinConsumptionRate`. -- `MaxConsumptionRate` must be smaller or equal to `PercentDenominator`. - -See [Notes on Percentages](#notes-on-percentages) section to understand `PercentDenominator` role. - -### `MinValidatorStake` - -`MinValidatorStake` has type `uint64` and it's the minimum amount of funds required to become a validator. -The following constraints apply: - -- `MinValidatorStake` must be larger than zero -- `MinValidatorStake` must be smaller or equal to `InitialSupply` - -### `MaxValidatorStake` - -`MaxValidatorStake` has type `uint64` and it's the maximum amount of funds a single -validator can be allocated, including delegated funds. -The following constraints apply: - -- `MaxValidatorStake` must be larger or equal to `MinValidatorStake` -- `MaxValidatorStake` must be smaller or equal to `MaximumSupply` - -### `MinStakeDuration` - -`MinStakeDuration` has type `uint32` and it's the minimum number of seconds a staker can stake for. -The following constraints apply: - -- `MinStakeDuration` must be larger than zero. - -### `MaxStakeDuration` - -`MaxStakeDuration` has type `uint32` and it's the maximum number of seconds a staker can stake for. -The following constraints apply: - -- `MaxStakeDuration` must be larger or equal to `MinStakeDuration`. -- `MaxStakeDuration` must be smaller or equal to `GlobalMaxStakeDuration`. - -`GlobalMaxStakeDuration` is defined in genesis and applies to both the Primary Network and all -Subnets. - - - - -Its Mainnet value is $365 \times 24 \times time.Hour$. - - - - -### `MinDelegationFee` - -`MinDelegationFee` has type `uint32` and it's the minimum fee rate a delegator -must pay to its validator for delegating. `MinDelegationFee` is a percentage; the -actual fee is calculated multiplying the fee rate for the delegator reward. -The following constraints apply: - -- `MinDelegationFee` must be smaller or equal to `PercentDenominator`. - -The `MinDelegationFee` rate applies to Primary Network as well. Its Mainnet value is $2\%$. - -### `MinDelegatorStake` - -`MinDelegatorStake` has type `uint64` and it's the minimum amount of funds required to become a delegator. -The following constraints apply: - -- `MinDelegatorStake` must be larger than zero. - -### `MaxValidatorWeightFactor` - -`MaxValidatorWeightFactor` has type `uint8` and it's the factor which calculates -the maximum amount of delegation a validator can receive. A value of 1 -effectively disables delegation. You can find more details about it in the -[Delegators Weight Checks section](#delegators-weight-checks). -The following constraints apply: - -- `MaxValidatorWeightFactor` must be larger than zero. - -### `UptimeRequirement` - -`UptimeRequirement` has type `uint32` and it's the minimum percentage of its -staking time that a validator must be online and responsive for to receive a -reward. -The following constraints apply: - -- `UptimeRequirement` must be smaller or equal `PercentDenominator`. - -See [Notes on Percentages](#notes-on-percentages) section to understand `PercentDenominator` role. - -## Reward Formula - -Consider an Elastic Subnet validator which stakes a $Stake$ amount `AssetID` for $StakingPeriod$ seconds. - -Assume that at the start of the staking period there is a $Supply$ amount of `AssetID` in the Subnet. -The maximum amount of Subnet asset is $MaximumSupply$ `AssetID`. - -Then at the end of its staking period, a responsive Elastic Subnet validator -receives a reward calculated as follows: - - - - -$$ -Reward = \left(MaximumSupply - Supply \right) \times \frac{Stake}{Supply} \times \frac{Staking Period}{Minting Period} \times EffectiveConsumptionRate -$$ - -where - -$$ -MaximumSupply - Supply = \text{the number of tokens left to emit in the subnet} -$$ - -$$ -\frac{Stake}{Supply} = \text{the individual's stake as a percentage of all available tokens in the network} -$$ - -$$ -\frac{StakingPeriod}{MintingPeriod} = \text{time tokens are locked up divided by the $MintingPeriod$} -$$ - -$$ -\text{$MintingPeriod$ is one year as configured by the Primary Network).} -$$ - -$$ -EffectiveConsumptionRate = -$$ - -$$ -\frac{MinConsumptionRate}{PercentDenominator} \times \left(1- \frac{Staking Period}{Minting Period}\right) + \frac{MaxConsumptionRate}{PercentDenominator} \times \frac{Staking Period}{Minting Period} -$$ - - - - -Note that $StakingPeriod$ is the staker's entire staking period, not just the -staker's uptime, that is the aggregated time during which the staker has been -responsive. The uptime comes into play only to decide whether a staker should be -rewarded; to calculate the actual reward only the staking period duration is -taken into account. - -$EffectiveConsumptionRate$ is the rate at which the validator is rewarded based on $StakingPeriod$ selection. - -$MinConsumptionRate$ and $MaxConsumptionRate$ bound $EffectiveConsumptionRate$: - - - - -$$ -MinConsumptionRate \leq EffectiveConsumptionRate \leq MaxConsumptionRate -$$ - - - - -The larger $StakingPeriod$ is, the closer $EffectiveConsumptionRate$ is to $MaxConsumptionRate$. -The smaller $StakingPeriod$ is, the closer $EffectiveConsumptionRate$ is to $MinConsumptionRate$. - -A staker achieves the maximum reward for its stake if $StakingPeriod$ = $Minting Period$. -The reward is: - - - - -$$ -Max Reward = \left(MaximumSupply - Supply \right) \times \frac{Stake}{Supply} \times \frac{MaxConsumptionRate}{PercentDenominator} -$$ - - - - -Note that this formula is the same as the reward formula at the top of this section -because $EffectiveConsumptionRate$ = $MaxConsumptionRate$. - -The reward formula above is used in the Primary Network to calculate -stakers reward. For reference, you can find Primary network parameters in [the section below](#primary-network-parameters-on-mainnet). - -## Delegators Weight Checks - -There are bounds set of the maximum amount of delegators' stake that a validator can receive. - -The maximum weight $MaxWeight$ a validator $Validator$ can have is: - - - - -$$ - MaxWeight = \min(Validator.Weight \times MaxValidatorWeightFactor, MaxValidatorStake) -$$ - - - - -where $MaxValidatorWeightFactor$ and $MaxValidatorStake$ are the Elastic Subnet -Parameters described above. - -A delegator won't be added to a validator if the combination of their weights -and all other validator's delegators' weight is larger than $MaxWeight$. Note -that this must be true at any point in time. - - - -Note that setting $MaxValidatorWeightFactor$ to 1 disables delegation since the $MaxWeight = Validator.Weight$. - - - -## Notes on Percentages - -`PercentDenominator = 1_000_000` is the denominator used to calculate percentages. - -It allows you to specify percentages up to 4 digital positions. -To denominate your percentage in `PercentDenominator` just multiply it by `10_000`. -For example: - -- `100%` corresponds to `100 * 10_000 = 1_000_000` -- `1%` corresponds to `1* 10_000 = 10_000` -- `0.02%` corresponds to `0.002 * 10_000 = 200` -- `0.0007%` corresponds to `0.0007 * 10_000 = 7` - -## Primary Network Parameters on Mainnet - -An Elastic Subnet is free to pick any parameters affecting rewards, within the -constraints specified above. For reference we list below Primary Network -parameters on Mainnet: - -- `AssetID = Avax` -- `InitialSupply = 240_000_000 Avax` -- `MaximumSupply = 720_000_000 Avax`. -- `MinConsumptionRate = 0.10 * reward.PercentDenominator`. -- `MaxConsumptionRate = 0.12 * reward.PercentDenominator`. -- `Minting Period = 365 * 24 * time.Hour`. -- `MinValidatorStake = 2_000 Avax`. -- `MaxValidatorStake = 3_000_000 Avax`. -- `MinStakeDuration = 2 * 7 * 24 * time.Hour`. -- `MaxStakeDuration = 365 * 24 * time.Hour`. -- `MinDelegationFee = 20000`, that is `2%`. -- `MinDelegatorStake = 25 Avax`. -- `MaxValidatorWeightFactor = 5`. This is a platformVM parameter rather than a - genesis one, so it's shared across networks. -- `UptimeRequirement = 0.8`, that is `80%`. diff --git a/docs/build/subnet/elastic/transform-to-elastic-subnet.md b/docs/build/subnet/elastic/transform-to-elastic-subnet.md deleted file mode 100644 index d38c20a68a3..00000000000 --- a/docs/build/subnet/elastic/transform-to-elastic-subnet.md +++ /dev/null @@ -1,110 +0,0 @@ ---- -tags: [Build, Subnets] -description: This how-to guide focuses on taking an already created permissioned Subnet and transforming it to an elastic (or permissionless) Subnet. -sidebar_label: Make Subnet Permissionless -pagination_label: Transform a Permissioned Subnet into an Elastic Subnet -sidebar_position: 0 ---- - -# How to Transform a Permissioned Subnet into an Elastic Subnet - -Elastic Subnets are permissionless Subnets. More information can be found [here](/build/subnet/elastic/elastic-parameters.md). - -This how-to guide focuses on taking an already created permissioned Subnet and transforming it to an -elastic (or permissionless) Subnet. - -## Prerequisites - -- [Avalanche-CLI installed](/tooling/cli-guides/install-avalanche-cli.md) -- You have deployed a permissioned Subnet on [local](/build/subnet/deploy/local-subnet.md), on -[Fuji](/build/subnet/deploy/fuji-testnet-subnet.md) or on [Mainnet](/build/subnet/deploy/mainnet-subnet.md) - -## Getting Started - -In the following commands, make sure to substitute the name of your Subnet configuration for -``. - -To transform your permissioned Subnet into an Elastic Subnet (NOTE: this action is irreversible), run - -`avalanche subnet elastic ` - -and select the network that you want to transform the Subnet on. Alternatively, you can bypass this -prompt by providing the `--local`, `--fuji`, or `--mainnet` flag. - -Provide the name and the symbol for the permissionless Subnet's native token. You can also bypass -this prompt by providing the `--tokenName` and `--tokenSymbol` flags. - -Next, select the Elastic Subnet config. You can choose to use the default values detailed -[here](/build/subnet/elastic/elastic-parameters.md#primary-network-parameters-on-mainnet) -or customize the Elastic Subnet config. To bypass the prompt, you can use `--default` flag to use -the default Elastic Subnet config. - -The command may take a couple minutes to run. - -### Elastic Subnet Transformation on Fuji and Mainnet - -Elastic Subnet transformation on public network requires private key loaded into the tool, or a -connected ledger device. - -Both stored key usage and ledger usage are enabled on Fuji (see more on creating keys -[here](/build/subnet/deploy/fuji-testnet-subnet.md#private-key)) -while only ledger usage is enabled on Mainnet (see more on setting up your ledger -[here](/build/subnet/deploy/mainnet-subnet.md#setting-up-your-ledger)). - -To transform a permissioned Subnet into Elastic Subnet on public networks, users are required to -provide the keys that control the Subnet defined during the Subnet deployment process (more info on -keys in Fuji can be found -[here](/build/subnet/deploy/fuji-testnet-subnet.md#deploy-the-subnet), -while more info on ledger signing in Mainnet can be found -[here](/build/subnet/deploy/mainnet-subnet.md#deploy-the-subnet)). - -### Results - -If all works as expected, you then have the option to automatically transform all existing -permissioned validators to permissionless validators. - -You can also to skip automatic transformation at this point and choose to manually add -permissionless validators later. - -You can use the output details such as the Asset ID and Elastic Subnet ID to connect to and -interact with your Elastic Subnet. - -## Adding Permissionless Validators to Elastic Subnet - -If you are running this command on local network, you will need to first remove permissioned -validators (by running `avalanche subnet removeValidator `) so that you can have a list -of local nodes to choose from to be added as a permissionless validator in the Elastic Subnet. - -To add permissionless validators to an Elastic Subnet, run - -`avalanche subnet join --elastic` - -You will be prompted with which node you would like to add as a permissionless validator. You can -skip this prompt by using `--nodeID` flag. - -You will then be prompted with the amount of the Subnet native token that you like to stake in the -validator. Alternatively, you can bypass this prompt by providing the `--stake-amount` flag. Note -that choosing to add the maximum validator stake amount (defined during Elastic Subnet -transformation step above) means that you effectively disable delegation in your validator. - -Next, select when the validator will start validating and how long it will be validating for. You -can also bypass these prompts by using `--start-time` and `--staking-period` flags. - -## Adding Permissionless Delegator to a Permissionless Validator in Elastic Subnet - -To add permissionless delegators, run - -`avalanche subnet addPermissionlessDelegator ` - -You will be prompted with which Subnet validator you would like to delegate to. You can skip this -prompt by using `--nodeID` flag. - -You will then be prompted with the amount of the Subnet native token that you like to stake in the -validator. Alternatively, you can bypass this prompt by providing the `--stake-amount` flag. The -amount that can be delegated to a validator is detailed -[here](/build/subnet/elastic/elastic-parameters.md#delegators-weight-checks). - -Next, select when you want to start delegating and how long you want to delegate for. You can also -bypass these prompts by using `--start-time` and `--staking-period` flags. - - From f57e4e146c0dde795d296c90ed4e5602f5d06611 Mon Sep 17 00:00:00 2001 From: Raymond Sukanto Date: Tue, 30 Jul 2024 12:10:17 -0400 Subject: [PATCH 2/6] fix lint --- sidebars.json | 12 ------------ 1 file changed, 12 deletions(-) diff --git a/sidebars.json b/sidebars.json index a896197f95a..49c356ae9df 100644 --- a/sidebars.json +++ b/sidebars.json @@ -246,18 +246,6 @@ "type": "html", "value": "
" }, - { - "type": "html", - "value": " Elastic Subnets " - }, - { - "type": "autogenerated", - "dirName": "build/subnet/elastic" - }, - { - "type": "html", - "value": "
" - }, { "type": "html", "value": " Manage Subnets " From ce9491e793f2a3bfe2d46b636fd2edcb16b1335d Mon Sep 17 00:00:00 2001 From: Raymond Sukanto Date: Tue, 30 Jul 2024 12:12:24 -0400 Subject: [PATCH 3/6] fix lint --- static/_redirects | 2 -- 1 file changed, 2 deletions(-) diff --git a/static/_redirects b/static/_redirects index d0dc6c5e6e0..c1bd4683ceb 100644 --- a/static/_redirects +++ b/static/_redirects @@ -418,8 +418,6 @@ /subnets/how-to-delete-subnet /build/subnet/maintain/delete-subnet 301 /subnets/how-to-list-and-describe /build/subnet/maintain/view-subnets 301 /subnets/how-to-pause-and-resume-subnets /build/subnet/maintain/pause-resume-subnet 301 -/subnets/how-to-transform-subnet-to-elastic /build/subnet/elastic/transform-to-elastic-subnet 301 -/subnets/reference-elastic-subnets-parameters /build/subnet/elastic/elastic-parameters 301 /subnets/customize-a-subnet /build/subnet/upgrade/customize-a-subnet 301 /subnets/how-to-upgrade-precompile /build/subnet/upgrade/upgrade-precompile 301 /subnets/how-to-upgrade-subnet-vm /build/subnet/upgrade/upgrade-subnet-vm 301 From 8b3d406a209a8de139960a6c64939c7f05026009 Mon Sep 17 00:00:00 2001 From: Raymond Sukanto Date: Tue, 30 Jul 2024 12:15:41 -0400 Subject: [PATCH 4/6] fix lint --- docs/tooling/avalanche-cli.md | 89 +---------------------------------- 1 file changed, 1 insertion(+), 88 deletions(-) diff --git a/docs/tooling/avalanche-cli.md b/docs/tooling/avalanche-cli.md index d917a543387..ffb722a8291 100644 --- a/docs/tooling/avalanche-cli.md +++ b/docs/tooling/avalanche-cli.md @@ -129,7 +129,7 @@ avalanche subnet removeValidator [subnetName] [flags] --ledger-addrs strings use the given ledger addresses --local remove validator in existing local deployment --mainnet remove validator in existing mainnet deployment - --nodeID string node id of node to be added as validator in elastic subnet + --nodeID string set the NodeID of the validator to remove --output-tx-path string file path of the removeValidator tx --subnet-auth-keys strings control keys that will be used to authenticate removeValidator tx --testnet remove validator in existing testnet deployment (alias for `fuji`) @@ -521,93 +521,6 @@ The `subnet vmid` command prints the virtual machine ID (VMID) for the given Sub avalanche subnet vmid [subnetName] ``` -## Elastic Subnet - -### Transforms permissioned Subnet into Elastic Subnet - -This command transforms your permissioned Subnet into an Elastic Subnet (NOTE: this action is irreversible). - -**Usage:** - -```shell -avalanche subnet elastic [subnetName] [flags] -``` - -**Flags:** - -```shell - --default If true, use default elastic subnet config values - --denonimation int specify the token denomination (for Fuji and Mainnet only) - --force If true, override transform into elastic subnet warning - --fuji elastic subnet transform existing fuji deployment (alias for `testnet`) --k, --key string select the key to use [fuji only] --g, --ledger use ledger instead of key (always true on mainnet, defaults to false on fuji) - --ledger-addrs strings use the given ledger addresses - --local elastic subnet transform existing local deployment - --mainnet elastic subnet transform existing mainnet deployment - --output-tx-path string file path of the transformSubnet tx - --stake-amount int amount of tokens to stake on validator - --staking-period string how long validator validates for after start time - --start-time string when validator starts validating (format as "2006-01-02 15:00:00") - --subnet-auth-keys strings control keys that will be used to authenticate transformSubnet tx - --testnet elastic subnet transform existing testnet deployment (alias for `fuji`) - --tokenName string specify the token name - --tokenSymbol string specify the token symbol - --transform-validators If true, transform validators to permissionless validators after elastic transform -``` - -### Add Permissionless Validator in an Elastic Subnet - -This command adds a node as a permissionless validator in an Elastic Subnet. - -**Usage:** - -```shell -avalanche subnet join [subnetName] --elastic [flags] -``` - -**Flags:** - -```shell - --fuji add permissionless validator in existing fuji deployment (alias for `testnet`) --k, --key string select the key to use [fuji only] --g, --ledger use ledger instead of key (always true on mainnet, defaults to false on fuji) - --ledger-addrs strings use the given ledger addresses - --local add permissionless validator in existing local deployment - --mainnet add permissionless validator in existing mainnet deployment - --nodeID string node id of node to be added as validator in elastic subnet - --stake-amount int amount of tokens to stake on validator - --staking-period string how long validator validates for after start time - --start-time string when validator starts validating (format as "2006-01-02 15:00:00") - --testnet add permissionless validator in existing testnet deployment (alias for `fuji`) -``` - -### Add Permissionless Delegator in an Elastic Subnet - -This command delegates stake to a permissionless validator in an Elastic Subnet. - -**Usage:** - -```shell -avalanche subnet addPermissionlessDelegator [subnetName] [flags] -``` - -**Flags:** - -```shell - --fuji add permissionless delegator in existing fuji deployment (alias for `testnet`) --k, --key string select the key to use [fuji only] --g, --ledger use ledger instead of key (always true on mainnet, defaults to false on fuji) - --ledger-addrs strings use the given ledger addresses - --local add permissionless delegator in existing local deployment - --mainnet add permissionless delegator in existing mainnet deployment - --nodeID string node id of node to be added as validator in elastic subnet - --stake-amount int amount of tokens to delegate to validator - --staking-period string how long to delegate for after start time - --start-time string when to starts delegating (format as "2006-01-02 15:00:00") - --testnet add permissionless delegator in existing testnet deployment (alias for `fuji`) -``` - ## Subnet Upgrade The `subnet upgrade` command suite provides a collection of tools for From 31e5a36ce24b40be9e32a5749635920df9604cda Mon Sep 17 00:00:00 2001 From: Raymond Sukanto Date: Fri, 2 Aug 2024 18:14:26 -0400 Subject: [PATCH 5/6] fix merge --- docs/tooling/avalanche-cli.md | 2 -- 1 file changed, 2 deletions(-) diff --git a/docs/tooling/avalanche-cli.md b/docs/tooling/avalanche-cli.md index ca627f5f532..7d971f4bb61 100644 --- a/docs/tooling/avalanche-cli.md +++ b/docs/tooling/avalanche-cli.md @@ -521,8 +521,6 @@ The `blockchain vmid` command prints the virtual machine ID (VMID) for the given avalanche subnet vmid [blockchainName] ``` -## Subnet Upgrade - ## Blockchain Upgrade The `blockchain upgrade` command suite provides a collection of tools for From b524ad35022bb7c1f181bc06a0a1942d2c9cd4af Mon Sep 17 00:00:00 2001 From: Lavinia Talpas Date: Fri, 9 Aug 2024 17:32:27 +0300 Subject: [PATCH 6/6] remove links to elastic subnets --- docs/build/subnet/README.md | 7 +------ .../current/build/subnet/README.md | 5 ----- 2 files changed, 1 insertion(+), 11 deletions(-) diff --git a/docs/build/subnet/README.md b/docs/build/subnet/README.md index fd1460f193f..3c636b5b2c3 100644 --- a/docs/build/subnet/README.md +++ b/docs/build/subnet/README.md @@ -27,12 +27,7 @@ for a broad overview. | [**On Production Infrastructure**](/build/subnet/deploy/on-prod-infra.md) | | [**With Multisignature Authorization**](/build/subnet/deploy/multisig-auth.md) | | [**With a Custom Virtual Machine**](/build/subnet/deploy/custom-vm-subnet.md) | - -| Elastic Subnets | -| :----------------------------------------------------------------------------------------------------------------- | -| [**Transform a Permissioned Subnet into an Elastic Subnet**](/build/subnet/elastic/transform-to-elastic-subnet.md) | -| [**Elastic Subnet Parameters**](/build/subnet/elastic/elastic-parameters.md) | - + | Manage Subnets | | :----------------------------------------------------------------------------------------------------- | | [**View Your Created Subnets**](/build/subnet/maintain/view-subnets.md) | diff --git a/i18n/es/docusaurus-plugin-content-docs/current/build/subnet/README.md b/i18n/es/docusaurus-plugin-content-docs/current/build/subnet/README.md index c6bca04fb7c..2dd01635310 100644 --- a/i18n/es/docusaurus-plugin-content-docs/current/build/subnet/README.md +++ b/i18n/es/docusaurus-plugin-content-docs/current/build/subnet/README.md @@ -25,11 +25,6 @@ Las Subnets de Avalanche son un subconjunto de validadores de la red primaria de | [**Con autorización de firma múltiple**](/build/subnet/deploy/multisig-auth.md) | | [**Con una Máquina Virtual personalizada**](/build/subnet/deploy/custom-vm-subnet.md) | -| Subnets elásticas | | -| :--------------------------------------------------------------------------------------------------------------------- | --- | -| [**Transformar una Subnet permisionada en una Subnet elástica**](/build/subnet/elastic/transform-to-elastic-subnet.md) | -| [**Parámetros de la Subnet elástica**](/build/subnet/elastic/elastic-parameters.md) | - | Gestionar Subnets | | | :------------------------------------------------------------------------------------------------------------------ | --- | | [**Ver tus Subnets creadas**](/build/subnet/maintain/view-subnets.md) |