Topic: [CLOSED] BTC Guild - Pays TxFees+NMC, Stratum, VarDiff, Private Servers - page 371. (Read 903150 times)
October 11, 2012, 10:34:07 AM
CGminer 2.8.2 is broke for my FPGA Single and many others report the same https://bitcointalk.org/index.php?topic=28402.7540
October 11, 2012, 06:54:28 AM
Liked it better that way!
Fine, I restored the original response
. 
October 11, 2012, 06:21:20 AM
Riiiiiiiiiiiiiight - trap all small miners into your stupid pool in order to prevent blockchain from becoming bloated. Fuck you!
I swear - if someone gives me a button which would permanently eliminate current and any future pool owners, I'd press
it right now. What next showoff of your power we can expect? Miners with less than 1 GHash/sec can't join? Fuck you!
I swear - if someone gives me a button which would permanently eliminate current and any future pool owners, I'd press
it right now. What next showoff of your power we can expect? Miners with less than 1 GHash/sec can't join? Fuck you!
You're welcome to fuck off and mine solo. If 0.10 BTC is too much for a miner to accumulate before needing to withdraw, then maybe they should reconsider mining, since they're obviously losing money by doing so. I gave recommended numbers, not mandatory amounts.
Liked it better that way!
October 11, 2012, 05:15:18 AM
WARNING TO CGMINER USERS
A bug has been reported by two users so far with cgminer 2.8.1. This bug is so far only being shown to affect workers that are very fast (> 4 GH/s). There seems to be a bug in cgminer 2.8.1's difficulty targetting, and when a miner either hits difficulty=4, or is supposed to hit difficulty=8 (not yet confirmed which part is causing the problem), it is having drastically reduced share submissions.
If you are having this problem, downgrade to a 2.7.x version of cgminer and use the stratum proxy, or regular getwork pools. I've posted on the cgminer thread and am waiting for a response from ckolivas.
There is a hotfix update of cgminer to version 2.8.2 which fixes this bug. Anyone mining on btcguild with cgminer 2.8.0 or 2.8.1 is strongly encouraged to update. A bug has been reported by two users so far with cgminer 2.8.1. This bug is so far only being shown to affect workers that are very fast (> 4 GH/s). There seems to be a bug in cgminer 2.8.1's difficulty targetting, and when a miner either hits difficulty=4, or is supposed to hit difficulty=8 (not yet confirmed which part is causing the problem), it is having drastically reduced share submissions.
If you are having this problem, downgrade to a 2.7.x version of cgminer and use the stratum proxy, or regular getwork pools. I've posted on the cgminer thread and am waiting for a response from ckolivas.
October 10, 2012, 08:20:09 PM
Riiiiiiiiiiiiiight - trap all small miners into your stupid pool in order to prevent blockchain from becoming bloated. Fuck you!
I swear - if someone gives me a button which would permanently eliminate current and any future pool owners, I'd press
it right now. What next showoff of your power we can expect? Miners with less than 1 GHash/sec can't join? Fuck you!
I swear - if someone gives me a button which would permanently eliminate current and any future pool owners, I'd press
it right now. What next showoff of your power we can expect? Miners with less than 1 GHash/sec can't join? Fuck you!
You're welcome to fuck off and mine solo. If 0.10 BTC is too much for a miner to accumulate before needing to withdraw, then maybe they should reconsider mining, since they're obviously losing money by doing so. I gave recommended numbers, not mandatory amounts.
October 10, 2012, 08:03:50 PM
The payout minimum will not be lowered any time soon. If it does, there will be a fee attached to requesting such a small payout, because I will not be the one paying the transaction fee in order to send somebody a payout that is worth less than $1.
As a long time user of Bitcoin and a developer: Thank you for taking a firm position against making dust payouts. Blockchain bloat is no one's friend, and tiny outputs will likely never get spent— meaning they'll bloat the txout set perpetually.Can that be remedied by sending all coins from one wallet to another in one transaction? Also what is the recommended payout size? I've heard 1 BTC is good.
Thanks,
Sam
I've always felt the best setting for automatic payments to be the greater of: 1 BTC or your weekly mining revenue. Think of it as your weekly mining paycheck.
Riiiiiiiiiiiiiight - trap all small miners into your stupid pool in order to prevent blockchain from becoming bloated. Fuck you!
I swear - if someone gives me a button which would permanently eliminate current and any future pool owners, I'd press
it right now. What next showoff of your power we can expect? Miners with less than 1 GHash/sec can't join? Fuck you!
Now you've gone a bit beyond ridiculous.
Don't know if you've been keeping tabs on what's going to be happening to the network hash rate, but, in 2 or 3 months 1Ghs will be a smaller percentage your 35Mhs/s 4670 is now. And he won't be barring small hash rate miners.
Sam
October 10, 2012, 07:20:29 PM
The payout minimum will not be lowered any time soon. If it does, there will be a fee attached to requesting such a small payout, because I will not be the one paying the transaction fee in order to send somebody a payout that is worth less than $1.
As a long time user of Bitcoin and a developer: Thank you for taking a firm position against making dust payouts. Blockchain bloat is no one's friend, and tiny outputs will likely never get spent— meaning they'll bloat the txout set perpetually.Can that be remedied by sending all coins from one wallet to another in one transaction? Also what is the recommended payout size? I've heard 1 BTC is good.
Thanks,
Sam
I've always felt the best setting for automatic payments to be the greater of: 1 BTC or your weekly mining revenue. Think of it as your weekly mining paycheck.
And your weekly mining earnings variance will be minimal.
October 10, 2012, 07:19:24 PM
The payout minimum will not be lowered any time soon. If it does, there will be a fee attached to requesting such a small payout, because I will not be the one paying the transaction fee in order to send somebody a payout that is worth less than $1.
As a long time user of Bitcoin and a developer: Thank you for taking a firm position against making dust payouts. Blockchain bloat is no one's friend, and tiny outputs will likely never get spent— meaning they'll bloat the txout set perpetually.Can that be remedied by sending all coins from one wallet to another in one transaction? Also what is the recommended payout size? I've heard 1 BTC is good.
Thanks,
Sam
I've always felt the best setting for automatic payments to be the greater of: 1 BTC or your weekly mining revenue. Think of it as your weekly mining paycheck.
October 10, 2012, 05:55:45 PM
As a long time user of Bitcoin and a developer: Thank you for taking a firm position against making dust payouts. Blockchain bloat is no one's friend, and tiny outputs will likely never get spent— meaning they'll bloat the txout set perpetually.
On the other hand, thanks to sites like Satoshi dice or Deepbit, bitcoin client get drastically improved in the area of tx processing and a lot of other major improvements are coming thanks to unbelievable effort of core developers. Although I'm not a fan of bloating blockchain, these things definitely help whole project move forward its prime time...
October 10, 2012, 05:55:34 PM
The payout minimum will not be lowered any time soon. If it does, there will be a fee attached to requesting such a small payout, because I will not be the one paying the transaction fee in order to send somebody a payout that is worth less than $1.
As a long time user of Bitcoin and a developer: Thank you for taking a firm position against making dust payouts. Blockchain bloat is no one's friend, and tiny outputs will likely never get spent— meaning they'll bloat the txout set perpetually.Can that be remedied by sending all coins from one wallet to another in one transaction? Also what is the recommended payout size? I've heard 1 BTC is good.
Thanks,
Sam
October 10, 2012, 05:49:09 PM
The payout minimum will not be lowered any time soon. If it does, there will be a fee attached to requesting such a small payout, because I will not be the one paying the transaction fee in order to send somebody a payout that is worth less than $1.
As a long time user of Bitcoin and a developer: Thank you for taking a firm position against making dust payouts. Blockchain bloat is no one's friend, and tiny outputs will likely never get spent— meaning they'll bloat the txout set perpetually.
October 10, 2012, 04:43:37 PM
WARNING TO CGMINER USERS
A bug has been reported by two users so far with cgminer 2.8.1. This bug is so far only being shown to affect workers that are very fast (> 4 GH/s). There seems to be a bug in cgminer 2.8.1's difficulty targetting, and when a miner either hits difficulty=4, or is supposed to hit difficulty=8 (not yet confirmed which part is causing the problem), it is having drastically reduced share submissions.
If you are having this problem, downgrade to a 2.7.x version of cgminer and use the stratum proxy, or regular getwork pools. I've posted on the cgminer thread and am waiting for a response from ckolivas.
A bug has been reported by two users so far with cgminer 2.8.1. This bug is so far only being shown to affect workers that are very fast (> 4 GH/s). There seems to be a bug in cgminer 2.8.1's difficulty targetting, and when a miner either hits difficulty=4, or is supposed to hit difficulty=8 (not yet confirmed which part is causing the problem), it is having drastically reduced share submissions.
If you are having this problem, downgrade to a 2.7.x version of cgminer and use the stratum proxy, or regular getwork pools. I've posted on the cgminer thread and am waiting for a response from ckolivas.
Something else I noticed with the issue was the cgminer console looked fine, as in it reported your normal hash rate consistantly. When I would look on the Worker Summary page it would get slower and slower over 10 min or so. Switched back to cgminer 2.7.7 and Stratum Proxy 1.0.2 and all is well. For those needing the latest Stratum proxy, it's here: https://github.com/slush0/stratum-mining-proxy
October 10, 2012, 03:34:15 PM
WARNING TO CGMINER USERS
A bug has been reported by two users so far with cgminer 2.8.1. This bug is so far only being shown to affect workers that are very fast (> 4 GH/s). There seems to be a bug in cgminer 2.8.1's difficulty targetting, and when a miner either hits difficulty=4, or is supposed to hit difficulty=8 (not yet confirmed which part is causing the problem), it is having drastically reduced share submissions.
If you are having this problem, downgrade to a 2.7.x version of cgminer and use the stratum proxy, or regular getwork pools. I've posted on the cgminer thread and am waiting for a response from ckolivas.
A bug has been reported by two users so far with cgminer 2.8.1. This bug is so far only being shown to affect workers that are very fast (> 4 GH/s). There seems to be a bug in cgminer 2.8.1's difficulty targetting, and when a miner either hits difficulty=4, or is supposed to hit difficulty=8 (not yet confirmed which part is causing the problem), it is having drastically reduced share submissions.
If you are having this problem, downgrade to a 2.7.x version of cgminer and use the stratum proxy, or regular getwork pools. I've posted on the cgminer thread and am waiting for a response from ckolivas.
October 10, 2012, 01:12:54 PM
For those who haven't read it yet, organofcorti has a writeup about variable difficulty found here: http://organofcorti.blogspot.com/2012/10/71-variable-pool-difficulty.html
For a summary of the BTC Guild effects:
BTC Guild has a target share rate of 12-19 shares per minute. This means your hourly variance should be between -7% to +7%. Daily variance should be between -1.5% to 1.5%. This is assuming you are at the low end (12 shares per minute).
This only affects users that have enough speed to require a difficulty greater than 1. For users still at difficulty=1, the individual miner variance is no different than what you would have had before Stratum on any other PPS pool.
For a summary of the BTC Guild effects:
BTC Guild has a target share rate of 12-19 shares per minute. This means your hourly variance should be between -7% to +7%. Daily variance should be between -1.5% to 1.5%. This is assuming you are at the low end (12 shares per minute).
This only affects users that have enough speed to require a difficulty greater than 1. For users still at difficulty=1, the individual miner variance is no different than what you would have had before Stratum on any other PPS pool.
October 10, 2012, 12:29:37 PM
I haven't used the new cgminer on Windows (my only miners use Linux). Are you using 2.8.0 or 2.8.1? I know 2.8.0 had issues if there's any kind of connection trouble between you and the server.
2.8.1 for the last 4 hours there wasn't a problem.
October 10, 2012, 11:52:15 AM
I'm an idiot (again). It was fault in my code.
October 10, 2012, 11:26:41 AM
Did you cut off the worker part of your command line? Because -u averwind is not a valid worker (you're missing _[workername]).
Yeah I intentionally cut it. The statistics and everything was showing that all was fine for 5 hours than suddenly I got the windows message telling me nothing.
I haven't used the new cgminer on Windows (my only miners use Linux). Are you using 2.8.0 or 2.8.1? I know 2.8.0 had issues if there's any kind of connection trouble between you and the server.
October 10, 2012, 11:18:28 AM
Did you cut off the worker part of your command line? Because -u averwind is not a valid worker (you're missing _[workername]).
Yeah I intentionally cut it. The statistics and everything was showing that all was fine for 5 hours than suddenly I got the windows message telling me nothing.
October 10, 2012, 11:09:59 AM
Following is how I am using the new stratum version:
cgminer -o btcguild.com:8332 -u averwind -p x -I 9 -v 2 -w 128
I have 10miners and all of them had the same windows message this morning "cgminer has stopped working". I will give it another go but this just doesn't look good...
cgminer -o btcguild.com:8332 -u averwind -p x -I 9 -v 2 -w 128
I have 10miners and all of them had the same windows message this morning "cgminer has stopped working". I will give it another go but this just doesn't look good...
Did you cut off the worker part of your command line? Because -u averwind is not a valid worker (you're missing _[workername]).
October 10, 2012, 07:27:17 AM
Following is how I am using the new stratum version:
cgminer -o btcguild.com:8332 -u averwind -p x -I 9 -v 2 -w 128
I have 10miners and all of them had the same windows message this morning "cgminer has stopped working". I will give it another go but this just doesn't look good...
cgminer -o btcguild.com:8332 -u averwind -p x -I 9 -v 2 -w 128
I have 10miners and all of them had the same windows message this morning "cgminer has stopped working". I will give it another go but this just doesn't look good...
Jump to: