Protocol + Feature Control

[5-mark]

User Story

As GameDAO Council I want to be able to control availability of protocol features:

• enable / disable protocol features via council vote
• emergency stop and restart
• immediate or blocktime based

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.:

1. Tokensale
2. Token Generation
3. Protocol Core Launch
4. DID, DAO
5. Staking
6. Voting
7. Grants
8. Fundraising

Additional Information

Discussion:

• https://www.figma.com/file/sCvZGzghEHSKKNeXtMdi3W/Protocol-Config-Pallet?node-id=0%3A1

How to test

1. create a voting to enable feature x on block y
2. see x enabled on chain at destination block y

to be specified:

• expose state via graphql

[vayesy]

@5-mark assuming some extrinsic is disabled.
There are two options how it can be blocked from execution.

1. Extrinsic is not listed in available endpoints and not possible to be called. This is similar to when extrinsic doesn't exist.
2. Extrinsic exists but returns error upon execution.

Could you please specify which one is expected as a result of disabling any extrinsic?

[2075]

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?

[vayesy]

Yes, that's the simplest approach I could think of.

In general I see this feature the next way.

1. New pallet to control availability of other pallets/extrinsics.
   This pallet will expose few helper methods for other pallets to validate if those pallets and extrinsics are available.
   It will also provide API (extrinsics with root only access or outcome of a vote?) to mark specific pallet/extrinsic as enabled/disabled and store that value in storage.
2. Invoke helper methods in the extrinsics to validate for access, based on storage value and raise an error in case if needed.
   In case access is granted, proceed with pallet/extrinsic specific logic.

[vovacha]

Moved: playzero/zero-network#185