Ethereum [ETH] ProgPow technical audit will be conducted by Least Authority
Hudson Jameson, a core dev of Ethereum Foundation, released an update on Programmatic Proof-of-Work [ProgPow], on the official blog of Ethereum Cat Herders, on March 25. According to the report, Ethereum Cat Herders are responsible for two tasks related to the ProgPow implementation; ‘Gauge the community sentiment’ and ‘general consensus’ of the Ethereum community, and its technical audit.
On the technical audit side, the Ethereum Cat Herders decided that the audit would be conducted by the Least Authority, a security consultancy. Notably, this is not the first time that Least Authority is performing an audit on Ethereum. Previously, the consultancy performed one of the most elaborate audits on Ethereum, gas economics, and PoW puzzle. Least Authority has also performed an audit for another leading cryptocurrency project in the space, ZCash.
The blog read:
“Please note that the timeline contained in this version of the audit proposal is inaccurate. The timeline for the audit is currently unknown until the audit is funded and technical details of the audit are finalized with the auditor.”
Hudson further stated that the Cat Herders were seeking funding for the ProgPow audit from a “variety of sources”. This included miners, community members, and organizations in the Ethereum ecosystem. The team also created a Gitcoin account specifically for ProgPow funding, with a monthly goal of 50,000 DAI. At press time, the funding for the ProgPow implementation was 0 DAI. The post said,
“Note that the Gitcoin grant will only be for a portion of the funding and we will rely on larger organizations and others to contribute. We appreciate everyone who is contributing to this audit!”
Previously, there were doubts pertaining to the implementation of ProgPow and its timeline, however, these concerns were addressed by Hudson in a Reddit post. He stated:
“In summary, a decision was made to move forward with ProgPoW, but no timeline was given as to when it would be activated in a hard fork. It may be activated in its own fork or with Istanbul. If an issue is found by the ProgPoW audit, we may not go forward with implementing and activating ProgPoW.”
Back to the list