Yes , Any new info for the pocminer written in C and not in java ( java is very very slow
) .
95% done, but usable if you add your passphrase to the code manually.
- a lot faster
- multithreaded
- multiple plot directories
- uses almost no memory
- for solo mining only (I guess)
http://pastebin.com/PrnGyg19Go to line 101 and put your passphrase in. Remember to replace spaces with +
Then compile (gcc -o mine mine.c shabal.o -lpthread)
When running always end the path's with /
so:
> ./mine 127.0.0.1 /mnt/disk1/plots/ /mnt/disk2/plots/ /mnt/disk3/plots/
2872 MB read/11488 GB total/deadline 13929s (13855s left)
New block 8144, basetarget 12214315
2872 MB read/11488 GB total/deadline 3537s (3166s left)
New block 8145, basetarget 12897708
2872 MB read/11488 GB total/deadline 12357s (12077s left)
New block 8146, basetarget 13253224
2872 MB read/11488 GB total/deadline 2202s (1944s left)
New block 8147, basetarget 13829153
2872 MB read/11488 GB total/deadline 2579s (1850s left)
New block 8148, basetarget 13957505
2872 MB read/11488 GB total/deadline 9786s (9643s left)
New block 8149, basetarget 13761067
2872 MB read/11488 GB total/deadline 17811s (17506s left)
New block 8150, basetarget 13768134
2872 MB read/11488 GB total/deadline 8542s (8407s left)
its working for pool mining at
http://burst-pool.cryptoport.io
but sometime it get segfault when new block event, do you know why? but if i run inside gdb its ok, no problem at all, is it thread problem maybe?
source and bin is here
https://s3-ap-southeast-1.amazonaws.com/burst-mirror/dcct-pool-miner.tgzHi Uray, do you know why when I'm mining I receive this error??
{"baseTarget":"12336437","height":"8209","generationSignature":"5d38600ea5b3bfcc
db85915b634442e442e5700abb6ac0526e0a731e6ec9f09d","poolTime":1409745437760,"pool
Diff":"0.0015","netDiff":"1485.5"}
New best: 14201777295111134013:2732
{"baseTarget":"12336437","height":"8209","generationSignature":"5d38600ea5b3bfcc
db85915b634442e442e5700abb6ac0526e0a731e6ec9f09d","poolTime":1409745443281,"pool
Diff":"0.0015","netDiff":"1485.5"}
Submitting share
{"result":"Passphrase is for a different account"}
these are some of the case :
- did your account have public key? (done atleast 1 output tx)
- reward assignment transaction done? if its done, its maybe your reward assignment not confirmed yet by network
- you are using wrong miner, you can't use miner for solo, there are one more field on post request on pool mining which is accountId, pool will detect if you have accountId field, it will ignore passphrase, if you dont have it, pool will read passpharase and redirect for solo mining (in this case your secret passphrase is wrong for your account)
Thanks!
