[CLOSED] BTC Guild - Pays TxFees+NMC, Stratum, VarDiff, Private Servers

[eleuthria]

I've fixed a small problem with automatic payouts.  After enabling lower amounts to be included in automatic payouts, the code was hitting 50 payouts at once, which was a limit I had hardcoded into the automatic payouts.  I've split how the automatic payouts are processed to give priority to larger payouts, but also set it to run more than once per hour if it hits a backlog.

As a result of this fix, some users may have noticed they received automatic payouts at an odd time, or multiple payouts for users who hadn't had a payout processed automatically in a while.  Going forward things should be functioning normally .

[1713936450]

1713936450

[1713936450]

1713936450

[1713936450]

1713936450

[eleuthria]

I apologize for EU Stratum having issues in the last 24 hours.  I've migrated eu-stratum.btcguild.com to another server in the last 15 minutes, and hopefully the new server will be stable while the DNS is pointed there.  It is temporarily not in the EU unfortunately.  However, I will be moving it back overseas as soon as possible.

[tnkflx]

I'm using stratum-mining-proxy and getting a lot of dupes on the BTC Guild site. Any idea why this is?

[eleuthria]

I'm using stratum-mining-proxy and getting a lot of dupes on the BTC Guild site. Any idea why this is?

Are you mining on FPGAs?  I've found that many FPGAs submit a significant number of dupes.  However, they are simply resubmitting a share more than once, rather than wasting time on duplicated work, and their accepted share rate still matches the expected speed.  Different miner versions have also had more or less (cgminer/bfgminer on ztex chips seem to bounce between no dupes and lots of dupes with each version update).

[Fiyasko]

Stats are messed up.

[eleuthria]

Stats are messed up.

Please provide details on what is wrong when posting something like this.  I can't really do anything when I have no idea what you're referring to.

[eleuthria]

Upcoming Changes To Payouts

As difficulty rises and still more miners come online, it is becoming very frequent for members to request payouts that are extremely small in size (under 0.10).  As a result, the pool is constantly churning through coins which have had confirmations, reducing the priority of the transactions, which means they often take longer to receive the first confirmation.  When the network has bad luck, it is sometimes the case where the pool has 30 or 40 payouts without confirmations, and some of them are waiting for a handful of other transactions which are the source for their inputs.


Later this weekend, small payouts (less than 0.10) will no longer be available for Instant Withdrawal.  Instead, these payouts will enter 'Pending' status.  Every 30 minutes, pending payouts will be grouped together and sent as a single "sendtomany" payment, similar to what is done with automatic payouts already.

Please note that for very small payouts, it is not rare for you to have to wait 30-60 minutes for the first confirmation in the first place, so this change should not have any significant change to confirmation times of payouts, and may actually improve the speed of confirmations for all users (both small and large) due to not eating through as many pre-confirmed coins.

[eleuthria]

Getwork (regular and merged mining) servers are being restarted to try to force miners to connect to the proper servers after some migrations and DNS changes.  It should be available again within the next 30 minutes, hopefully faster!

[pazor]

stratum and mergedmining, is this possible (btc+nmc) ?

[eleuthria]

stratum and mergedmining, is this possible (btc+nmc) ?

I have no plans to rewrite my Stratum code to add dependency on namecoind (which is extremely outdated) and rewrite the coinbase creation to add merged mining.

[eleuthria]

Sorry for the long reload of the getwork servers.  The restart process of the server is very slow due to worker authorization + prioritization of already authorized workers.  It means after the first few get in, it gets slower and slower at letting new workers get authorized.  As a result, restarting the server is taking a significant amount of time for some users to resume working.

I've made a few tweaks to the configuration, but I'm limited on how much I can do with getwork.  This is one of the reasons I encourage all users to upgrade to Stratum.  With Stratum, I designed the pool software myself, I can find and easily fix bottleneck issues.  With getwork, that is not an option, I can only fiddle with a few settings and make tweaks.  Major overhauls of the design are not possible since I am extremely limited in my knowledge of Java.  Miners get the side benefit of Stratum being a significantly more efficient protocol as well.

[eleuthria]

Merged Mining should be stable again shortly.  I was up til 3 AM trying to get it to handle the new load, and at the time I went to sleep it seemed to be doing so.  However, sometime during the night it failed and completely stopped handing out work.  It's back up now and I believe I've been able to identify what caused the major problems last night with restarting the server with so many users trying to connect at once.

At this point, I would continue to encourage miners that are stuck on getwork to consider other pool options.  At this time I simply cannot afford to toss extra servers at the getwork protocol to handle the number of users trying to utilize it.  There are plenty of other pools out there that are willing to dedicate more time to maintaining getwork based poolservers.

[Soros Shorts]

Can someone remind me what the BTC Guild API key is for? I looked at the OP as well as the online support pages but there was no mention of an API.

I need to write a program to power-cycle my Avalon when it hasn't submitted a share after X number of seconds. I can easily scrape the dashboard but I was wondering if there was a less silly way to get this information.

[eleuthria]

Can someone remind me what the BTC Guild API key is for? I looked at the OP as well as the online support pages but there was no mention of an API.

I need to write a program to power-cycle my Avalon when it hasn't submitted a share after X number of seconds. I can easily scrape the dashboard but I was wondering if there was a less silly way to get this information.

Click on the API key in the settings, it takes you to the API URL with your key, spitting out JSON for your account and worker statistics.

[Soros Shorts]

Click on the API key in the settings

Works like a charm. Apparently the link was too obvious for me to notice.

[ewibit]

I need to write a program to power-cycle my Avalon when it hasn't submitted a share after X number of seconds. I can easily scrape the dashboard but I was wondering if there was a less silly way to get this information.

will this be open source?
(and run on lucy...)
 

[eleuthria]

Click on the API key in the settings

Works like a charm. Apparently the link was too obvious for me to notice.

It's my fault for not getting back into the Support/FAQ sections and getting more documentation added.  I'm hopeful that I can get in write in some new information for users regarding the API, and also answers to common mining related issues.  If all goes well, this weekend it should start to show up in there.

[eleuthria]

Small website outage for people whose DNS updated quickly.  Website is now being proxied through a colocated server rather than an EC2 server.  Additionally, I have restored the forced-move to HTTPS for users connecting to the website without entering https://.

[Giddeon]

Hi,

I cannot change my automatic payout amount amount. It gives me the error:

"There was an error updating the database. Please try again after a few seconds."

It's been this way since I first started trying yesterday. (First time I've tried changing it for a day or two, was using manual payouts before) I want to change from 0.1 to 0.1005 so it's not like I'm using a weird amount or anything. Can you help me?

Also, you mention a 'small charge' for manual payouts, how much? Maybe I should just go back to manual payouts.


EDIT: Little update, just tried disabling automatic payouts by changing it to 0 and it worked right away. Tried changing it to 0.1005 and it it's gone to 0.1 So, I think it will only do a value of one decimal place. So I guess my question now is, how much are you charging for manual payouts?

[eleuthria]

Hi,

I cannot change my automatic payout amount amount. It gives me the error:

"There was an error updating the database. Please try again after a few seconds."

It's been this way since I first started trying yesterday. (First time I've tried changing it for a day or two, was using manual payouts before) I want to change from 0.1 to 0.1005 so it's not like I'm using a weird amount or anything. Can you help me?

Also, you mention a 'small charge' for manual payouts, how much? Maybe I should just go back to manual payouts.


EDIT: Little update, just tried disabling automatic payouts by changing it to 0 and it worked right away. Tried changing it to 0.1005 and it it's gone to 0.1 So, I think it will only do a value of one decimal place. So I guess my question now is, how much are you charging for manual payouts?

Automatic payouts are multiples of 0.01 only.  Manual payouts have no charge.  The previous post said a small chaNge .  It hasn't happened yet, but it won't involve any type of withdrawal fee.