-
Notifications
You must be signed in to change notification settings - Fork 4
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Protocol + Feature Control #29
Comments
@5-mark assuming some extrinsic is disabled.
Could you please specify which one is expected as a result of disabling any extrinsic? |
I would see something the way ensure_signed works, like ensure_enabled where it checks if the extrinsic is e.g. whitelisted/signed/root. to make things simpler, we could/should also enable on pallet level. what do you think? |
Yes, that's the simplest approach I could think of. In general I see this feature the next way.
|
Moved: playzero/zero-network#185 |
User Story
As GameDAO Council I want to be able to control availability of protocol features:
Acceptance Criteria
Each major milestone contains different features, but the public availability may be phased in or out at different points in time or even may or may not be available on network a,b,c.
As launch support, we want to create a smooth transition from initial deployment to fully functional protocol suite. To achieve this, we want to enable features after periods, e.g.:
Additional Information
Discussion:
How to test
to be specified:
The text was updated successfully, but these errors were encountered: