Upcoming DAG size reduction for VEIL ProgPow

[us77ipis]

We are planning to reduce the DAG size for VEIL ProgPow mining.

As far as I can see, mining software currently has hardcoded the rule for epoch derivation from the block height. Since the DAG size reduction will be done by changing the epoch, and to allow for more flexibility in the future, I would propose the following changes:

• Add another parameter to the mining.notify call of the stratum protocol implementation through which the mining software gets the current epoch number.
• If you (or WildRig miner) currently have implemented some optimization for pre-computing DAGs near an epoch change, maybe we could also add a second additional parameter to mining.notify which specifies the epoch of the upcoming next block. Then, you can still pre-compute DAGs on GPUs with enough memory.

This (or a similar) solution would be preferable over hardcoding the epoch derivation changes in the mining software, as it allows for more flexibility in the future.

Once we agree on a solution, I can quickly setup a stratum server on a devnet where you can connect to for testing your T-Rex implementation.

Thanks for your support.

[seanPhill]

Thanks! We are available for any questions and collaboration with T-Rex. support@veil-project.com is also another way to contact us.

[us77ipis]

See https://github.com/andru-kun/wildrig-multi/issues/144 for ongoing discussion on this.

[us77ipis]

@trexminer How does T-Rex miner currently pre-compute DAGs? Is it done only one block before the epoch change or already multiple blocks before?