Motion to NOT include ProgPow without audit

Here is the main contention @ameensol surfaces:

A completed audit is a prerequisite for hard fork inclusion. I think this is not only reasonable, but a bare minimum for due diligence! Changing a core component of the protocol should not be taken lightly and would only benefit from an external review.

Setting aside who pays for it, don’t you agree there should be an audit?

5 Likes