Wow! My miner found a block. Number 285163. A first for me.

I love it when all the whining kicks in!! The total hash numbers fall as the flakes leave and my rewards jump back up. LOVE IT!!!

Morris

Yes. It looks like slush was down for a few minutes. My miner reset itself due to no activity but it's working fine now.

Morris

Does anyone have information about payout comparisons between pools? For instance Slush has about 500 terahash and btcguild has about 2500 terahash. What would be the payout from each pool for the same amount of hashing?
Any comparison of the same type between pools would be of interest, not just btcguild.
Also, at the moment slush has found 3 blocks for today (24 Dec) and btcguild has found 22. That seems out of balance but maybe just because of short timeframes.

Morris

When I first started with Slush about two weeks ago I set the threshold to 0.01 and when I crossed the threshold it transferred.

Morris

My numbers look ok now too. Looks to me like since the database server upgrade on 26 Nov things have been quite unstable.

Morris

So what's going on with the rewards???  Confirmed blocks are not getting posted and total reward just went down instead of up!!

Morris

>>So how do people intend to stay in the game? I mean, what kind of a rig would give enough GH/s/J and
>>not cost too much to eat into the revenues?

That is a really hard question. For me it is a keep watching and calculating what the yields would be for the various combinations of mining methods. At the moment some of the group buy/shared plans sound fairly good but the difficulty changes can cause big aberrations because the shared plans all start in March or later.

Morris

Yes. The big factor not addressed in most of the profitability calculators is the difference between mining now and 3 months from now. An eruptor blade (at 10 Ghs) that will pay for itself in about 2 months right now will return just a few dollars a week starting in March. Also, The huge volume of new terahash coming online in the next few months is most likely to skew the difficulty big time.

Morris

The projected difficulty for late February 2014 is somewhere around 3 billion on the low side and something like 5 - 6 billion on the high side. 312 Ghs at that difficulty and the current exchange rate for bitcoins would yield about $425 per week with the yield dropping about 15 - 20 % every 12 days or so. The yield for 6 billion difficulty would be about $200 per week. That weekly yield would give about $20,000 or $10,000 earnings WITHOUT any further increase in difficulty which will never happen.

Morris

Here's a guide: https://bitcointalk.org/?topic=205369.0

Good luck.

Morris

Based on the numbers I can find, the current total hash rate of the network is around 6000Ths. KnC is building 1200 Neptunes to be released in first or second quarter 2014 each with 3 Ths for a total of 3600 Ths to be added to the network. If my calcs are correct that means almost a doubling of the hash rate from one manufacturer and one batch.

Do everyone's estimates of 5 or so billion difficulty by March 1 take that into account?

Morris

That looks like a V2 config screen. V2 does not have the switch clock button.

Morris

Like the title - are they legit? Any problems?

Morris

I just looked at the Jones Gear website and they have blades for $419. I bought one from them and they seem to be a very reliable company. When my order got lost in shipping they FedEx'd me another one right away.

Morris

You want to have to ip of your proxy in the blade setup twice and you want the mining_proxy to be run with the command (linux)

mining_proxy.py -o stratum.bitcoin.cz -p 3333

Morris

Well, I found the problem. I had previously been using the mining_proxy instance to mine lite coins and when I started using it for bit coins I just changed the -o parameter to slush's pool but I left the other parameters the same. To mine litecoins there is a -pa script parameter and having that still there caused the proxy to spit accepted messages but the pool ignored them. So the running command line for the mining proxy is:

python mining_proxy.py -o stratum.bitcoin.cz -p 3333

Sometimes I amaze myself by how dumb I can be.

Anyway, thanks to everyone who helped.

Morris

I am running the blade to mining_proxy.py on a computer on the network and then to slush's pool.

Interestingly, I just was looking through the stats on slush pool and I found that during the time that I had the blade trying to run there that the reward for that round was about 9 times higher than other rounds. I guess that means that even though the worker did not show activity it was being accepted. Very strange. I guess I'll hook it up to that pool again and let it run through the night and see what I see. I'll report back.

Morris

Interestingly, I just was looking through the stats on slush pool and I found that during the time that I had the blade trying to run there that the reward for that round was about 9 times higher than other rounds. I guess that means that even though the worker did not show activity it was being accepted. Very strange. I guess I'll hook it up to that pool again and let it run through the night and see what I see. I'll report back.

Morris

(xandriel)

<
<
<
I did a test of pointing the blade to a non-existent worker at the pool and things did not appear to work at the proxy. I then created that worker at the pool and the proxy started spitting accepted messages and the blade started showing accepted count. I took that to mean that the blade was talking through the proxy to the pool server.

(DrunkenSailor)

>>I've got a v2 blade working fine with Slush's pool. Could you post some of your proxy log? That might help folks >>point you in the right direction.  Also, it does take some time for the worker to show up, and even more time for the >>Mh/s to be shown accurately for the worker. Having said that, 2 hours should have been more than enough for the >>worker to at least show up…

It is very encouraging to hear that both you and grim xandriel have blades talking to slush. That means I just have to find the right combination.
I will try to post some proxy log a bit later. I have to get it from across the network.

(grimsparkle)

>>One other thought... make sure the blade's configuration points to the IP address of the computer running >>mining_proxy under Server addresses:

>>Ports: 8332,8332 
>>Server Addresses: your Mac's IP address, your Mac's IP address
>>user:pass: username.worker1:password,username.worker1:password

>>Blade port 8332 ---->Proxy(Mac 'server' running mining_proxy.py) port 3333 ----> Slush's Pool

I am pretty sure that is how I had it set up. I will check a bit later after it has run for a while on bitminter.

I also have to eat dinner. I certainly appreciate all the help especially knowing that it will work.

Morris