Skip to content
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

Closed
YazzyYaz opened this issue Nov 7, 2019 · 7 comments
Closed

ECIP-1070: ProgPoW for ETC Discussions #172

YazzyYaz opened this issue Nov 7, 2019 · 7 comments
Labels
type: std-core ECIPs of the type "Core" - changing the Classic protocol.

Comments

@YazzyYaz
Copy link
Contributor

YazzyYaz commented Nov 7, 2019

Discussions for ProgPoW for ETC Discussions concerning this Pull Request: #171

@realcodywburns realcodywburns added the type: std-core ECIPs of the type "Core" - changing the Classic protocol. label Nov 7, 2019
@realcodywburns
Copy link
Member

Conclusion of hardware and software security audits.
https://medium.com/ethereum-cat-herders/progpow-audits-released-ed4973ebe073

@realcodywburns
Copy link
Member

Former home of gangnum testnet. https://github.com/greerso/testnet
Status Dashboard: http://boot.gangnam.ethdevops.io/
Block Explorer: https://gangnam.etherchain.org/
Mining Pool: https://gangnam.wattpool.net/
Gitter Support: https://gitter.im/ifdefelse/community/

@realcodywburns
Copy link
Member

Current Trello of ProgPoW hype/fud https://trello.com/b/KrD25QI5/progpow

@BelfordZ
Copy link
Member

BelfordZ commented Nov 8, 2019

gonna post the same comment I wrote for the sha3 ticket:
#13 (comment)

@zmitton
Copy link
Contributor

zmitton commented Nov 8, 2019

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.

@soc1c
Copy link
Contributor

soc1c commented Nov 8, 2019

Yeah, that's why I believe SHA3 is the most elegant solution.

@GregTheGreek
Copy link

I believe this can be closed.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
type: std-core ECIPs of the type "Core" - changing the Classic protocol.
Projects
None yet
Development

No branches or pull requests

6 participants