 Show Posts
|
|
Pages: [1] 2 »
|
|
I want to sell my mining rig, set up to mine under linux. I mine at 940 mhz, both cards are stable to 980+. Have mined continuously for several months. Rig is a AMD athlon x2 w/ 4gb of ram and a 250 gb sata drive, inside of a Lian-Li aluminum case w/ a window. 80 + gold powersupply draws ~400watts while mining.
Rough values in USD:
Cards - 120 each
Case - 50
CPU fan - 30
CPU/mobo/ram/hdd - 100
Power Supply - 120
== $540 + shipping in usd (it's quite heavy so I'd expect shipping in the states to be at least $30, more elsewhere)
Make an offer in BTC
|
|
|
|
|
I'm in hook me up with an address.
|
|
|
|
If a guy steals a truck full of goods, and decides to dump them for cheap, whoever buys those shoes is still committing a crime. I say fuck Kevin and take the coins off him (he seems pretty seedy anyway).
This. To say "I got extraordinarily lucky and was able to use my wits to help someone perpetrate a crime at the right moment but 'dems da rules' so I should get to keep my ill gotten gains and the system I exploited to get them should be destroyed in the process." is not only incredibly selfish but an untenable position for someone who claims to want to *help* the bitcoin community. Assuming the sale came from a compromised account, which at this point seems very likely, "Kevin" either knowingly profited from theft or he was too ignorant to realize the figures he was seeing could only be a bug in the system or the result of something uncouth. Honestly if someone was claiming they put in a sell order at $100 "just in case" and a bug caused it to go through mt. gox at $0.01 and it caused this event would anybody argue *not* to roll back translations? I can't imagine the "it's important that if our exchanges are bugged we allow the market to collapse" argument holding water. |
|
|
|
( 8 ) "At the moment, Bitcoins can't really be used at any mainstream retailers. According to a wiki list of businesses that accept Bitcoin, you can use the currency to buy real goods and services, but we're not exactly talking about Amazon.com (AMZN)." // OMG OMG OMG YOU CAN ALREADY USE BITCOIN TO MAKE PURCHASES ON AMAZON.COM !!!!!!!! via TradeHill.com..... TODAY!
TRADEHILL IS NOT JUST CONVERTING BITCOIN INTO AMAZON MONEY.
TRADEHILL ALLOWS YOU TO COMPLETELY MAKE THE PURCHASE ---- USING ONLY BITCOIN ---- WITH ONE CLICK. THAT IS NOT JUST BUYING AMAZON MONEY.
And many many many online retailers are quickly following suit with the Amazon + TradeHill system.
There is absolutely no reference on TradeHill's site currently to this functionality. They may have allowed this at some point but they say nothing about it now, and even if it worked the way you described Amazon would still be collecting USD not BTC for your purchase which makes the authors statement completely factual. |
|
|
|
Crash is a tricky word, but you certainly can't insist it only goes up up up when it's currently trading at <50% of it's high from a little over a week ago. It is a *highly* volatile market and you can only say factually that it has gone from $.005 to it's current price of ~$14 for a 200k%+ increase. That is 100% accurate and incredibly compelling.
It's not 100% accurate, because you're leaving out the fact that on its way to the current price it achieved a high just over DOUBLE the current price. I don't think you can just ignore the fact that a week ago people thought their 100 btc were worth $3000 in their pocket, and today that could only be $1500 in their pocket. |
|
|
|
Accepted. I tweaked the formatting a bit, but please keep it coming I'm really glad to not be the only one using the script. I'll likely refactor a bit in the coming days but don't let that stop you from submitting more pull request.
I realize that my display tweak focuses on my worker's name as opposed to yours. Probably time for me to start using ncurses to display things a bit more easily, and put the whole script in a delay loop so I don't have to run it with watch -n 300 ./btcguild.py anymore. |
|
|
|
I've sent you a pull request for a small calculation fix and also individual worker stats  Accepted. I tweaked the formatting a bit, but please keep it coming I'm really glad to not be the only one using the script. I'll likely refactor a bit in the coming days but don't let that stop you from submitting more pull request. |
|
|
|
Thanks, pretty cool. For the Windows users that want to check it out I used the following: Curl - http://www.paehl.com/open_source/?CURL_7.21.6Python - http://www.python.org/ftp/python/2.7.2/python-2.7.2.msiI installed Python with default selections. Then I copied the curl.exe into C:\BTCGuild_Stats folder along with the btcguild.py file. You will need to add your API key on line 6, keep the ' on each end, and then remove the /usr/bin/ from line 9,10,11. Then just be in a command prompt in the directory and type btcguild.py Glad to hear it works. I just updated it to have a CURL_PATH directly below the API_KEY so you only have to change the path in one place. It now displays the current Round Time next to the Average Block time as well. |
|
|
|
So instead of reloading the block stats and my account pages on the site all the time I whipped up a quick python script to curl down the data from the api and display it. It requires python and curl to be installed, I've tested it on ubuntu but there isn't a reason it wouldn't work with any other os. For now you need to just put your API Key in the top, and if you're on a different os flavor update the #! python path and the curl path. Here is the sample of the output: +-+-+-+-BTC GUILD Pool Stats for XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX-+-+-+-+
+ Confirmed Payout : 0.58573323 +
+ Unconfirmed Payout : 0.34381127 +
+ Estimated Payout : 0.02086434 +
+ Sum Total (inc est): 0.95040884 +
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
+ Total Worker Hashrate 615.61 Shares 1375 Stales 3 Stale% 0.22 +
+ Pool Average Block Time (seconds) 2825 +
+ Latest Block Times 1:07:50 0:36:48 0:12:03 0:07:46 0:14:48 0:44:14 +
+ Pool Est Blks/24hrs 31 Miner Est 24hr Rewards : 0.61859068 +
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
I'll likely provide some updates to allow for all sorts of extras (config files, idle warnings, etc.) as well but this is a start at least. Feel free to pm me if you have questions, and you can always submit a pull request to change the code. |
|
|
|
|
screen -r
(or screen -rd)
will connect you back to the existing windows
^a-c makes a new virtual window once you're back inside of screen
|
|
|
|
|
A standard circuit is 20 amps not 30 amps, 30 requires upgraded wiring specs if I am not mistaken. If your house has homerun outlets or you can run new homeruns to your circuit breaker you should have 20amp circuits and plug 3 machines per breaker in.
If you're buying new breakers and wiring them in, you should buy 15amp breakers and only run 2 machines per breaker (then you can use a standard outlet per circuit), you're confident about not overloading the circuit, and you're not wasting anything other than circuit breaker slots.
If you can install as many circuits as possible you shouldn't worry about max per circuit you should just be safe and go for the 2 machines per 15 amp circuit route, and worry about maxing your 100amps of power.
|
|
|
|
Okay I'll try Diablo with a smaller pool that has been more reliable for me in the past and let you know if that helps. Like I've said to others, I believe there is either a widespread bug in how some pools operate (such as giving the wrong diff target out, or incorrectly checking hashes (such as H == 0 only instead of also G <= target)), or Pheonix is incorrectly reporting that shares have been accepted when they haven't.
For me, on Deepbit, I get two or three stale shares for every 1000 give or take.
I connected to a small pool I often use with Diablo. It kept up reporting 304Mhash/s but after several hours the pool reported that of the 1231 requested blocks Diablo had only been able to return 854, for an efficiency of 69%. With phoenix my efficiency is upwards of 90% even though my Mhash rate is slower by 5. I don't know enough about the long polling process or the way the rpcs work to identify if this is a bug with my pool or the miner. But my effective hash rate is certainly better with phoenix. |
|
|
|
Okay I'll try Diablo with a smaller pool that has been more reliable for me in the past and let you know if that helps. Like I've said to others, I believe there is either a widespread bug in how some pools operate (such as giving the wrong diff target out, or incorrectly checking hashes (such as H == 0 only instead of also G <= target)), or Pheonix is incorrectly reporting that shares have been accepted when they haven't.
For me, on Deepbit, I get two or three stale shares for every 1000 give or take.
|
|
|
|
|
So I've been mining with phoenix and phatk and I get 299Mhash/sec pretty consistently (VECTORS BFI_INT AGGRESSION=12 WORKSIZE=128). I tried Diablo and it lets me push it up to around 304Mhash/sec (-v 19 -w 192) (Headless linux miner, 6870 1000MHz core 920Mhz memory). That does seem higher, but with phoneix I get an average of 98% accepted blocks where as with Diablo I'm seeing 90% accepted or below. That's a big difference. I'd love the 5 Mhash/sec more, but the drop in efficiency makes my actual throughput lower.
Any suggestions?
|
|
|
|
|
I pay about .09c per kWh for service and about .10c for delivery. Just over .19c per kWh total. Standard coned rate in NYC. Our power comes from the Indian Point Nuke plant, coal, and Niagara falls. (among others). I pull 275watts to run a 6870 so about $30 a month.
|
|
|
|
s/finding/hosting/  |
|
|
|
|
No problem, thanks for the guide. If I discover anything else I'll come post. Really want to figure out how to override my max clock and push up a few more mhz so I can break 299.6 Mhash/sec barrier and get the 300 I know I can.
|
|
|
|
|
