Quote from: BoozyTalking on Today at 08:42:00 AM

Quote from: rigelminer on September 25, 2023, 09:23:10 PM

Quote from: angelbbs on September 25, 2023, 08:56:24 PM

Quote from: rigelminer on September 24, 2023, 01:59:13 PM

Rigel 1.8.0

* Add mining support for the following coins (dev fee 1%):
  * Ravencoin (`-a ravencoin`, see `rvn` bat/sh script)
  * Neurai (`-a neurai`, see `xna` bat/sh script)
  * Clore (`-a clore`, see `clore` bat/sh script)
* (IronFish) Minor performance improvements for `<algo>+ironfish` dual modes

Raven coin, Neural, Clore, Neoxa.. and Paprikacoin, Zatox, Gamepass, Meow coin, Hivecoin, Procyon Coin etc. come true mining with KAWPOW algo.
Why split it up on "-a ravencoin", "-a neurai" etc?

I had to resort to using coin names for `-a` as different kawpow coins use DAGs of different sizes and it creates a problem where the miner would need to rebuild the DAG every few minutes to mine dev fee. When you specify the coin name the miner knows exactly what you're mining and will be mining the same coin as dev fee thus avoiding DAG rebuilds.

LooooooooL. What a joke. Miner must set correct algo through stratum protocol. Kawpow now use at least 20+ coins, Ethash use 30+ coins - will you name every coin as different parameters?

No joke, it´s normal. Reminds me to claymore in the past, where the miner in every devfee period recreates the DAG if you mined an other coin as ETH, and Rigel will avoid this, so it is good and bad.
But i understand the point, an native support for KAWPOW would nice, so that the user can decide if they want a DAG creation in every devfee period.