Pages:
Author

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

hero member
Activity: 658
Merit: 500
CCNA: There i fixed the internet.
The stratum servers will be getting restarted in 30 minutes (12:30 PM, PST) in order to deploy a fix.  bfgminer 4.1+ added TLS to Stratum as the default even though it was never a part of the protocol, and this ended up causing connections to hang for 1 minute+ when trying to connect to BTC Guild, and sometimes simply failing entirely.

The restart will only take a second to complete, but check your miners if they stop working, since historically there have always been certain miners which can't handle a disconnect properly.


EDIT/UPDATE:  Restart completed, everything appears to be working as expected.

was this necessary to do, basically without notice?  if the issue was with bfgminer wouldn't it be the responsibility of those that run it to revert to a previous version or change from the default - rather than bounce all miners?

Not all are aware of the issue and could possibly be lead to think btcguild was defective, and flood his inbox saying dafuq is going on.

He's just heading off the POTENTIAL problem before it happens

Although yes a little more time (24 hrs) would have been nicer
hero member
Activity: 677
Merit: 500
Any way to look to see which pool solved blocks in real time?  I'm interested to see which pool is getting the good luck while we are in the bad.

Luck isn't zero-sum.  One pool being lucky has no impact on another pool being unlucky and vice-versa.  http://blockorigin.pfoe.be has the most accurate tracking of which pools solved which blocks, normally on a 5-10 block delay I believe.

Thanks for the link.  I was curious as to who was solving the blocks.  This was helpful.
newbie
Activity: 42
Merit: 0
The stratum servers will be getting restarted in 30 minutes (12:30 PM, PST) in order to deploy a fix.  bfgminer 4.1+ added TLS to Stratum as the default even though it was never a part of the protocol, and this ended up causing connections to hang for 1 minute+ when trying to connect to BTC Guild, and sometimes simply failing entirely.

The restart will only take a second to complete, but check your miners if they stop working, since historically there have always been certain miners which can't handle a disconnect properly.


EDIT/UPDATE:  Restart completed, everything appears to be working as expected.

was this necessary to do, basically without notice?  if the issue was with bfgminer wouldn't it be the responsibility of those that run it to revert to a previous version or change from the default - rather than bounce all miners?
hero member
Activity: 667
Merit: 500
The reason that luck is not zero sum is that producing a valid block is a statistically-independent event for every single individual candidate block hash. It doesn't matter who else is solving what (with the exception of an orphan race / whether or not you're mining the main consensus chain), the expected number of blocks solved by a given pool in a given timeframe is purely a function of difficulty/target and the number of hashes per unit time that pool produces.
legendary
Activity: 1064
Merit: 1001
You only need stratum+tcp:// when working directly in the config file (and I'm not even positive if it's required there).
Ahh.
legendary
Activity: 1750
Merit: 1007
Also, from the website, doesn't mention the tcp thing at all.

CGMiner is one of the most advanced and full feature miners available. It runs in a command line, but allows configuration while running using the keyboard. After launching cgminer, you will be prompted with the following:

URL: stratum.btcguild.com:3333
Username: username_workername (example: MoreBloodWine_1)
Password: 123 (or leave blank, it does not matter)

-------

Miner Connection Details
Stratum Servers
Host (USA)   stratum.btcguild.com:3333
Host (EU)   eu-stratum.btcguild.com:3333
Username    MoreBloodWine_1
Password   (anything)

Because the website doesn't go into explaining how to setup config files, since most users that need to know how to connect a miner have no interest or understanding of how to do it.  If you just type in stratum.btcguild.com/eu-stratum.btcguild.com:3333 into the prompt, it works fine.  You only need stratum+tcp:// when working directly in the config file (and I'm not even positive if it's required there).
legendary
Activity: 1064
Merit: 1001
Also, from the website, doesn't mention the tcp thing at all.

CGMiner is one of the most advanced and full feature miners available. It runs in a command line, but allows configuration while running using the keyboard. After launching cgminer, you will be prompted with the following:

URL: stratum.btcguild.com:3333
Username: username_workername (example: MoreBloodWine_1)
Password: 123 (or leave blank, it does not matter)

-------

Miner Connection Details
Stratum Servers
Host (USA)   stratum.btcguild.com:3333
Host (EU)   eu-stratum.btcguild.com:3333
Username    MoreBloodWine_1
Password   (anything)
legendary
Activity: 1064
Merit: 1001
I never gave much thought to it since it's always worked. but I was bored and started looking through the config file trying to figure something out and got side tracked by the URL for BTCGuild.

I mean why not use this which is what my backup URL's for stratum look like.
stratum+tcp://btcguild.com:3333

btcguild.com points to the web server.  So that wouldn't work obviously.


Or say even use this...
stratum.btcguild.com:3333


If you were entering the URL when prompted instead of a config file, stratum.btcguild.com:3333 works, but I think the config file requires the full stratum+tcp:// which identifies the protocol to connect with.

The reason you have the "redundant" stratum (stratum+tcp://  and stratum.btcguild.com) is because stratum.btcguild.com is a subdomain which points to the pool servers, while stratum+tcp:// is used to let the miner know to connect with the stratum protocol over a persistent TCP connection.
So basically just keep it thee way it is now since it's been working that way without issue.
legendary
Activity: 1750
Merit: 1007
I never gave much thought to it since it's always worked. but I was bored and started looking through the config file trying to figure something out and got side tracked by the URL for BTCGuild.

I mean why not use this which is what my backup URL's for stratum look like.
stratum+tcp://btcguild.com:3333

btcguild.com points to the web server.  So that wouldn't work obviously.


Or say even use this...
stratum.btcguild.com:3333


If you were entering the URL when prompted instead of a config file, stratum.btcguild.com:3333 works, but I think the config file requires the full stratum+tcp:// which identifies the protocol to connect with.

The reason you have the "redundant" stratum (stratum+tcp://  and stratum.btcguild.com) is because stratum.btcguild.com is a subdomain which points to the pool servers, while stratum+tcp:// is used to let the miner know to connect with the stratum protocol over a persistent TCP connection.
legendary
Activity: 1064
Merit: 1001
I never gave much thought to it since it's always worked. but I was bored and started looking through the config file trying to figure something out and got side tracked by the URL for BTCGuild.

stratum+tcp://stratum.btcguild.com:3333

That's what's in my config file right now and is pretty much inline with how my backup URL's look. Anyway, it got me to thinking.

Am I even calling it right ?

I mean why not use this which is what my backup URL's for stratum look like.

stratum+tcp://btcguild.com:3333

Or say even use this...

stratum.btcguild.com:3333

Or would pretty much all of those work ?
legendary
Activity: 1750
Merit: 1007
The stratum servers will be getting restarted in 30 minutes (12:30 PM, PST) in order to deploy a fix.  bfgminer 4.1+ added TLS to Stratum as the default even though it was never a part of the protocol, and this ended up causing connections to hang for 1 minute+ when trying to connect to BTC Guild, and sometimes simply failing entirely.

The restart will only take a second to complete, but check your miners if they stop working, since historically there have always been certain miners which can't handle a disconnect properly.


EDIT/UPDATE:  Restart completed, everything appears to be working as expected.
legendary
Activity: 1750
Merit: 1007
Luck isn't zero-sum.  One pool being lucky has no impact on another pool being unlucky and vice-versa. 
Sorry for being obtuse here but I expect others will have the same difficulty that I have understanding the above.   You stated this a couple times and I could not think of a simple way to think about it so others might be confused too.

1.   luck is not zero sum.   I can understand this statement on its own and how it is true.

But what I do not understand is "Luck is not zero sum EVEN when the average block solving time is 9 minutes (especially when I assume "luck" is calculated on a 10 minute block time)."

How is it possible for the whole network to be having "bad luck" without the average block time going to 12 or 15 minutes?
If there is some simple way to explain this, please try.    And if Organ needs to answer this (to make me feel dumb as usual) can he please try to use words that average syllables?
thanks in advance

The average block time of 10 minutes assumes that the network speed is not increasing.  However, this is not true, the network speed has been growing by 10 to 30% per adjustment for almost a year.  So it is possible for the average block time to be under 10 minutes and luck to still be negative.  However, over the course of a difficulty adjustment, the deviation from expectation/luck (for the entire network) is quite low, just a few percent in either direction.
legendary
Activity: 2478
Merit: 1020
Be A Digital Miner
Luck isn't zero-sum.  One pool being lucky has no impact on another pool being unlucky and vice-versa.
Sorry for being obtuse here but I expect others will have the same difficulty that I have understanding the above.   You stated this a couple times and I could not think of a simple way to think about it so others might be confused too.

1.   luck is not zero sum.   I can understand this statement on its own and how it is true.

But what I do not understand is "Luck is not zero sum EVEN when the average block solving time is 9 minutes (especially when I assume "luck" is calculated on a 10 minute block time)."

How is it possible for the whole network to be having "bad luck" without the average block time going to 12 or 15 minutes?
If there is some simple way to explain this, please try.    And if Organ needs to answer this (to make me feel dumb as usual) can he please try to use words that average 2 syllables?
thanks in advance
legendary
Activity: 1750
Merit: 1007
Any way to look to see which pool solved blocks in real time?  I'm interested to see which pool is getting the good luck while we are in the bad.

Luck isn't zero-sum.  One pool being lucky has no impact on another pool being unlucky and vice-versa.  http://blockorigin.pfoe.be has the most accurate tracking of which pools solved which blocks, normally on a 5-10 block delay I believe.
hero member
Activity: 677
Merit: 500
Any way to look to see which pool solved blocks in real time?  I'm interested to see which pool is getting the good luck while we are in the bad.
full member
Activity: 221
Merit: 100
I just noticed a transitory display error after I made a manual withdrawal:  on confirming the withdrawal and returning to the dashboard screen, the account balance was the same as the withdrawals figure plus 1 Satoshi, and Earnings was the total of both.  Got me all excited for a moment, but on refreshing the screen it had corrected itself; Earnings=Withdrawals with Account balance zero.
newbie
Activity: 5
Merit: 0
After the monsterous growth of cex.io/ghash.io I decided to move my measely TH/s back to btcguild. Though the one thing I miss is the troll.. err chat box. Any possibility of getting a chatbox on btcguild?
legendary
Activity: 1148
Merit: 1000
Yuck...24hr. luck below 70
 Angry Cry Angry Cry
legendary
Activity: 1064
Merit: 1001
Even if no one ever decides they want one for their own stat's, they can still use mine to display block info as seen below.
[SNIP]
It's very nice, but it amounts to including a signature effectively in the body of your message which is against the forum rules if you include it in every one of your posts so please stop doing it.
Wow, so everyone here is a hard ass when a member of the community tries to make and share something !

He wasn't being a hard-ass, just pointing out that it's against forum rules.
As is apparently a lot of other things around here.

What should be against the rules is the PTB sitting on a horde of coin people donated over the years for forums upgrades that never came !

As to not side track this post this will be my last OT matter in it.
donator
Activity: 2058
Merit: 1007
Poor impulse control.
Even if no one ever decides they want one for their own stat's, they can still use mine to display block info as seen below.
[SNIP]
It's very nice, but it amounts to including a signature effectively in the body of your message which is against the forum rules if you include it in every one of your posts so please stop doing it.
Wow, so everyone here is a hard ass when a member of the community tries to make and share something !

He wasn't being a hard-ass, just pointing out that it's against forum rules.
Pages:
Jump to: