You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently, if value is sent when registering a new subnet, we record it as collateral contributed by the creator, who will now be enlisted as a validator in the network. While this might be useful in some situations, it can be achieved by performing both actions separately, in an atomic manner if needed, either through a Multicall contract or through a dedicated utility smart contract.
In other words, this feature is actually an aggregate of two other features, and therefore my view is that it can be dropped from the base protocol/mechanics in order to reduce complexity. As far as I know, it is not being actively used by any adopter at the current time. And this work #1130 was forced to add extra complexity to sustain this feature as we added a new collateral asset kind.
We can apply the same simplification to circulating supply -- I would just drop this as a subnet creation parameter.
The text was updated successfully, but these errors were encountered:
Currently, if value is sent when registering a new subnet, we record it as collateral contributed by the creator, who will now be enlisted as a validator in the network. While this might be useful in some situations, it can be achieved by performing both actions separately, in an atomic manner if needed, either through a Multicall contract or through a dedicated utility smart contract.
In other words, this feature is actually an aggregate of two other features, and therefore my view is that it can be dropped from the base protocol/mechanics in order to reduce complexity. As far as I know, it is not being actively used by any adopter at the current time. And this work #1130 was forced to add extra complexity to sustain this feature as we added a new collateral asset kind.
We can apply the same simplification to circulating supply -- I would just drop this as a subnet creation parameter.
The text was updated successfully, but these errors were encountered: