-
Notifications
You must be signed in to change notification settings - Fork 45
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
This PR removes the minStake and status from the GATEWAY contracts. Previously we had this as we only have collateral based PermissionMode and the idea is to use these parameters to control in the Gateway to enforce some control over different subnets. But now we are moving towards different `PermissionMode` and these parameters no longer required. Note that `minStake` is a parameter applied to all subnets created, but for `PermissionMode.Federated`, there is no collateral requirements, so a `minStake` in the Gateway must be 0. Anything above zero will prevent `Federated` subnet to be register in the gateway. If `minStake` is always 0, just remove this parameter. At the same time, `status` will be deprecated as well as collateral alone does not manage the status of the subnet. Overall, subnets are managing their own stake requirements and status, so that the gateway does not really need to be aware of subnet’s status and status is not used anywhere except for listing subnets. Subnet’s status is managed in SubnetActor now, in bootstrapped and killed parameters, Gateway no longer needs to maintain the status.
- Loading branch information
1 parent
903ade6
commit 8632617
Showing
17 changed files
with
773 additions
and
857 deletions.
There are no files selected for viewing
Large diffs are not rendered by default.
Oops, something went wrong.
Large diffs are not rendered by default.
Oops, something went wrong.
Large diffs are not rendered by default.
Oops, something went wrong.
Large diffs are not rendered by default.
Oops, something went wrong.
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file was deleted.
Oops, something went wrong.
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.