Topic: [4+ EH] Slush Pool (slushpool.com); Overt AsicBoost; World First Mining Pool - page 1067. (Read 4382653 times)
April 27, 2011, 01:17:54 AM
He doesn't need to port forward anything for his workers. What he needs to port forward for is the bitcoin client.
April 26, 2011, 10:04:31 PM
I'm able to ping mining.bitcoin.cz from all my machines, but workers will only connect from one. I haven't tried accessing from a browser since I'm usually connected via SSH.
... what about the port forwarding to 8332 ... how does it get to both machines from the firewall/router? .. (assuming you have one)
I'm not doing any port forwarding.
well are you behind a firewall? ... help us a out bit, it sounds like a networking problem, if you tell us what your network set-up is maybe we can fix it ... don't give away much or someone might be able to hack all your rigs and take them over ... just kidding.
April 26, 2011, 08:55:54 PM
I'm able to ping mining.bitcoin.cz from all my machines, but workers will only connect from one. I haven't tried accessing from a browser since I'm usually connected via SSH.
... what about the port forwarding to 8332 ... how does it get to both machines from the firewall/router? .. (assuming you have one)
I'm not doing any port forwarding.
April 26, 2011, 08:03:48 PM
I'm able to ping mining.bitcoin.cz from all my machines, but workers will only connect from one. I haven't tried accessing from a browser since I'm usually connected via SSH.
... what about the port forwarding to 8332 ... how does it get to both machines from the firewall/router? .. (assuming you have one)
April 26, 2011, 08:02:06 PM
I'm able to ping mining.bitcoin.cz from all my machines, but workers will only connect from one. I haven't tried accessing from a browser since I'm usually connected via SSH.
April 26, 2011, 07:58:36 PM
I'm having trouble connecting with more then 1 worker. I have four instances using the same worker on one computer - they are all working fine. A worker on a different computer won't connect. If I turn off the other worker it will.
This just started last night.
This just started last night.
I am having the same problems. My second rig with four workers will not connect. I can't get to your website from that machine either. Thanks for any help.
April 26, 2011, 07:30:05 PM
I'm having trouble connecting with more then 1 worker. I have four instances using the same worker on one computer - they are all working fine. A worker on a different computer won't connect. If I turn off the other worker it will.
This just started last night.
This just started last night.
April 26, 2011, 04:03:28 PM
some of workers works? some not (problem communicating with bitcoin RPC).
April 26, 2011, 07:27:13 AM
Code:
c:\rpcminer>rpcminer-4way.exe -url http://mining.bitcoin.cz:8332 -user user -password pass
rpcminer-4way -url=http://mining.bitcoin.cz:8332 -user=user.miner1 -password=pass
ETA - just to be clearer miner1 is what I called my miner instance, it's not any sort of default. You need to go into your profile and press "register new worker" to give it a name like miner1 and a password.
April 26, 2011, 06:53:03 AM
Hello,
I am not very experienced in this bitcion setup but i have setup my accounts so far. But now when i try this pool site
with settings
i am getting this error
Is it like unable to connect to the site address or what ??
Thanks in advance.
I am not very experienced in this bitcion setup but i have setup my accounts so far. But now when i try this pool site
with settings
Code:
c:\rpcminer>rpcminer-4way.exe -url http://mining.bitcoin.cz:8332 -user user -password pass
Code:
Client will start 2 miner threads
Work will be refreshed every 4000 ms
Could not retrieve work from RPC server.
CURL return value = 3
Is it like unable to connect to the site address or what ??
Thanks in advance.
April 24, 2011, 06:38:12 PM
This should be possible, and in the limit it allows the cheater to almost double his earnings. I don't know if it was discussed before, I'll call it the "lie in wait" cheating method.
A possible countermeasure, which I don't know if is now implemented, is to keep track of the times of getwork requests, and ignore shares which were requested later than the winning share (or in the same getwork with a higher nonce).
Ok, shhhh don't say anything... some people may listen, this is the most read topic on the forum 
April 23, 2011, 02:46:51 PM
UPDATE [4/23 3:10P server]: Only 1820 into slush and have 6 stale which is about 0.33%. That is higher than it ever got in my comparisons with deepbit. A larger sample is still needed, but if I were to extrapolate this out, this still comes nowhere near the 1% difference for long polling deepbit claims. Tycho, how did you derive ~1% savings from this?
The number of stale shares has gotten a lot lower on Slush's pool lately, especially if you use a low polling value. It used to be 2-3%, but now I too get less than 1%.As of right now, I am at 0.48%. It has risen significantly. I definitely see how this may approach 1% if hit with a large chunk of work to find out it is stale. I am not sure how to change the polling rate though. I am using the poclbm miner so I assume there is a switch for that. I will have to look into it.
April 23, 2011, 12:37:13 PM
What about :
Have a big rig such that it finds a block rather often. (2-3GH/s+)
Have parts of this rig in multiple pools, with score-based and share-based reward. When the subrig on the pool with score-based reward solves a block, retain the solution for a moment. Shift all your other subrigs working on pools with share-based reward to this pool, increase your score (this is rather quick in Slush's pool) until it you reach the score corresponding to the whole rig involved. Then submit the winning solution.
You could also extend this if electricity is expensive and mining is unprofitable at times for a part of your rig, so that you have certain of your miners idle. You can then use them as extra power to increase your score for a low energy consumption, since you turn them on at the right moment, and off again.
?
This should be possible, and in the limit it allows the cheater to almost double his earnings. I don't know if it was discussed before, I'll call it the "lie in wait" cheating method.Have a big rig such that it finds a block rather often. (2-3GH/s+)
Have parts of this rig in multiple pools, with score-based and share-based reward. When the subrig on the pool with score-based reward solves a block, retain the solution for a moment. Shift all your other subrigs working on pools with share-based reward to this pool, increase your score (this is rather quick in Slush's pool) until it you reach the score corresponding to the whole rig involved. Then submit the winning solution.
You could also extend this if electricity is expensive and mining is unprofitable at times for a part of your rig, so that you have certain of your miners idle. You can then use them as extra power to increase your score for a low energy consumption, since you turn them on at the right moment, and off again.
?
A possible countermeasure, which I don't know if is now implemented, is to keep track of the times of getwork requests, and ignore shares which were requested later than the winning share (or in the same getwork with a higher nonce).
April 23, 2011, 11:50:17 AM
UPDATE [4/23 3:10P server]: Only 1820 into slush and have 6 stale which is about 0.33%. That is higher than it ever got in my comparisons with deepbit. A larger sample is still needed, but if I were to extrapolate this out, this still comes nowhere near the 1% difference for long polling deepbit claims. Tycho, how did you derive ~1% savings from this?
The number of stale shares has gotten a lot lower on Slush's pool lately, especially if you use a low polling value. It used to be 2-3%, but now I too get less than 1%. April 23, 2011, 08:28:48 AM
Yes.
From pool's home page:
"Every instance of your miner needs its own worker account!!!"
You could have also seen that your grand total hash rate was staying the same running the two PCs as the same worker, compared to only running one PC. I believe running two PCs as the same worker splits the work in half, so you were getting the same reward as you would have with just one PC. (I believe).
http://mining.bitcoin.cz/accounts/profile/worker-edit/
Anyway, register a different worker and you're fine. Edit the batch script on one of the PCs so it uses a second worker.
From pool's home page:
"Every instance of your miner needs its own worker account!!!"
You could have also seen that your grand total hash rate was staying the same running the two PCs as the same worker, compared to only running one PC. I believe running two PCs as the same worker splits the work in half, so you were getting the same reward as you would have with just one PC. (I believe).
http://mining.bitcoin.cz/accounts/profile/worker-edit/
Anyway, register a different worker and you're fine. Edit the batch script on one of the PCs so it uses a second worker.
thanks. I now have 10 worker accounts and have made a script to randomly create a number between 1 and 10, and so have a 90% chance of been logged in into 2 worker accounts.
April 23, 2011, 03:29:31 AM
Surprisingly, it hasn't made a huge difference in my comparisons. I am seeing 24 stale blocks with 9003 accepted at deepbit. 0.27% is not so different than what I saw when using slush with the same number of blocks. I will startup my slush fund again and see how it goes. I hope long polling has more benefits than I am seeing; it almost seems a bit of vapor when I compare. Maybe I need larger samples. I can say payouts have been approximately equal over time.
UPDATE [4/23 3:10P server]: Only 1820 into slush and have 6 stale which is about 0.33%. That is higher than it ever got in my comparisons with deepbit. A larger sample is still needed, but if I were to extrapolate this out, this still comes nowhere near the 1% difference for long polling deepbit claims. Tycho, how did you derive ~1% savings from this?
UPDATE [4/23 3:10P server]: Only 1820 into slush and have 6 stale which is about 0.33%. That is higher than it ever got in my comparisons with deepbit. A larger sample is still needed, but if I were to extrapolate this out, this still comes nowhere near the 1% difference for long polling deepbit claims. Tycho, how did you derive ~1% savings from this?
April 23, 2011, 02:19:08 AM
'Block #0' is fixed. Long polling - I was quite busy this month until now, I'll continue on pool improvements from next week again.
April 22, 2011, 10:01:41 PM
Yo slush, when are you going to support long polling?
April 22, 2011, 09:33:21 PM
I'm not mining anymore due to summer air conditioning, but it is nice to see the pool at ~205 GHash/sec.
Up here in the great white North, all the heat is useful about 7 months out of the year, neutral for one to two months and detrimental for the remainder. Net positive for the year however. So, the cost of electricity heating the home as opposed to the cost of using our natural gas forced air furnace is really the difference that matters on an annual basis and all I have to do is make a reasonable profit from mining that is greater than that such that it remains worth mining
I think I will be mining for quite awhile yet. All the southerners are at a huge disadvantage I think. 
April 22, 2011, 07:47:42 PM
Yeah, that's kind of worrying.
But hey, it's confirmed already!
But hey, it's confirmed already!
Jump to: