|
cryptohunter
Legendary
Offline
Activity: 2100
Merit: 1167
MY RED TRUST LEFT BY SCUMBAGS - READ MY SIG
|
|
May 22, 2013, 10:06:41 PM |
|
this pool needs to stop registrations, the coin is very vulnerable at this level that pool had way over 51% of hash.
|
|
|
|
MaGNeT
Legendary
Offline
Activity: 1526
Merit: 1002
Waves | 3PHMaGNeTJfqFfD4xuctgKdoxLX188QM8na
|
|
May 22, 2013, 10:11:28 PM |
|
If you have >1000 Khash/s just keep solo mining. You still find an average of 9 blocks in 24 hours at current difficulty with 1000 Khash/s No pool fees, no DDOS, no pool crashes, etc. Just went back on mining solo again
|
|
|
|
daytrader420
|
|
May 22, 2013, 10:17:31 PM |
|
If you have >1000 Khash/s just keep solo mining. You still find an average of 9 blocks in 24 hours at current difficulty with 1000 Khash/s No pool fees, no DDOS, no pool crashes, etc. Just went back on mining solo again I'm pretty sure its less than that. Difficulty is 2.22 (last i checked). It should take only about 4 hrs to find a block with 600 kh/s at current difficulty. SOLO mine away !
|
|
|
|
MinerLT
|
|
May 22, 2013, 10:19:44 PM |
|
I bet we will see this coin on bter.com even better on mcxnow.com
|
Success doesn't come to you…you go to it
|
|
|
cryptohunter
Legendary
Offline
Activity: 2100
Merit: 1167
MY RED TRUST LEFT BY SCUMBAGS - READ MY SIG
|
|
May 22, 2013, 10:20:44 PM |
|
POKER CRASHED AGAIN GRRRRR what is wrong why does it keep crashing?
|
|
|
|
daytrader420
|
|
May 22, 2013, 10:25:38 PM |
|
I bet we will see this coin on bter.com even better on mcxnow.com Better than that, I'll bet you see this coin have a longer lifespan than every other scrypt-alt since Litecoin.
|
|
|
|
nulo0b
|
|
May 22, 2013, 10:28:03 PM |
|
POKER CRASHED AGAIN GRRRRR what is wrong why does it keep crashing?
Did you not played the whole match out? I think its get blocked by the new one that pops...
|
|
|
|
cryptohunter
Legendary
Offline
Activity: 2100
Merit: 1167
MY RED TRUST LEFT BY SCUMBAGS - READ MY SIG
|
|
May 22, 2013, 10:30:52 PM |
|
POKER CRASHED AGAIN GRRRRR what is wrong why does it keep crashing?
Did you not played the whole match out? I think its get blocked by the new one that pops... no , so annoying to play up all that time then it crashes they need to fix that asap, it's stupid the game gets destroyed because a new one starts also just freezes up .
|
|
|
|
nulo0b
|
|
May 22, 2013, 10:41:00 PM |
|
Arggh, thats bad tbh...
Now more and more peeps, find the way to the pokersite
|
|
|
|
TheFuneral
|
|
May 22, 2013, 10:48:37 PM Last edit: May 22, 2013, 11:08:25 PM by TheFuneral |
|
If you have >1000 Khash/s just keep solo mining. You still find an average of 9 blocks in 24 hours at current difficulty with 1000 Khash/s No pool fees, no DDOS, no pool crashes, etc. Just went back on mining solo again I'm pretty sure its less than that. Difficulty is 2.22 (last i checked). It should take only about 4 hrs to find a block with 600 kh/s at current difficulty. SOLO mine away ! How do I tell if I have set it up correctly without waiting for an entirely new block? cgminer currently says New Block Detected on network. Does that mean it's workign correctly? How will it know where to payout? I assume 127.0.0.1 is your computers localhost and we should use what we get from cmd>ipconfig instead?
|
|
|
|
YaCoinYeah
Newbie
Offline
Activity: 42
Merit: 0
|
|
May 22, 2013, 10:56:49 PM |
|
Wish iamatrix and John would wake up and start posting. They have a lot to say
|
|
|
|
nulo0b
|
|
May 22, 2013, 10:59:02 PM |
|
you know something more?
|
|
|
|
Scooby903
|
|
May 22, 2013, 11:02:16 PM |
|
If you have >1000 Khash/s just keep solo mining. You still find an average of 9 blocks in 24 hours at current difficulty with 1000 Khash/s No pool fees, no DDOS, no pool crashes, etc. Just went back on mining solo again I'm pretty sure its less than that. Difficulty is 2.22 (last i checked). It should take only about 4 hrs to find a block with 600 kh/s at current difficulty. SOLO mine away ! Is there a dummies guide to setting up solominig? Everytime I try to start the server it tells me I need a rpcpassword even though I have one set in my .conf file; # listen=1 upnp=1 rpcuser=YourUserName rpcpassword=YourPassword rpcallowip=* rpcport=9554 rpcconnect=* daemon=1 server=1 gen=0 # What am I doing wrong? I had some issues with this as well...I was putting the .conf file in with the qt.exe and it needs to be in the roaming\appdata folder...
|
|
|
|
cryptohunter
Legendary
Offline
Activity: 2100
Merit: 1167
MY RED TRUST LEFT BY SCUMBAGS - READ MY SIG
|
|
May 22, 2013, 11:04:27 PM |
|
Wish iamatrix and John would wake up and start posting. They have a lot to say
Tell us ? what do you mean.?
|
|
|
|
MrSike
Member
Offline
Activity: 63
Merit: 10
I do not support any of these 3 coins in my avatar
|
|
May 22, 2013, 11:05:58 PM |
|
If you have >1000 Khash/s just keep solo mining. You still find an average of 9 blocks in 24 hours at current difficulty with 1000 Khash/s No pool fees, no DDOS, no pool crashes, etc. Just went back on mining solo again I'm pretty sure its less than that. Difficulty is 2.22 (last i checked). It should take only about 4 hrs to find a block with 600 kh/s at current difficulty. SOLO mine away ! Is there a dummies guide to setting up solominig? Everytime I try to start the server it tells me I need a rpcpassword even though I have one set in my .conf file; # listen=1 upnp=1 rpcuser=YourUserName rpcpassword=YourPassword rpcallowip=* rpcport=9554 rpcconnect=* daemon=1 server=1 gen=0 # What am I doing wrong? Often that error pops up when the file is saved as .conf.txt, make sure it's just .conf
|
BTC: 1167XUNMF95xpRvQphKnKXPiJmP16cgTpm MRO: 49BqijXcCU4MGfp2PGpqETNnX4yjrx9ZNj8TiKUj2N1kAZmY3A5cmHfiDGHnnTDiwbfmE7MZYDrSATz 2AN1JQvtWGVm6MJ6
|
|
|
TheFuneral
|
|
May 22, 2013, 11:08:51 PM |
|
If you have >1000 Khash/s just keep solo mining. You still find an average of 9 blocks in 24 hours at current difficulty with 1000 Khash/s No pool fees, no DDOS, no pool crashes, etc. Just went back on mining solo again I'm pretty sure its less than that. Difficulty is 2.22 (last i checked). It should take only about 4 hrs to find a block with 600 kh/s at current difficulty. SOLO mine away ! Is there a dummies guide to setting up solominig? Everytime I try to start the server it tells me I need a rpcpassword even though I have one set in my .conf file; # listen=1 upnp=1 rpcuser=YourUserName rpcpassword=YourPassword rpcallowip=* rpcport=9554 rpcconnect=* daemon=1 server=1 gen=0 # What am I doing wrong? Often that error pops up when the file is saved as .conf.txt, make sure it's just .conf How do I tell if I have set it up correctly without waiting for an entirely new block? cgminer currently says New Block Detected on network. Does that mean it's workign correctly? How will it know where to payout? I assume 127.0.0.1 is your computers localhost and we should use what we get from cmd>ipconfig instead?
|
|
|
|
MrSike
Member
Offline
Activity: 63
Merit: 10
I do not support any of these 3 coins in my avatar
|
|
May 22, 2013, 11:11:50 PM |
|
If you have >1000 Khash/s just keep solo mining. You still find an average of 9 blocks in 24 hours at current difficulty with 1000 Khash/s No pool fees, no DDOS, no pool crashes, etc. Just went back on mining solo again I'm pretty sure its less than that. Difficulty is 2.22 (last i checked). It should take only about 4 hrs to find a block with 600 kh/s at current difficulty. SOLO mine away ! Is there a dummies guide to setting up solominig? Everytime I try to start the server it tells me I need a rpcpassword even though I have one set in my .conf file; # listen=1 upnp=1 rpcuser=YourUserName rpcpassword=YourPassword rpcallowip=* rpcport=9554 rpcconnect=* daemon=1 server=1 gen=0 # What am I doing wrong? Often that error pops up when the file is saved as .conf.txt, make sure it's just .conf How do I tell if I have set it up correctly without waiting for an entirely new block? cgminer currently says New Block Detected on network. Does that mean it's workign correctly? How will it know where to payout? I assume 127.0.0.1 is your computers localhost and we should use what we get from cmd>ipconfig instead? "New block detected" that means another miner found the block, so you receive no reward. 127.0.0.1 is good. Seems like you are solo mining just fine, once you solve your first block it is very exciting! Edit: It will know where to pay out because you should be using your wallet as a server. It will automatically pay out to an address in it when a block is solved.
|
BTC: 1167XUNMF95xpRvQphKnKXPiJmP16cgTpm MRO: 49BqijXcCU4MGfp2PGpqETNnX4yjrx9ZNj8TiKUj2N1kAZmY3A5cmHfiDGHnnTDiwbfmE7MZYDrSATz 2AN1JQvtWGVm6MJ6
|
|
|
JohnCar (OP)
|
|
May 22, 2013, 11:12:08 PM |
|
Wish iamatrix and John would wake up and start posting. They have a lot to say
I am here and Mike is looking at code for poker site whats up?
|
TIT coming soon..............
|
|
|
TheFuneral
|
|
May 22, 2013, 11:13:11 PM |
|
If you have >1000 Khash/s just keep solo mining. You still find an average of 9 blocks in 24 hours at current difficulty with 1000 Khash/s No pool fees, no DDOS, no pool crashes, etc. Just went back on mining solo again I'm pretty sure its less than that. Difficulty is 2.22 (last i checked). It should take only about 4 hrs to find a block with 600 kh/s at current difficulty. SOLO mine away ! Is there a dummies guide to setting up solominig? Everytime I try to start the server it tells me I need a rpcpassword even though I have one set in my .conf file; # listen=1 upnp=1 rpcuser=YourUserName rpcpassword=YourPassword rpcallowip=* rpcport=9554 rpcconnect=* daemon=1 server=1 gen=0 # What am I doing wrong? Often that error pops up when the file is saved as .conf.txt, make sure it's just .conf How do I tell if I have set it up correctly without waiting for an entirely new block? cgminer currently says New Block Detected on network. Does that mean it's workign correctly? How will it know where to payout? I assume 127.0.0.1 is your computers localhost and we should use what we get from cmd>ipconfig instead? "New block detected" that means another miner found the block, so you receive no reward. 127.0.0.1 is good. Seems like you are solo mining just fine, once you solve your first block it is very exciting! how will I know and how long should I expect to wait if I have 2500Kh/s ?
|
|
|
|
|