Selling 5 shares to dogie.
Will confirm after I receive the payment.
Paid, awaiting confirmation. |
|
|
|
|
Hello all,
What exactly is the criteria for being able to self lock your own thread? I've seen a few cases where you can, and others were you can't. Who, what, where, when, why?
|
|
|
|
|
@eleuthria
Is there anything against us creating multiple accounts to put different workers on (Avalons etc) to track their lifetime earnings easier?
|
|
|
|
my paper clip trick on my powersupply is unstable, I put electrical tape over it (just that part of the connector it covers maybe 5 pins in a row) but it doesn't hold the paper clip down forever, it becomes less effective and the paper clip is able to move just the slightest to turn the power supply off
how do other people deal with this? Its just a minor annoyance because the block erupter blade reboots so quickly and gets back to work
Just make it a bit spring-loaded and plug into two holes next to each other. Yeah mine requires a decent bit of force to put it in and out. Its also cut to the perfect length so taping is purely to prevent drunk people and cats getting electrocuted. |
|
|
|
Here's my proxy command and notice I do not use user/password in the command so I can use only one proxy for 2 or more blades, each configured with its worker username and password:
nohup python mining_proxy.py -o stratum.btcguild.com -gp 8332 -o eu-stratum.btcguild.com -gp 8332 > /dev/null 2>&1 &
Does the proxy support multiple getwork hosts at once? And how it manage them (switch, etc.)? Only testing to see if that works. I put both btcguild stratum servers so if the first one goes down it should connect to the second one. J/ Why do you use twice the same getwork port "8332" Shouldn't you be using a different one for the backup server? No. He's specifying the port of the pools. Both of those servers both have the same pool. |
|
|
|
Xian where are you located? I set up the 300 page setup guide, I can probably help  |
|
|
|
|
PM'ed all. Sorry, was finding it difficult to track so many threads.
|
|
|
|
Thinking... if the goal is co-location, i dont think datacenters allow 1kw for 1 or 2u rackspace... its just too dense...
Checking that out. There are plenty of GPU servers that throw that sort of wattage and more so not sure that is a hard and fast rule depending on the nature of the data center and what services they provide. http://www.nvidia.com/object/tesla-servers.html If I need to go to a 1U K256 so be it that is still doable I just do not want to have to build a server room on my 3rd floor so this is really an experiment to see if I can get my chips into a rack mount configuration. If it works I will definitely be doing more of them in the future. As for flipping the boards they are fin to fin so that the heat is pushed out through the fins getting the best airflow from of the fans. Also the Klego is easier to put togther in a fin to fin configuration. Access however is not and maintenance and inspection will require a lot of time. But given this a stanchion solution it is easy enough to test both configurations by changing stanchion length. I can test both ways and see which is better. I have a feeling fin to fin is optimal if the air flow is constant and in that Venturi type configuration. I really don't think this is the "venturi" layout you're looking for. There is no significant reduction in cross section, just a hell of a lot of turbulent flow. I really think that even with a middle row of fans you'd struggle to remove that crazy amount of heat from there. |
|
|
|
Q#1: If it turns out that metabank and the bitfury asic are a scam, will you refund our money?
A#1: If it turns out metabank is indeed perpetrating a scam and all funds sent to them are lost; we will take a loss on any onsite incidental expenses (Employees, Plane Tickets, Rent, etc) incurred and refund the remainder of your transaction to your bitcoin address. Unfortunately we cannot take responsibility for the actions of anyone but ourselves. The amount refunded should be roughly 12 bitcoins per device. Illegal. We would be purchasing the unit off YOU. If your supplier is a scam, that's not our responsibility. I would be suing YOU, your company and anyone else involved. |
|
|
|
|
And if it turns out like a scam, YOU will refund us right? That's the responsibility you take as a proxy.
|
|
|
|
|
If you need some advice on a portfolio then hit me up in a PM.
|
|
|
|
|
Worst. Setup. Ever. Its like offering to instruct someone how to cut off their own penis.
|
|
|
|
Apologies if this has been asked and answered, but I seem to remember reading that the estimated speed by pools is not as accurate as the hash rate shown on my miner. I am running two blades on BTC Guild and they both indicate 13000+ mh/s on my config screen. They are running neck and neck in my stats page under "accepted shares". In the past 30 minutes, they each had 4480 accepted shares. The min difficulty was set to 8 up until an hour ago and then I changed it to 64. Yet the estimated speed has been reading 12,400mh/s for one and 11,400mh/s for as long as I can remember. Which stat should I believe?
Edit: now the stats on btc guild are starting to update and even out. Looking at the 24 hour charts I see this as well. Both are at about 12,000mh/s. Why don't they reflect a number closer to the 13,000mh/s that my miners show?
I to would like to know about this :/ |
|
|
|
TRUE AMERICAN SLIME
You realize you are slagging an entire country? = they are slime, who are americans. Not americans, who are slime. |
|
|
|
Have to say it for the 3000th time. Even at 150m difficulty in a year, blades still ROI in 16-20 weeks depending on batch. Remember when it was QQ Avalon B2s overpriced, then QQQQ Avalon B3s rip off?
Let us presume that the Eruptor Blade can do 12GH. Some may be able to produce slightly more but lets be conservative for the moment. They are priced in BTC, which makes it easy to identify what return is being generated by the device without involving rises or falls in exchange rate. According to http://dustcoin.com/miningAt 12.1M difficulty, a 12GH blade generates roughly .5 BTC per day. At that rate it would take 100 days to generate 50 BTC at zero growth rate in difficulty. At 150M difficulty, a 12GH blade would generate rougly 0.04 BTC per day. Assuming a constant rate of growth between 12.1M and 150M over the period of 1 year, the difficulty will adjust by roughly 2.5M every 7 days (round numbers make things easy). At 20 weeks the blade will have generated 27.06 BTC, the dificulty will be about 57million and the blade will be generating .74 BTC per week. At that difficulty growth rate, an Eruptor Blade will not pay for itself in 1 year if purchased for 50BTC. IMO, 150M in 365 days is a very aggressive estimate for the difficulty growth rate. Please let me know if I got the math wrong, I didn't use a spreadsheet, I just did back of the envelope. Purchased today, a blade would generate 64 in 52 weeks. And for every week earlier you purchased, its an additional 3 coins. Ie mine purchased 3-4 weeks ago = ~73 with frozen exchange rates. ROI for purchased today is about 27 weeks. EDIT: Its also worth noting that the main ROI is actually from expected currency shifts. 52 weeks is a long, long time in btc terms. At what rate of difficulty growth are you assuming that 64BTC in 52weeks? 10% consistently on the basic model. |
|
|
|
Have to say it for the 3000th time. Even at 150m difficulty in a year, blades still ROI in 16-20 weeks depending on batch. Remember when it was QQ Avalon B2s overpriced, then QQQQ Avalon B3s rip off?
Let us presume that the Eruptor Blade can do 12GH. Some may be able to produce slightly more but lets be conservative for the moment. They are priced in BTC, which makes it easy to identify what return is being generated by the device without involving rises or falls in exchange rate. According to http://dustcoin.com/miningAt 12.1M difficulty, a 12GH blade generates roughly .5 BTC per day. At that rate it would take 100 days to generate 50 BTC at zero growth rate in difficulty. At 150M difficulty, a 12GH blade would generate rougly 0.04 BTC per day. Assuming a constant rate of growth between 12.1M and 150M over the period of 1 year, the difficulty will adjust by roughly 2.5M every 7 days (round numbers make things easy). At 20 weeks the blade will have generated 27.06 BTC, the dificulty will be about 57million and the blade will be generating .74 BTC per week. At that difficulty growth rate, an Eruptor Blade will not pay for itself in 1 year if purchased for 50BTC. IMO, 150M in 365 days is a very aggressive estimate for the difficulty growth rate. Please let me know if I got the math wrong, I didn't use a spreadsheet, I just did back of the envelope. Purchased today, a blade would generate 64 in 52 weeks. And for every week earlier you purchased, its an additional 3 coins. Ie mine purchased 3-4 weeks ago = ~73 with frozen exchange rates. ROI for purchased today is about 27 weeks. EDIT: Its also worth noting that the main ROI is actually from expected currency shifts. 52 weeks is a long, long time in btc terms. |
|
|
|
|
I'd love this feature. I'm often engaged in 20 or so threads, but don't want to keep them open and refresh. Like the "my messages" tab we could have one for quotes. Then it flags "unread" quotes so I can address them in turn.
|
|
|
|
Lol I bet no one will pay BTC tax, then what will they do?
I know you're just spamming 100s of nonsense posts to gain posts then scam someone, but I'll answer your question anyway. They'll rape you. Account for bitcoin transactions in the same way you would track how much money you've made from them. Need to track £ price in and out, to work out final profit in £, then declare it under self assessment. Its non VATable though. https://bitcointalk.org/index.php?topic=153332.new#new |
|
|
|
Face value vouchers
Face value vouchers have a monetary face value. These are used instead of money for a future purchase. If you sell them at or below their monetary value, no VAT is due.
When a customer redeems a face value voucher, the transaction is treated as though the face value voucher was cash, and VAT is due on the full value of the transaction. If you can show the voucher had been sold at a discounted amount, VAT is due on the discounted value, rather than the face value of the voucher.
If you give away face value vouchers and redeem them for no further payment, the goods purchased are usually treated as if they were free gifts for VAT purposes. http://www.hmrc.gov.uk/vat/managing/charging/discounts-etc.htm#4It makes sense. Effectively they're saying its a ticket you can redeem for a Fiat price, which is correct, and that it isn't a good on its own. Hence, non VATable. Good call HMRC. |
|
|
|
|
Show Posts
