Oh, another "we found the issue, wait a while" response.  Fourth time is the charm?


22 hours ago from BigVern (via reddit: pevernon): "It's a long chain download, but we should have it back online sometime tonight. BigVern"


WDC does not take anywhere near 24 hours to redownload/sync.

This is flat out wrong.  You do not lose ANY hash power by putting multiple machines on one worker on ANY pool.  It's not recommended purely because it means idle notifications won't work unless all machines go down at the same time, and the stats will be merged for all hardware.  But you don't lose any speed.



This is the correct answer.  If your workers share a single miner instance (either a single BFGMiner or a single stratum proxy), you should set the difficulty to the combined speed, since vardifficulty will be doing that whether you want it to or not (and it works the same on every pool).

If your workers are running their own miner instance, you just use that miner's speed.

So far the closeout is going pretty smooth, the only issue I'm aware of is the WDC problems.  Cryptsy support has stopped responding at this point and has taken zero visible action towards resolving the problem so far.

I recommend you not look at the next difficulty adjustment coming in 3 days.  Or the next few coming after that now that ASICMINER is starting to flood the supply chain which will soon find its way into user's hands.

First support ticket just said it was "wallet maintenance".  Well that clearly is over (and was never mentioned, so it was in all likelihood bullshit).  Doesn't change the fact that Cryptsy still has yet to recognize over 70k WDC in deposits that have over 10,000 confirmations, and the latest support response is a complete lie and stall tactic.

"I apologize for the delay, our wallet seems to be merging inputs on incoming deposits, our wallet team is going to have this issue fixed very soon."  - This is bullshit you feed to people who have no idea how cryptocoins work.


7501 WDC - 6a26c047ec61b7532b5b89af37c3c4d42c3028f6fb352d737066abe70327ddcf
10326 WDC - 7894151ed49402cf9126765a774fa095db1359faefa7edaf8b5f8f053026e99c
9309 WDC - 72c30dbfc7ad2bf5eec3b442c868a68ee4e510b4a79ab6cb226a67c0dc9de96b
12751 WDC - 4290db138a810e5d0bfe63b6ce2ba868ef86d92b8618feb6a7e190347cd9f4a4
10037 WDC - ef72bdaaa0d3c7dd98d6eb73ff27d7f23d7976a2247bedefd7064e45a8e8cab2
6655 WDC - f71828185ba385d09758b61d1d44a76cf6223a8fc5d1ef954e2762d0ffecf2ef
10693 WDC - 80df684f3f9d8ffc217d17577409b070f0a77af6d6a98f132c4cfad6d8c08781
8380 WDC - 9c14caf78de15308ebadd678f1560d35d10ee0c0238f70a9f6257c89a74024c0


The most recent of these was confirmed over 2 weeks ago.  Ticket ID #151416.

The donation button has been added for explicitly donating your remaining balances to the pool.  As stated, the button is for *all* remaining balances, so it should only be used after pulling out whichever coins you wish to keep.  There is a confirmation screen before anything is done, and I can/will revert any coins marked as donated if somebody makes a mistake or changes their mind.

Cryptsy is still trying to drag out crediting the 70k+ WDC that was deposited which they didn't recognize.  Now over 2 weeks since the deposits were made, and of course the support response is *complete bullshit*, simply trying to get me to wait 1-2 days and hoping I forgot the whole thing.

While I don't promote pool jumping,  this is  false logic.  The PPLNS charge-up/wind-down time are symmetrical.  You do not lose anything by mining on a PPLNS pool for a few minutes, nor do you lose anything by leaving it after a few hours.  It is unhoppable because it uses a backward-looking payment allocation, not because it penalizes you if you don't mine constantly.  The expected payout per share on a PPLNS pool never changes based on timing/frequency of submissions.  Every share submission has the same expected payout whether you quit mining immediately after sending it, or if it was your first submission.

Because there is a symmetrical chance of getting twice the expected payout as there is of getting 0 payout.  If you mine for 24 hours and get twice what you should have, and then mine another 24 hours and get nothing, you end up right where you should be.

The chance of low payouts during a given timeframe is greater the smaller your pool is.  At the exact same time, when a smaller pool gets lucky it pays out *significantly* better.  The expected earnings is the same regardless, and so is the long term average.  It's just a matter of how far you can deviate from expectations during that time frame (and the smaller the time frame, the greater that deviation can be).

---

Adding on that previous thought, if you want to attempt to refute it:  Pooled mining as a whole works on the exact same principal.  Every hash is equal, even though a user with 1 GH/s is statistically unlikely to ever find a block for the pool, and will siphon off a small piece of each block they participate in, they are still worth having.

You will have users who have never mined a block for the pool (similar to your picking and choosing periods of time with no payment).  You will have users who have mined significantly more blocks than expected for their hash rate.  Average it all together over enough time and you should end up with the same number of blocks as you would have mined if it was just a single user mining with the pool's hashrate.

You're a little off on the math (but round numbers are okay normally).  However, you did 3600 x 12, not 3600 x 14.  The difficulty should change every 14 days at neutral (which would be 144 blocks -> 3600 coins).  While difficulty adjustments lately are much faster than that, it doesn't change the fact that the # of coins mined during a difficulty period is 3600 x 14 = 50,400.  If difficulty increased faster, the x14 would go down, but the 3600 would go up, but the product will always be 50,400 coins mined during a given difficulty period (+0.5% or so for tx fees).

I'll probably add a button this weekend to donate/forfeit your balance just so the system stops counting it as owed coins.

At this point I'm starting to think Cryptsy is just flat out trying to steal a couple thousand dollars of WDC by making me run out of patience.

Heh, I saw that little story earlier.  And I thought *I* wasted a lot of time over the years in World of Warcraft...

No...it doesn't work like that.  The number of blocks being produced is completely independent of the number of transactions on the network.

You're asking someone who is very pessimistic, and somebody who started when BTC being worth $1 seemed like a big surprise.  At this point I just go with the flow.  I'm not a market maker/mover, and for my personal use, Bitcoin can be worth $1 or $1m, since as a transactional currency the only requirement is that there's enough purchasing power in the non-hoarded coins to transact business efficiently.

Wasn't even aware that a legendary status existed, hah!  Fun little tidbit:  "Total time logged in: 127 days, 11 hours and 13 minutes."

Why should those be separated?  AFAIK, BitMinter it the only one that even attempts to differentiate between the two, but they both mean the same thing:  The pool wasted work on a block that was not accepted (thus orphaned) by the network.

Comparing 3 relatively small pools (all 3 are under 8% of the network) will almost always have one showing significantly better.  Had he done his experiment about 9 months ago p2pool would've been dead last by a significant margin.  Luck will affect your earnings on small pools more than anything, because the smaller you are the more you're affected by variance.

Especially true in his experiment, which was done at a point where p2pool simply finding a single block more or less than expected during two weeks would have a massive impact.  Almost the entire difference between p2pool and BTC Guild in his timeline is the difference in the second period's results.

Working to resolve WDC...Cryptsy has over 70k WDC that they are not currently recognizing because they're incompetent.

Just don't read into it with too much certainty.  While you can know for sure if the next few will end above 100%, you can never be sure how many will end under it.  You can have a pretty good idea if they will (0-2 blocks found in the next shifts to close), but you never know when a burst might occur to bring them up to neutral or better (like how we had 3 blocks in under an hour earlier).