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 named task.

 # <weight>
 - S = Number of already scheduled calls
 - Base Weight: 29.6 + .159 * S µs
 - DB Weight:
     - Read: Agenda, Lookup
     - Write: Agenda, Lookup
 - Will use base weight of 35 which should be good for more than 30 scheduled calls
 # </weight>

- There was a referendum called Referendum 71 that already passed.
- They want to submit the same design as a motion to fast track it.
- The proposal will increase the number of validators by 2 every 3600 blocks for about 3 months.
- At the end, there will be a total of x+672 validators.
- If there are any problems, they can cancel the increases.

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