 Show Posts
|
|
Pages: [1] 2 »
|
2) There have been no backend changes for ScryptGuild. There have been no changes to the backends period in the last 9 months. 6 of those months were positive on luck. The last 2 were not. The 9th month isn't available since luck only started being tracked across multiple difficulties 8 months ago (prior to that it only showed the most recent shifts of the current difficulty).
eleuthria, you should just eliminate the luck graph on the site entirely. Even though the metric is measurable, it cannot be acted upon, so, in this instance, the measurement is not valuable. And if I have to read the "bad luck" posts for 4 more months (until we are even again), I'm going to kill myself. P.S. Yes, I do know that the 4 month number is not really the guaranteed length of time it will take until the variances work themselves out - it was a joke. |
|
|
|
Size has nothing to do with Luck. If someone is having bad Luck, it does not imply that someone else is having good Luck. Luck does not balance out, it just averages out over time. Luck is just that, Luck.
I'm confused. If two people flip a coin six times an hour, and each time the winner gets 25 bitcoins - doesn't ones person's luck affect the other persons luck? In this analogy, I understand the "size of the player" doesn't matter because they have the same chance of winning (the exact same pool size), but one player's luck seems to affect the other player. I also understand how a smaller pool's share of the total bitcoin rewards will eventually equal its percent of the total network hashrate; however, even taking this into consideration, one pool's luck should impact other pools (in the short term). |
|
|
|
Website down?
Yep:  EDIT: Back up... |
|
|
|
|
Is GHash.IO down again? My miner just switched to a failover, away from GHash.IO
|
|
|
|
Would you care to elaborate? The website is not responding, although the pool seems to be accepting shares. Is this going to be like last week, when the pool "ate" several hours worth of hashes without payouts? Maybe you should just shut it down while you are dealing with the "minor" difficulties so that miners could switch to backup pools.
Just an FYI, my miners is switch automatically to other pools when GHash.IO went down. |
|
|
|
You are basically solo mining if you aren't on the auto switch coin. That's probably why you aren't getting anything.
Op: not sure why you are offering this feature? Most users don't seem to understand the implications of it.
M
When I was referring to mining litecoin only, I meant at another litecoin only pool. |
|
|
|
|
With Litecoin increasing in price, I'm wondering if there is a website that might show if its more profitable to mine only litecoin, auto-switch mine (and keep the litecoin), or just auto-switch mine. How do I know the most profitable choice?
|
|
|
|
I have my rigs split across pools to minimize variance.
M
I'm fairly new to mining; however, I have read that balancing your hash rate between pools is a best practice, to minimize variance. I'm assuming that just choosing "(b)alanced" from the "[C]hange Management Strategy" option in BFGMiner, is all I have to do (if I already have multiple pools listed in the command line), correct? BFGMiner is telling me it is "Connected to multiple pools without LP". What is "LP"? When using BTC Guild as one of multiple pools, is there any disadvantage to using this strategy (slower share acceptance, etc.)? Finally, when I am connected to multiple pools, only BTC Guild (pool 0 in my example) seems to be requesting regular work updates. Is this normal? FWIW, all pools are accepting shares normally (best I can tell)  Wow, I asked four questions... I feel like a hog sometimes... |
|
|
|
Looks like the wheels are coming off at Ghash.io's LTC pool:  Not sure what the heck is going on. My workers are filling up the shifts, but the block payouts are MESSED up |
|
|
|
um... not to look a gift horse in the mouth, but do you think you could make the option to automatically change our nmc into btc like you do on scryptguild?  +1 |
|
|
|
|
If the fee for Pay Per Share (PPS) Method is 7.5%, is it correct that if the pool's luck (hypothetically) ran at 92.5% forever, than the PPS method would break even? Asked another way, if a miner is using PPS, and the pool luck is below 92.5% for an very extended period, would the miner make more than if he was using PPLNS, for the same extended time period?
|
|
|
|
LTC -> BTC auto exchange is now part of automatic conversion (did a manual script execution about 10 minutes ago before putting it into the auto script). It uses BTC-e instead of Cryptsy, since BTC-e is consistently a better price with significantly more market depth to avoid slippage.
Well, I guess I gotta ask.... now that we can auto exchange LTC to BTC, should we? Right now I'm converting all the other coins to BTC, except LTC (they're just piling up). Is there anyway to know if I should keep the TLC or exchange them for BTC? |
|
|
|
eleuthria, I noticed that the finger pointing down, and the "dropdown" on the "Pool Speed" icon disappeared. It showed the pool speed for each coin type. Do you plan on bringing that back? - it was helpful Great new pool , by the way!!!!! |
|
|
|
Finally, anyone think there is actually any shot of the difficulty increase actually slowing down:  |
|
|
|
The even easier version (doesn't factor in the current shift): Check how many open shifts currently have 0 blocks. Multiply that by shift length (4 billion as of my previous post, 4.5 billion going forward), and compare that number to network diff.
At the risk of looking like a complete idiot, I'll ask this... So, if the current network difficulty is 3,815,723,799, and with ZERO variance, how do you compute the number of shares it should take to find a block (is it just the network difficultly number)? Asked another way, what math do you use to to see if you are above or below 100%, on your "luck chart"? Man, I hate being the dumbest guy in the room.... |
|
|
|
The even easier version (doesn't factor in the current shift): Check how many open shifts currently have 0 blocks. Multiply that by shift length (4 billion as of my previous post, 4.5 billion going forward), and compare that number to network diff.
At the risk of looking like a complete idiot, I'll ask this... So, if the current network difficulty is 3,815,723,799, and with ZERO variance, how do you compute the number of shares it should take to find a block (is it just the network difficultly number)? Asked another way, what math do you use to to see if you are above or below 100%, on your "luck chart"? |
|
|
|
Right now we're at a little under 6 hours without a block. Not exactly hard to believe, that's only ~6x difficulty, something which happens at least once a month (probably more).
Is there a good reference where I can learn about the relationship between the time between blocks, the pool size, and network difficulty? Specifically, how can I look at this info and see if the time is 2x difficulity etc.? Thanks. |
|
|
|
Shifts are currently 3.5 billion *per shift*, 35 billion for the 10 open shifts.
Holy cow, had no idea. |
|
|
|
OMG what is up with the bad luck.... Been mining for over 6 months on BTC Guild and have not seen any period of time like the last few weeks.... Am I wrong?
Now we're talking:  |
|
|
|
|
