-
Notifications
You must be signed in to change notification settings - Fork 61
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
ECIP-1070: ProgPoW for ETC Discussions #172
Comments
Conclusion of hardware and software security audits. |
Former home of gangnum testnet. https://github.com/greerso/testnet |
Current Trello of ProgPoW hype/fud https://trello.com/b/KrD25QI5/progpow |
gonna post the same comment I wrote for the sha3 ticket: |
The asymmetry between mining and verifying is still problematic (too low). It has the same issue as Ethash: Extremely expensive verification (compared to sha256, for instance). This is because of a pseudo-random changing of params per epoch (every ~5 days). This prevents the ability to have a pure function for verification. Verification requires a much more expensive context: The full historic datasets that resulted in particular epoch params. |
Yeah, that's why I believe SHA3 is the most elegant solution. |
I believe this can be closed. |
Discussions for ProgPoW for ETC Discussions concerning this Pull Request: #171
The text was updated successfully, but these errors were encountered: