Referendum 71 was scheduled to be executed on block 3,200,000, and when it passed this was in already in the past. Submitting the same design as Ref 71 but as motion, since it was passed already via referenda, so we can fast track. 

This proposal will increase the validator count by 2 every 3600 blocks (1 era) 336 times (roughly over the course of 3 months).

At the end of this time period we will have a total of x+672 validators, where x is the number of validators slot once enactment of this proposal begins (in total 1172 if https://kusama.polkassembly.io/referendum/69 passes, of 1072 if it does not).

If at any point during enactment we see network stability or economics being harmed, we can cancel further increases using scheduler.cancel_named on the id this uses, 0x2b3325 (please ignore the fact this converts to +3% in utf8, I changed the parameters of the proposal based on advice and forgot to change the id).

 Schedule a majority-carries referendum to be tabled next once it is legal to schedule
 an external referendum.

 The dispatch of this call must be `ExternalMajorityOrigin`.

 - `proposal_hash`: The preimage hash of the proposal.

 Unlike `external_propose`, blacklisting has no effect on this and it may replace a
 pre-scheduled `external_propose` call.

 # <weight>
 - Complexity: `O(1)`
 - Db write: `NextExternal`
 - Base Weight: 3.065 µs
 # </weight>

- Referendum 71 has already passed in the past.
- A motion is being submitted with the same design as Ref 71 to fast track it.
- The proposal will increase the validator count by 2 every 3600 blocks for 3 months.
- At the end of the time period, there will be a total of x+672 validators.
- If there are any issues during the process, further increases can be canceled.

#185 Gradual Validator Count Ramp-up (+672 Validators/~3 Months) - same as Referendum 71 (read below)