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

this proposal has not necessarily been thoroughly game-theoried, other than a quick sanity check by Will P.

 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>



1. Increase the validator count by 2 every 3600 blocks, 336 times (over 3 months). 
2. After enactment, total validator count will be 1172 (if https://kusama.polkassembly.io/referendum/69 passes) or 1072 (if it does not). 
3. Network stability or economics can be cancelled at any point during enactment with the command `scheduler.cancel_named` on the id `0x2b3325` 
4. Proposal has gone through a quick sanity check by Will P.

#71 Gradual Validator Count Ramp-up (+672 Validators/~3 Months)

No Active Proposals