ProgPOW
ProgPOW copied to clipboard
ifdefelse
A Programmatic Proof-of-Work for Ethash. Forked from https://github.com/ethereum-mining/ethminer
README states that release 0.9.3 has been software and hardware audit. The hardware audit seems to be there. However, the link for Least Authority's audit in the repository is broken....
Noting that ETHASH_DATASET_PARENTS is included from https://github.com/ifdefelse/ProgPOW/blob/master/libethash/ethash.h#L37, for use in https://github.com/ifdefelse/ProgPOW/blob/master/libethash-cuda/CUDAMiner_cuda.cu#L9. Is the current implementation working?
I have a problem with running ProgPow on my macbook (I am doing this only for test purposes). When I start benchmark mode, I get: ``` [~/open-source/ProgPOW/build]$ ./ethminer/ethminer -G -M...
I'm trying to implement ProgPow 0.9.4 in Scala from the spec described [here](https://github.com/ifdefelse/ProgPOW/blob/master/README.md), but I have a problem matching test vectors from [the repo](https://github.com/ifdefelse/ProgPOW/blob/master/test-vectors.md#progpowhash) to my results. The problem starts...
uint64_t is too small. see detail https://github.com/kik/progpow-exploit
https://github.com/SChernykh/CryptonightR/issues/1#issuecomment-452775046 > In fact, a carefully designed ASIC could still outperform GPU by spending more resource/area on the bottlenecks. The memory bandwidth can be greatly improved using more smaller DRAM...
64-bit seed did look like providing only a low safety margin to me during my ProgPoW review last year, and I was going to revisit this and share some thoughts...
The [ProgPoW software audit](https://github.com/ethereum-cat-herders/progpow-audit/raw/master/Least%20Authority%20-%20ProgPow%20Algorithm%20Final%20Audit%20Report.pdf) recommend to increase the `DATASET_PARENTS` Ethash cache parameter from 256 to 512. This has direct impact on verification performance as the time for single verification doubles...
As I understand, this ProgPoW tree relies on never finding a solution below target, or else it'd try to validate the solution on CPU as Ethash, which will fail. The...
We might want to either tune ProgPoW to produce a similar hashrate to what Ethash produces on same currently relevant hardware and at same DAG size, or document a rationale...