Well written and well said Brunic. I think there were quite a few of us who thought/felt the same way about GPUMax, IE "He wouldn't be stupid enough to run his superior position by running off with the btc.." What ultimately suckered me into moving beyond just mining there to investing with BTCS&T was GPUMax, and the length of time they both survived.
It will be interesting to hear, at some point, the 'real' story about what happened and why it went south, because, imho, it could still be around and making money if not for greed.
|
|
|
Can someone lock and bury this? Its pretty clear that this has run its course.
I don't think we've seen the last chapter in this yet........
|
|
|
So has there been any news on the original thread?
assuming no one else has been repaid.
|
|
|
All the threads seem to have fallen silent.... so I'm assuming it's just over?
|
|
|
Requires : -- Cyanogen source, compile custom kernel -- libcurl -- build files for cgminer -- tweak cgminer pthread behavior (pthread_cancel) -- compile ftdi kernel module -- usb host mode working Miss anything?
|
|
|
I ran into an interesting failure state today, and the stratum proxy, I believe, played a roll in the failure. I posted over in the cgminer thread about the cgminer portion, but wanted to post here about the proxy portion.
Shouldn't the proxy, in some way, tell the clients when it's primary upstream connection dies?
Yes, it should. Let me ask some questions: a) Are you using latest Windows binary? b) If you're using Linux, are you sure you ran "setup.py install" or "setup.py develop" after last upgrade? c) Do you see any error/traceback in the proxy during connection outage? Proxy should propagate all connection failures to all connected miners immediately. It is implemented in method on_disconnect ( https://github.com/slush0/stratum-mining-proxy/blob/master/mining_proxy.py) and I don't see any reason why it shouldn't work, except ther was another error. A: No. cgminer 2.8.3 (at the time) linux, proxy 1.1.1 linux. B: yes, and yes C: no, proxy just sat.. idle. primary pool hasn't crashed again since, so haven't had the chance to see again.. but I'll let you know if it happens.
|
|
|
Dlasher - conservatively, how long before a jalapeno earns you the $160 back? Same question for the 60Gh model? Also what is the delivery ETA on these items?
Conservatively? 12 months. Same all models, since they have -about- the same $-per-Ghash rate, approximately. Delivery ETA is mid-to-end of November for Round 1, and guessing Mid-to-end of December for Round 2.
|
|
|
I have just bought a new Graphics card for bitcoin mining and realized that ASIC's were going to be released in a short while. Graphics card overheats from over clocking and knowing the cable for the cooling fan out while installing sound card leaving me with a nvida geforce 840gs. I want to get into the Bitcoin mining business. Any ideas? Buy ASIC. Buy one of -these-. Gamble like the rest of us did when we bought piles of GPU's that we'd pay them off in 12 months.. Most of us did. After the dust settles, enjoy the coin earned every month, and congratulate yourself for being willing the take the risk. In the mean time, talk to your friends, come up with new ways to spend/use/promote bitcoin so that the coin you earn has more value.
|
|
|
Interesting failure state today.
<snip>
2 minutes. It's there already. Hmmm... I wonder what went wrong then.. I'll have to go back and look at logs again, see if I can dig anything up. In the mean time, I updated all the 2.8.3's to 2.8.4, hope there's magic in the upgrade.
|
|
|
Hopefully by now you should be able to cgminer directly to stratum pools more reliably than through the proxy.
2.8.4 is a dramatic improvement in stratum reliability.. /nod /thankyou Sadly, none of my individual miners are fast enough (right now) to get over a 1-diff, but together they can get 16-diff when run behind the proxy.
|
|
|
Honestly, for me, the "nail in the coffin" against DeepBit was about the time SatoshiDice started up, and it brought to light that Deepbit was refusing to include both '0% fee' transactions, and transactions below a certain transaction fee threshold. At the time, they were a large percentage of the network, and their refusal to process transactions created, in some cases, 12+hour delays to get normal (paid) transactions confirmed. I posted my opinion, deepbit responded, and I don't mine there any more. https://bitcointalk.org/index.php?topic=3889.msg949717#msg949717https://bitcointalk.org/index.php?topic=86129.msg985972#msg985972
|
|
|
Slush:
I ran into an interesting failure state today, and the stratum proxy, I believe, played a roll in the failure. I posted over in the cgminer thread about the cgminer portion, but wanted to post here about the proxy portion.
Scenerio: - stratum pool proxy is pointed at crashes - clients behind proxy stay connected to proxy, but get no work - since connection doesn't 'close' cgminer didn't demote the pool - all GPU's idling and cold
Shouldn't the proxy, in some way, tell the clients when it's primary upstream connection dies?
|
|
|
Interesting failure state today.
I have some (2.8.3) miners behind stratum 1.1.1 proxy.. primary pool stratum was pointed at failed. (stratum crashed). cgminer stayed connected to proxy, which stayed up. proxy couldn't get work from primary pool, stayed idle, all miners went idle, cgminer never failed down to next pools in the chain.
It would be nice to be able to set some sort of threshold.. (And shoot me conman if you already do this and I just missed it)..in cgminer. If I don't get any work from a pool in {threshold} minutes, in spite of being TCP/UDP/etc up, I should mark it dead. (I swear cgminer already does this for getwork.. I see messages about "pool not providing work fast enough")
(FWIW, I'm going to post something over in Slush's proxy thread, because I think his proxy should have marked itself dead, but somehow cgminer should know a pool is "starving", shouldn't it?)
|
|
|
No issues with 2.8.3, been running several days w and w/o stratum.. Perfect version so far.
|
|
|
Linux is a PAIN IN THE ARSE
If you're not 100% versed in LINUX, just install windows. IT'S EASIER
Windows is a PAIN IN THE ARSE If you're not 100% versed in WINDOWS, just install linux. IT'S EASIER Blaming familiarity with one for lack of ease on the other works both ways. This is my version. Computers are a PAIN IN THE ARSE if you're not 100% versed in COMPUTERS, just use pen and paper. IT'S EASIER. <grin>
|
|
|
Ease of use.
BTC needs transactional volume for stability. Volume needs easy use.
|
|
|
Actually martingaling can turn a hefty profit. This one time I won 5 BTC.
There's some truth there... I was up almost 100btc till they lowered the MaxBet to 5... my 100 profit dropped to 20 btc in a matter of hours, and I quit while I was ahead. The MaxBet is back up now, but with a larger house percentage.. So you _could_ make money, not sure you can now..
|
|
|
I'm sure there's another thread, but Oct 12th come and gone... assuming no news, no surprise.
|
|
|
3. Show diff per share submitted in console?
Check latest git version. Thank you! Works like a charm! RE: #2, logging, was hoping to have a log file to pull data from, # of shares per minute, average diff, stuff I can generate easily if I have a logfile, and can then graph. At a minimum, it would be nice to have in syslog so i can redirect it to a central syslog server, on a local1-7.
|
|
|
Thanks again for the proxy, loving it.. two small feature requests:
1. Fail over/back/load balance/etc for multiple servers.
2. syslog facility/target?
3. Show diff per share submitted in console? 2012-10-11 16:56:14,510 INFO proxy stratum_listener.submit # [91ms] Share from 'miner5' accepted
|
|
|
|