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
Registering an expired (but not yet deleted) node is currently subject to the same update restriction rules as an active node being updated. However it would make sense for expired nodes to be allowed to update certain(most?) fields.
AFAIK the reasons for restrictions apply mostly to active nodes - since most restrictions are there to prevent certain mid-epoch updates (e.g. removing node support for a runtime mid-epoch).
For example: currently a node needs to be unregistered for a debonding-period number of epochs, before it is able to register without a previously registered runtime.
The text was updated successfully, but these errors were encountered:
Registering an expired (but not yet deleted) node is currently subject to the same update restriction rules as an active node being updated. However it would make sense for expired nodes to be allowed to update certain(most?) fields.
AFAIK the reasons for restrictions apply mostly to active nodes - since most restrictions are there to prevent certain mid-epoch updates (e.g. removing node support for a runtime mid-epoch).
For example: currently a node needs to be unregistered for a debonding-period number of epochs, before it is able to register without a previously registered runtime.
The text was updated successfully, but these errors were encountered: