Does anyone have ccminer at suprnova pool working?
Give me five minutes, im updating the OP with all links
Topic: Securitycoin [SCSY] | Bittrex and IRC in Wallet | Ccex | Community | VPOS - page 45. (Read 75214 times)
January 15, 2015, 04:49:42 PM
Give me five minutes, im updating the OP with all links
January 15, 2015, 04:48:55 PM
Does anyone have ccminer at suprnova pool working?
Give me five minutes, im updating the OP with all links
January 15, 2015, 04:47:21 PM
Does anyone have ccminer at suprnova pool working?
January 15, 2015, 04:34:37 PM
Suprnova pools have been finding blocks but nobody is getting the rewards.
yeah because block reward is 0 until block 7,200
If there is nothing to pay out, there is nothing to pay out ;-)
January 15, 2015, 04:29:17 PM
I can't get more than 17.5 Mh/s on 280x, any config to improve that?
Thanks!
Thanks!
i'm getting 21 MH/s on linux, latest omega drivers, non overclocked with -I 12 and -g 1
Thanks, I'll try!
January 15, 2015, 04:28:19 PM
running in to a little trouble with stratum.
always shares are rejected with ntime out of range.
also it's not clear on a couple settings...
MPOS global.inc.php - $config['algorithm'] = '??'
securitycoin-stratum-mining config.py - COINDAEMON_ALGO = '??'
always shares are rejected with ntime out of range.
also it's not clear on a couple settings...
MPOS global.inc.php - $config['algorithm'] = '??'
securitycoin-stratum-mining config.py - COINDAEMON_ALGO = '??'
I did some poking around in the code and found that template_registry.py tests if COINDAEMON_ALGO is 'hefty1', as opposed to 'heavy' from heavycoin, so that's what I'm going to assume is right for now.
I also found the implementation of checking ntime in the same template_registry.py which implements check_ntime from block_template.py
I commented out the "if ntime < self.curtime" and my errors are no longer "ntime out of range" but rather something else entirely, so I'm pretty sure my miner is sending some kind of invalid shares but I don't know if it's a miner problem or still a stratum problem not configured correctly.
I'm happy to see such a lover of stratums, pools, hefty1 and our coin.
But sorry, this is not a "stratum developers forum".
OCminer has already done all the work to get stratum working.
If you want to become a pool owner and you need some explanation, please send a pm to me or to ocminer (ocminer is for sure better than me in stratum-mining).
thanks.
Cheers
Sorry didn't mean to be rude.
Suprnova pools have been finding blocks but nobody is getting the rewards.
No rewards until block > 7200
I don't think our dev was trying to be either. I have had the same problem with him since his first language is not english it comes off alot more harsh than he actually means it lol.
lol oh yeah no problem. He's just being direct, not rude. Nothing wrong with being direct.
He probably owes an apology to ocminer though, sending me his way. Poor guy!
January 15, 2015, 04:28:08 PM
January 15, 2015, 04:24:43 PM
Suprnova pools have been finding blocks but nobody is getting the rewards.
yeah because block reward is 0 until block 7,200
January 15, 2015, 04:17:00 PM
I can't get more than 17.5 Mh/s on 280x, any config to improve that?
Thanks!
Thanks!
i'm getting 21 MH/s on linux, latest omega drivers, non overclocked with -I 12 and -g 1
January 15, 2015, 04:13:53 PM
I can't get more than 17.5 Mh/s on 280x, any config to improve that?
Thanks!
Thanks!
January 15, 2015, 04:09:18 PM
running in to a little trouble with stratum.
always shares are rejected with ntime out of range.
also it's not clear on a couple settings...
MPOS global.inc.php - $config['algorithm'] = '??'
securitycoin-stratum-mining config.py - COINDAEMON_ALGO = '??'
always shares are rejected with ntime out of range.
also it's not clear on a couple settings...
MPOS global.inc.php - $config['algorithm'] = '??'
securitycoin-stratum-mining config.py - COINDAEMON_ALGO = '??'
I did some poking around in the code and found that template_registry.py tests if COINDAEMON_ALGO is 'hefty1', as opposed to 'heavy' from heavycoin, so that's what I'm going to assume is right for now.
I also found the implementation of checking ntime in the same template_registry.py which implements check_ntime from block_template.py
I commented out the "if ntime < self.curtime" and my errors are no longer "ntime out of range" but rather something else entirely, so I'm pretty sure my miner is sending some kind of invalid shares but I don't know if it's a miner problem or still a stratum problem not configured correctly.
I'm happy to see such a lover of stratums, pools, hefty1 and our coin.
But sorry, this is not a "stratum developers forum".
OCminer has already done all the work to get stratum working.
If you want to become a pool owner and you need some explanation, please send a pm to me or to ocminer (ocminer is for sure better than me in stratum-mining).
thanks.
Cheers
Sorry didn't mean to be rude.
Suprnova pools have been finding blocks but nobody is getting the rewards.
No rewards until block > 7200
I don't think our dev was trying to be either. I have had the same problem with him since his first language is not english it comes off alot more harsh than he actually means it lol.
January 15, 2015, 04:08:13 PM
running in to a little trouble with stratum.
always shares are rejected with ntime out of range.
also it's not clear on a couple settings...
MPOS global.inc.php - $config['algorithm'] = '??'
securitycoin-stratum-mining config.py - COINDAEMON_ALGO = '??'
always shares are rejected with ntime out of range.
also it's not clear on a couple settings...
MPOS global.inc.php - $config['algorithm'] = '??'
securitycoin-stratum-mining config.py - COINDAEMON_ALGO = '??'
I did some poking around in the code and found that template_registry.py tests if COINDAEMON_ALGO is 'hefty1', as opposed to 'heavy' from heavycoin, so that's what I'm going to assume is right for now.
I also found the implementation of checking ntime in the same template_registry.py which implements check_ntime from block_template.py
I commented out the "if ntime < self.curtime" and my errors are no longer "ntime out of range" but rather something else entirely, so I'm pretty sure my miner is sending some kind of invalid shares but I don't know if it's a miner problem or still a stratum problem not configured correctly.
I'm happy to see such a lover of stratums, pools, hefty1 and our coin.
But sorry, this is not a "stratum developers forum".
OCminer has already done all the work to get stratum working.
If you want to become a pool owner and you need some explanation, please send a pm to me or to ocminer (ocminer is for sure better than me in stratum-mining).
thanks.
Cheers
Sorry didn't mean to be rude.
Suprnova pools have been finding blocks but nobody is getting the rewards.
No rewards until block > 7200
January 15, 2015, 04:02:23 PM
Suprnova pools have been finding blocks but nobody is getting the rewards.
January 15, 2015, 03:31:09 PM
running in to a little trouble with stratum.
always shares are rejected with ntime out of range.
also it's not clear on a couple settings...
MPOS global.inc.php - $config['algorithm'] = '??'
securitycoin-stratum-mining config.py - COINDAEMON_ALGO = '??'
always shares are rejected with ntime out of range.
also it's not clear on a couple settings...
MPOS global.inc.php - $config['algorithm'] = '??'
securitycoin-stratum-mining config.py - COINDAEMON_ALGO = '??'
I did some poking around in the code and found that template_registry.py tests if COINDAEMON_ALGO is 'hefty1', as opposed to 'heavy' from heavycoin, so that's what I'm going to assume is right for now.
I also found the implementation of checking ntime in the same template_registry.py which implements check_ntime from block_template.py
I commented out the "if ntime < self.curtime" and my errors are no longer "ntime out of range" but rather something else entirely, so I'm pretty sure my miner is sending some kind of invalid shares but I don't know if it's a miner problem or still a stratum problem not configured correctly.
I'm happy to see such a lover of stratums, pools, hefty1 and our coin.
But sorry, this is not a "stratum developers forum".
OCminer has already done all the work to get stratum working.
If you want to become a pool owner and you need some explanation, please send a pm to me or to ocminer (ocminer is for sure better than me in stratum-mining).
thanks.
Cheers
January 15, 2015, 03:19:07 PM
running in to a little trouble with stratum.
always shares are rejected with ntime out of range.
also it's not clear on a couple settings...
MPOS global.inc.php - $config['algorithm'] = '??'
securitycoin-stratum-mining config.py - COINDAEMON_ALGO = '??'
always shares are rejected with ntime out of range.
also it's not clear on a couple settings...
MPOS global.inc.php - $config['algorithm'] = '??'
securitycoin-stratum-mining config.py - COINDAEMON_ALGO = '??'
I did some poking around in the code and found that template_registry.py tests if COINDAEMON_ALGO is 'hefty1', as opposed to 'heavy' from heavycoin, so that's what I'm going to assume is right for now.
I also found the implementation of checking ntime in the same template_registry.py which implements check_ntime from block_template.py
I commented out the "if ntime < self.curtime" and my errors are no longer "ntime out of range" but rather something else entirely, so I'm pretty sure my miner is sending some kind of invalid shares but I don't know if it's a miner problem or still a stratum problem not configured correctly.
January 15, 2015, 01:35:23 PM
running in to a little trouble with stratum.
always shares are rejected with ntime out of range.
also it's not clear on a couple settings...
MPOS global.inc.php - $config['algorithm'] = '??'
securitycoin-stratum-mining config.py - COINDAEMON_ALGO = '??'
always shares are rejected with ntime out of range.
also it's not clear on a couple settings...
MPOS global.inc.php - $config['algorithm'] = '??'
securitycoin-stratum-mining config.py - COINDAEMON_ALGO = '??'
January 15, 2015, 12:03:26 PM
Ok..so max block reward is 640. Anyone know what the max block size should be in coin control to avoid hitting max reward. Just bought 30k of these and need to stake them for max reward. Also I noticed I dont see min stake time listed anywhere. Anyone?
Vegas
Vegas
MinStageAge is 24 hours.
To avoid hit max reward you should consider also the % reward (which is variable in our coin). Anyway, until the last PoW block it's 100% .. so, this means 640 * 365 = 233600 should be the limit. More or less.
January 15, 2015, 11:53:32 AM
SCSY_dev hefty1 is not an algorithm check here please. this coin should use mjollnir i think thats the problem.
https://bitcointalksearch.org/topic/m.10163048
https://bitcointalksearch.org/topic/m.10163048
first of all the first coin which used hefty1 was heavycoin, so it's not mjollnir coin algo but better heavycoin algo.
hefty1 it's a combination between sha, blake, groestl and keccak.. it's all well explained here http://heavycoin.github.io/about.html
January 15, 2015, 10:43:41 AM
Ok..so max block reward is 640. Anyone know what the max block size should be in coin control to avoid hitting max reward. Just bought 30k of these and need to stake them for max reward. Also I noticed I dont see min stake time listed anywhere. Anyone?
Vegas
Vegas
24h min stake age.
Got the same question here, have ~3.000.000 to stake
January 15, 2015, 10:31:08 AM
Ok..so max block reward is 640. Anyone know what the max block size should be in coin control to avoid hitting max reward. Just bought 30k of these and need to stake them for max reward. Also I noticed I dont see min stake time listed anywhere. Anyone?
Vegas
Vegas
Jump to: