Parts of deployed shared random protocol are specified only in the proposal
In dir-spec.txt, commit c4ae4dd31 gave us lines like
+ Denotes a directory authority commit for the shared randomness
+ protocol, containing the commitment value and potentially also the
+ reveal value. See sections [COMMITREVEAL] and [VALIDATEVALUES] of
+ proposal 250 on how to generate and validate these values.That's a great improvement over just leaving it implicit. But if we have a goal of having Tor specified in the spec files (is that true?), then we should migrate the key sections from the proposal file to either dir-spec or a new srv-spec file.
To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information