I tried to change the minimum difficulty on my workers and got the following error - "There was an error updating at least 1 Stratum server. Please try again." Is anyone else getting this or is it just me??
***EDIT*** Just tried again and it worked this time. I didn't make any changes on my end so guess it cleared itself.
Topic: [CLOSED] BTC Guild - Pays TxFees+NMC, Stratum, VarDiff, Private Servers - page 148. (Read 903163 times)
January 17, 2014, 12:36:25 AM
January 17, 2014, 12:05:54 AM
DVC/IXC are likely coming near the end of the month. Not a high priority (they're essentially worthless). I've been finishing up the new stratum backend this week, and have now done a full test for share submissions/logging and solving blocks on testnet. It has also been holding strong on the botnet/ddos filtering server, with very low resource usage. It will likely be going live on one of the BTC Guild backend servers tomorrow, and once it has solved a few blocks, live on the remaining backends.
January 16, 2014, 11:39:07 PM
can BTCguild get merged mining for DEV/Ixo like cex has?
It's in the works. Please read the last 2 pages for further details.
January 16, 2014, 11:13:19 PM
can BTCguild get merged mining for DEV/Ixo like cex has?
January 16, 2014, 02:42:26 PM
EDIT: Rewritten to reflect updated information
The "Block Rewards" table is a calculated value, since your actual rewards are determined by the shift payments. It's fairly accurate, usually within a few decimals (normally past the ones displayed since rewards are tracked out to 14 decimals).
It looks like the block in question was recorded twice. This was likely due to bitcoind being extremely slow (it's time to defrag the payout wallet). I've tweaked the table where it records blocks to prevent a block from showing up twice.
Since the Block Rewards table is keyed based on the Block #, but the payouts are keyed based on an internal ID, it was looking up the rewards for the block twice (since it was recorded twice), but only used one ID, resulting in only half the reward being displayed.
I've removed the double-payment of that block, and the value in the Block Rewards table should now be showing up correctly.
The "Block Rewards" table is a calculated value, since your actual rewards are determined by the shift payments. It's fairly accurate, usually within a few decimals (normally past the ones displayed since rewards are tracked out to 14 decimals).
It looks like the block in question was recorded twice. This was likely due to bitcoind being extremely slow (it's time to defrag the payout wallet). I've tweaked the table where it records blocks to prevent a block from showing up twice.
Since the Block Rewards table is keyed based on the Block #, but the payouts are keyed based on an internal ID, it was looking up the rewards for the block twice (since it was recorded twice), but only used one ID, resulting in only half the reward being displayed.
I've removed the double-payment of that block, and the value in the Block Rewards table should now be showing up correctly.
January 16, 2014, 02:13:45 PM
same here , the block in question only rewarded about half of what I usually get.
January 16, 2014, 01:34:15 PM
Does anybody else see something wonky with the PPLNS payout of block 280856?
I've been mining with a constant hashrate past 24 hours or so, and this block is showing half the normal payout of the rest? Just wondering if this is a display glitch, a calculation glitch, or if there's a legitimate reason.
(EDIT: corrected to PPLNS, not pps)
I've been mining with a constant hashrate past 24 hours or so, and this block is showing half the normal payout of the rest? Just wondering if this is a display glitch, a calculation glitch, or if there's a legitimate reason.
(EDIT: corrected to PPLNS, not pps)
Same here. Block 280856 payout is only half what it should be. My hashrate has not changed and my submitted shares per PPLNS shift did not go down but it show my contribution % and payout for the block as only half of what it should be.
Well glad it's not just me.
In other news, I checked all the open shifts and the block shows there as a full payout, in all of them, so I'm willing to bet it's just a display glitch. We'll see what happens after the next found block I suppose.
January 16, 2014, 01:18:38 PM
Does anybody else see something wonky with the PPLNS payout of block 280856?
I've been mining with a constant hashrate past 24 hours or so, and this block is showing half the normal payout of the rest? Just wondering if this is a display glitch, a calculation glitch, or if there's a legitimate reason.
(EDIT: corrected to PPLNS, not pps)
I've been mining with a constant hashrate past 24 hours or so, and this block is showing half the normal payout of the rest? Just wondering if this is a display glitch, a calculation glitch, or if there's a legitimate reason.
(EDIT: corrected to PPLNS, not pps)
Same here. Block 280856 payout is only half what it should be. My hashrate has not changed and my submitted shares per PPLNS shift did not go down but it show my contribution % and payout for the block as only half of what it should be.
January 16, 2014, 01:11:22 PM
Does anybody else see something wonky with the PPLNS payout of block 280856?
I've been mining with a constant hashrate past 24 hours or so, and this block is showing half the normal payout of the rest? Just wondering if this is a display glitch, a calculation glitch, or if there's a legitimate reason.
(EDIT: corrected to PPLNS, not pps)
I've been mining with a constant hashrate past 24 hours or so, and this block is showing half the normal payout of the rest? Just wondering if this is a display glitch, a calculation glitch, or if there's a legitimate reason.
(EDIT: corrected to PPLNS, not pps)
January 16, 2014, 12:32:45 PM
I just got a new miner last night and was having trouble getting it to stay connected to the pool. I tried both the US and EU URL's but it would mine for 5 to 10 minutes and then stop. I tried several times and was worried I got hosed on this one. I tried connecting it to another pool and it stayed running just fine over night to current. Not sure what could be going on, my other miners have been connected for the last week without issues. Just thought I'd report it, I'm going to try connecting back here tonight when I get home from work.
January 16, 2014, 10:35:09 AM
I'm running from CA on US servers and not experiencing any problems or drops in hashrate.
January 15, 2014, 09:05:11 PM
The fact is people who mine with their own equipment pay 0 fees. Whatever I mine with my share of the pool I withdraw at 100%.
No you don't. You pay a withdrawal fee.
January 15, 2014, 08:47:34 PM
Alright damn it. I'm a dick, but I'll apologize for being one last night. Me and the wife had a horrible argument that set me off and she's the only one in this world that knows how to press my buttons. Compounding my misery last night I also had a 4TB hard drive die on my media server which caused a big headache. Then to finally sit down and apply a new shiney firmware to my miner only to not able to connect to the Guild was too much for me to handle. It was just a really bad night.
more like it
welcome back
January 15, 2014, 07:54:05 PM
Hey eleuthria,
Not sure what PM notifications you have set but I sent ya somethin I think it was last night / early today... Ty.
Not sure what PM notifications you have set but I sent ya somethin I think it was last night / early today... Ty.
PM answered. Clicked it last night and it was on a new page so I missed the previous page of messages.
January 15, 2014, 07:29:18 PM
Hey eleuthria,
Not sure what PM notifications you have set but I sent ya somethin I think it was last night / early today... Ty.
Not sure what PM notifications you have set but I sent ya somethin I think it was last night / early today... Ty.
January 15, 2014, 04:42:18 PM
How come BTC Guild reports much higher hashing rate when I'm connected to the EU server then the US server? I'm located in the Northeast of the US.
It wouldn't...either you're comparing bad numbers (one with downtime in the average window), or "much higher" is only a few %, which is standard variance.
January 15, 2014, 04:21:27 PM
How come BTC Guild reports much higher hashing rate when I'm connected to the EU server then the US server? I'm located in the Northeast of the US.
January 15, 2014, 01:21:50 PM
Alright damn it. I'm a dick, but I'll apologize for being one last night. Me and the wife had a horrible argument that set me off and she's the only one in this world that knows how to press my buttons. Compounding my misery last night I also had a 4TB hard drive die on my media server which caused a big headache. Then to finally sit down and apply a new shiney firmware to my miner only to not able to connect to the Guild was too much for me to handle. It was just a really bad night.
Could've been worse. Try being in my shoes where I was too sick to get out of bed for more than a few minutes at a time, and there weren't any signs of issues I could identify via my phone until a few hours after it started (due to the fact that it was only stopping new/restarted connections).
The private servers have been around with BTC Guild, and actually quite a few other pools have had them as well, for over a year. Whenever a strong, persistent DDoS hits, one of the first things pools do is try to get a server running and slowly spread the connection information to users with a long history, or a high speed. BTC Guild pre-emptively gives out this information to high end accounts. The logic is pretty simple: The more you have invested, the more downtime hurts you. Obviously it's in my best interests AND the user's best interest to have a server designated for those types of clients.
There have also been semi-private (designated this way because the criteria for receiving them was not strict) servers distributed during previous attacks, most of which are still online and available to this day.
January 15, 2014, 11:56:37 AM
Alright damn it. I'm a dick, but I'll apologize for being one last night. Me and the wife had a horrible argument that set me off and she's the only one in this world that knows how to press my buttons. Compounding my misery last night I also had a 4TB hard drive die on my media server which caused a big headache. Then to finally sit down and apply a new shiney firmware to my miner only to not able to connect to the Guild was too much for me to handle. It was just a really bad night.
Sorry for calling you a dick, lol. But you do see in the title of this thread "private servers"? It's not like it is a hidden feature of BTCGuild. So your rant did seem to be a bit over-the-top.
January 15, 2014, 11:25:16 AM
Alright damn it. I'm a dick, but I'll apologize for being one last night. Me and the wife had a horrible argument that set me off and she's the only one in this world that knows how to press my buttons. Compounding my misery last night I also had a 4TB hard drive die on my media server which caused a big headache. Then to finally sit down and apply a new shiney firmware to my miner only to not able to connect to the Guild was too much for me to handle. It was just a really bad night.
You could have had the EU server as failover/backup and you would have been fine, it would have just switched over when the US frontend server went kablooey.
Jump to: