Topic: [CLOSED] BTC Guild - Pays TxFees+NMC, Stratum, VarDiff, Private Servers - page 323. (Read 903150 times)

feeling like something is broken PPLNS, does it amplify variance?

4242 7 0.00000170538367  / 354 = .48 (=52% negative variance from PPS)
4241 8 0.00000194691120 / 354 =   .55 (=45% negative variance from PPS)
 4240 9 0.00000218239581  / 354 = .615
 4239 11 0.00000266574438  / 354 = .75
 4238 13 0.00000314915633  / 354 = .89
 4237 13 0.00000314915633  /354 = .89
 4236 13 0.00000314445819  / 354 = .887

A few payouts got stuck due to the server running the hot wallet running out of memory (I blame this terrible network luck, only like 6 blocks in 3 hours).

They're being rebroadcasted with proper transaction IDs now.

 Rune Quake 3 creator Jared Larson

 http://planetquake.gamespy.com/View.php?view=MOTW.Detail&id=185

found mod files on the wayback machine ca. 8/2000

http://web.archive.org/web/20000815000000*/http://rune.lost-boys.com/news.asp

Notice to Stratum Users

Later today (exact time not yet known), there will be some restarts on Stratum servers in an effort to make BTC Guild's stratum server hostile towards botnet miners.  Part of this change is limiting the number of active connections to a single worker, and limiting how long a connection stays open without authorizing any workers.  This limit is being set relatively high, and should not impact any legitimate user.  I will post another notice when the first servers are restarted.

It is possible that this change will cause a botnet to retaliate against the servers.  Users are highly encouraged to set backup servers.  If you want to stay on btcguild, the following is a good list of backups to use before moving to another pool.

1) stratum.btcguild.com:3333  (btcguild.com:8332 for getwork)
2) eu-stratum.btcguild.com:3333 (de.btcguild.com:8332 for getwork)
3) mergedmining.btcguild.com:8332
4)


This is the first (well, first fully automated/no manual interaction) of many changes being made to make the pool more botnet hostile.  Work is starting on a smart-loadbalancer which will be used to shuffle users to different servers based on priority/risk assessment, or outright denying some workers + IP banning them.

The warnings don't disable anymore after they've been sent.  It's been that way since a few days after the new layout went online.  The emails indicated otherwise until recently, but they do not turn themselves off anymore.

I did, But at this moment BTCGuild only allows One warning Per dropped worker (and then you go re enable it)
What happened for me was that a worker dropped off, I was alerted, I was on my way to fix it (another worker drops off) and i re-enabled it (While a worker was down)
leaving me with a dead worker for 48+ hours, Im trying to pinpoint the exact time so i can figure out Why it dropped off

Yes, I see now how the graphs would help for that.

Some people have so many devices they set multiple miners to the same worker, so unless all devices associated with a worker go offline the idle warning won't go off.

Wouldn't setting an idle alert work better for that?

Could we have the ability to set custom graph sizes? Im sick of only seeing 24hr/72hr and two week. I had a miner drop off "I dont know when" becuase of this.. :\

The 'btcguild.com' getwork server was restarted, adding the X-Stratum header to the new server to push people back to Stratum if they haven't updated to the proper address (stratum.btcguild.com:3333).  Everything else appears to be functioning normally.

If your payout has a transaction ID (standard hex string of characters), it WILL arrive eventually, even if it doesn't show up on Blockchain.info yet.  There's a few factors that have really lagged up payouts getting confirms:

1) The difficulty spiked up very high, reducing the rate of BTC Guild blocks which by default include more transactions than most pools (minsize 150kb, maxsize 450kb).
2) The network as a whole is having bad luck.  We've seen multiple 40-60 minute gaps between blocks in the last 24 hours.  This means a LOT of transactions are waiting to confirm.
3) The pool is having bad luck too, which means the funds in the pool wallet do not have many confirmations.  This reduces the priority of payments coming from the pool, so they aren't always in front of the line even though they pay a fee.


Again, if you have a transactoin ID present, the payout is just stuck in limbo waiting for a confirmation.  It will eventually show up.  The only time you have to worry is if the link to the transaction is a number (like 14831), or 'MANUAL_VERIFY'.  In those cases, it is likely the payout did not go through and will need to be corrected manually.


UPDATE:  I manually rebroadcasted all "stuck" payouts since bitcoind doesn't do that very aggressively.  It looks like quite a few payouts are stuck due to a few unconfirmed inputs from about 6 hours ago.  A payout was made that did not include a fee (BTC Guild lets the stock Satoshi 0.8.1 client decide the fee).  The change address was then used as the input to push other payouts.  This caused a lot of payments to get stuck waiting for the initial transaction to get its confirmation.

UPDATE2:  A significant number of stuck payments finally got a confirmation.  Only a few remain, probably will get confirmed within the next few blocks.

Waiting 

i have the same problem.
what do I do?

UPD transaction confirmed

Same Here,
Payout triggert 4 Hours ago.
http://www.blockchain.info/tx-index/cb5f1cd15d8ca2f9577dfcdab72d673efbe3f28bfe9f31dabd2a72fa20600189
Blockchain say'd transaction no found.

Update: 21:45 MEST My wallet recieved it, but Blockchain didn't Found it yet.

Network luck hasn't been too great recently (big difficulty jump and quite a bit of speed DDoS'd offline).  I see the payout that you requested, and it will probably show up shortly.  Some bad luck on the pool (+ DDoS scaring people) means the pool funds don't have as many confirmations as you'd normally expect, which slows down confirmation times.


UPDATE: Looks like it's showing up on blockchain.info now, just waiting for confirms: https://blockchain.info/tx/8babdff48e7cee4717b069c807d228bf6de4e3ef9304d9f03a3ca2d4d7a9bcbc

Payment server issues?

I have a payout timestamp roughly 50 minutes prior to this post, yet its not showing up in the blockchain, and the transaction link returns a "transaction not found" on blockchain.info.

Sorry if this is a normal delay, relatively new to the pool, but figured it couldn't hurt to point out if there is actually a problem.

Merged mining server was restarted to fix a connection issue.  The only server that should still be seeing high packet loss is btcguild.com:8332 now.

I'm using stratum, no connection problems at all.
also the webpage (with www  ) is working fine, and FAST 
thank you

Getwork in the US is still virtually offline as of this message.  As a reminder, access to the website should always include 'www' at the front.  If you do not include 'www', it will try to connect to btcguild.com, which is the getwork server, before being redirected to the correct address.  Since the getwork server is under attack, this means you cannot access the site if you forget 'www'.


Users who were using Stratum but can no longer connect, update your miner/proxy to connect directly to stratum.btcguild.com:3333 .  Older versions of cgminer (2.8.x/2.9.x) may require updates, some users had issues with direct connections.  Until the getwork server is restored, the redirect to stratum from btcguild.com:8332 will not be available.

Users who only have getwork available can use mergedmining.btcguild.com:8332 or de.btcguild.com:8332 during this outage.