Mark Evenson

> I'd suggest adding a section for `Wire Format Specification / Syntax` after `Exposition of Snow-family Consensus Models` Resolved. > `Security/Privacy Considerations` whould be helpful. See the "Sovereignty Considerations" section....

> Just looking briefly at https://www.notion.so/Consensus-cca3f5b9bed341219d1cfd027bea897c the first thing I see is a lot of helpful requirements regarding fast finality etc. This also might disqualify other mechanisms. I can't find...

> I think it would it make sense to have a brief section on how this compares with PoW/Nakamoto Consensus and PoS/LMD-GHOST (https://arxiv.org/pdf/2003.03052.pdf)? Similarities and differences, briefly. It should explain...

> initial coherent whole It is not the case that the notion content is not coherent: it is very coherent. It is more that we need to consider an audience...

Currently I favor utilizing some of Alexander's work on the mathematical exposition of Glacier, as with it is perhaps easier to see that Glacier is indeed one of many members...

> The underlying consensus algorithm is quite simple to implement. The acceptance criteria should mainly be that someone can implement it in a given language completely such that it yields...

> We have it in Rust, it might be worthwhile to talk with Daniel (Logos engineer) about how he did it. I have reviewed the code somewhat and will talk...

Was "Easye/reputation rfc/20220804a"

Joining a bit late, but chiming in an idea 1) rename the RFC category "Best Current Practice" to "Implementation Details". A BCP might be a type of an "Implementation" RFC....

Pulling the trigger on this for [kakuhen](https://github.com/kakuhen), who uses Leiningen more than I do.