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

Useless for mining altcoins (anycoin different than ethereum) #25

Closed
rvsh2 opened this issue Feb 9, 2018 · 4 comments
Closed

Useless for mining altcoins (anycoin different than ethereum) #25

rvsh2 opened this issue Feb 9, 2018 · 4 comments

Comments

@rvsh2
Copy link

rvsh2 commented Feb 9, 2018

Dev fee is mined only on ethereum and use ethereum DAG so need ethereum wallet. If I mine some altcoin eg. ELLAISM ora PIRL ora AKROMA then nodevfee use ELLAISM&etc. wallet address on ethereum pool for example on ethermine.org. I can see my ellaism address on ethermine.org with 'default' worker and hashrate that I missed.

Please add mining dev fee to wallet in nodevfeewallet.txt and mining normal to adress specified in config.txt or command line. That should fix the main issue of this app.

Will donate if you do.
Thanks!

@Demion
Copy link
Owner

Demion commented Feb 9, 2018

You can try nodevfeePools.txt and try redirect ethermine.org to your altcoin pool. If that does not help, then no solution so far. Read more about that on main page README.

@rvsh2
Copy link
Author

rvsh2 commented Feb 9, 2018

I tried it and it worked but only when dev fee 'is mined' from dwarfpool. Other pools has somekind of authorisation failure.

I normally use remote managment to change coins (many rigs) - in this case above solution is very time consuming.

Thanks for advice.

@rvsh2
Copy link
Author

rvsh2 commented Feb 9, 2018

I use config.txt:

-dbg -1
-r 1
-minspeed 190
-mport 3005
-mpsw xxx
-mode 1
-ftime 10
-tstop 85
-tt 60
-fanmin 85
-fanmax 100
-cclock 1050,1050,1150,1150,1150,1050,1150
-mclock 2050,2050,2050,2100,2050,2050,2100
-cvddc 870,870,870,870,870,870,870
-mvddc 885,885,885,885,885,885,885
-powlim -20,-20,-20,-20,-20,-20
-dcri 1
-allcoins -1
-asm 2
-retrydelay 1

'Retrydelay 1' is a must in this case.

@Demion
Copy link
Owner

Demion commented Feb 9, 2018

Authorization problem is common and cause is your pool only supports one of protocols (ESM 0 or ESM 1) but devfee switches protocols randomly (dwarpool being ESM 0 so must be your pool, other devfee pools ESM 1). So your only solution is to try another pool or just leave as is.

-retrydelay 1 is a nice catch, might be useful for other users.

Further resolving requires rebuild of whole devfee packet structure and change it from -esm 1 to -esm 0 or vice versa (nodevfee code update).

More discussion here - #19

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants