|
I got this with a video card I bought a while back. It's good until 12/31/2014. I'm not entirely sure what it's good for, but I'm not into racing games, so there's no way I'm ever going to use it.
Make an offer.
M
|
|
|
|
|
Why are the prices, maint fee included, so high?
M
|
|
|
|
|
A few more hours before this goes at 1/2 face. Any better offers?
M
|
|
|
|
...
As for the p2pool impact, I sure hope Bitmain has figured out how to deal with the variance problem. Throwing another 4PH/s onto the network will mean share difficulties of about 50M.
Yea, I asked about it in their announcement thread, that 4PH will basically annihilate many p2poolers if they have not come up with some radical change to how p2pool calculates/makes payments. I'll suggest now, possibly prematurely, that this may be the catalyst to have 2 separate P2Pool share chains running independently. I would assume that p2pool will fork, and the one we are currently using will die. That's assuming, of course, the antp2pool addresses the issues. M |
|
|
|
Hello Guyz The price went from 0.0016 to 0.00135฿/GHS, minus 18.5%  Still too high. If the maint fee was lower, it'd be a different story. This is China, electricity is supposed to be dirt cheap, why so high?? M |
|
|
|
To put things in perspective, if BTC/USD remains constant, you're looking at a 37% pool fee. No electricity, no heat, presumably guaranteed up time, but still 37% pool fee.
According to tradeblock.com, at 15% difficulty increase/month, if all else remains the same, you'll break even in March 2015.
Your analysis is incorrect because 37% is valid only at current difficulty. As the maintenance costs are fixed, the percentage will go up every time the difficulty rises. Better calculator is here https://bitcoinwisdom.com/bitcoin/calculatorEven at ultra optimistic 5% diff. growth per period the investment will never return. I don't like bitcoinwisdom, it always is wayyyy off on difficulty estimates. Regardless, if percentage increases every time, then my estimates are even worse. Thanks for pointing that out. M |
|
|
|
I'm declaring 3.2 stable enough to publish. v3.2 - Fixed the problem with not being able to save the config if you've never used it before. - Changed to query the Ants via the API on background threads. The numbers of threads is configurable. The more Ants you have, the higher you likely want this value to be. It defaults to 4. - Changed to refresh the display grid X numbers of seconds after the Ant refresh has started. This value is configurable. If you have a large number of Ants, or have slow video, you'll benefit from setting this to a larger value. It defaults to 1. - Fixed the default column widths and also added tool tips to the column headers that aren't self explanatory. - Added a routine to trim the log size down to approx 1m characters when it reaches 1.5m characters. Download link: MAntMonitor32.zipM So what doesn't this address out of everything we discussed ? It seems just like the saving thing where when I say have 4 units, close the program out. Come back and everything but one was gone. Ty. It doesn't fix most of your issues. That's coming when I redo the config UI. M Gotcha, thx for all your hard work ;-) It should fix your "it doesn't reboot" problem though. M |
|
|
|
I'm declaring 3.2 stable enough to publish. v3.2 - Fixed the problem with not being able to save the config if you've never used it before. - Changed to query the Ants via the API on background threads. The numbers of threads is configurable. The more Ants you have, the higher you likely want this value to be. It defaults to 4. - Changed to refresh the display grid X numbers of seconds after the Ant refresh has started. This value is configurable. If you have a large number of Ants, or have slow video, you'll benefit from setting this to a larger value. It defaults to 1. - Fixed the default column widths and also added tool tips to the column headers that aren't self explanatory. - Added a routine to trim the log size down to approx 1m characters when it reaches 1.5m characters. Download link: MAntMonitor32.zipM So what doesn't this address out of everything we discussed ? It seems just like the saving thing where when I say have 4 units, close the program out. Come back and everything but one was gone. Ty. It doesn't fix most of your issues. That's coming when I redo the config UI. M |
|
|
|
I'm declaring 3.2 stable enough to publish. v3.2 - Fixed the problem with not being able to save the config if you've never used it before. - Changed to query the Ants via the API on background threads. The numbers of threads is configurable. The more Ants you have, the higher you likely want this value to be. It defaults to 4. - Changed to refresh the display grid X numbers of seconds after the Ant refresh has started. This value is configurable. If you have a large number of Ants, or have slow video, you'll benefit from setting this to a larger value. It defaults to 1. - Fixed the default column widths and also added tool tips to the column headers that aren't self explanatory. - Added a routine to trim the log size down to approx 1m characters when it reaches 1.5m characters. Download link: MAntMonitor32.zipM |
|
|
|
|
To put things in perspective, if BTC/USD remains constant, you're looking at a 37% pool fee. No electricity, no heat, presumably guaranteed up time, but still 37% pool fee.
According to tradeblock.com, at 15% difficulty increase/month, if all else remains the same, you'll break even in March 2015.
If you buy 3 S3s from batch 8, or somewhere else, at 0.58 BTC a piece, you get 1.36 TH/s for 1.74 BTC. Mining at a 0% fee pool, like p2pool, and electricity at 0.12 KW/h, if all else remains same, you'll break even in Jan 2015. That's assuming you have PSUs available already, and you don't have a problem with the heat. Cold weather is coming in the northern hemisphere, so the heat should be welcome. And you can resell your S3s.
At 25% increase per month, you'll break even with Hashnest in August 2015. You'll never break even with your S3s.
M
|
|
|
|
M's Ant Monitor can reboot Ants when they drop below a certain hashrate as well. See my sig.
M
If I would have known about this application couple of days ago then I would probably not have written the script. But as I have written it, then I will keep running it, advantage of the script is that - it will not require a computer to be on 24/7 for the monitoring to work (because the script runs on miner itself) as opposed to the application. Thank you for the comment, I wish I had known this already  Sorry, I don't monitor this thread normally. Too many messages. M |
|
|
|
S1-1 - 218 - 5hr - 437gh - 1HR Restarts
S1-2 - 250Mhz - 5hr - 466gh - 1/2hr restarts.
This is an increase of over 40GH on both miners for me!
I'm going to clock-up S1-1 and see if I see increases at 1/2hr intervals.
I encourage those experiencing degrading performance over time to do something similar. You lose less than 10 seconds of mining per restart.
I have same problem with one of my antminers, that randomly it will start under performing, like for example when I first turn it on it will hash fine for random amount of hours averaging 440 GH/s, but then will go to 400-410 GH/s AVG for days unless I will reboot it, sometimes needs couple of reboots. M's Ant Monitor can reboot Ants when they drop below a certain hashrate as well. See my sig. M |
|
|
|
Official subscribed flat price is 0.0016 BTC/Gh/s.
Each user is limited to a maximum of 1,000Gh/s.
Maintenance fee of $0.0032424/GH/s/Day.
So max buy in is 0.0016 BTC/Gh/s x 1,000Gh/s = 1.6BTC
Maintenance fee of $0.0032424/GH/s/Day = $3.2424 per day or $98.623 per month
So a hosted S2 in China for 1.6BTC & $3.24 per day including power etc.
This price is a bit steep IMHO. 1.6 BTC for 1 tH/s? Can do better with 3 S3s if you have PSUs already, and electric cost is about the same or less. M My view as well and given that these S2s have probably been running for how many months already? If winter was just wrapping up in the northern hemisphere, and lots of warm weather was ahead, I'd consider it. But cold weather is coming this side of the world. Once again my space heaters can be put to good use. M |
|
|
|
Release candidate #2. MAntMonitor32rc2.zipOnly thing different is for the "reboot on error out" it uses the API to try to reboot instead of the web browser. M |
|
|
|
Beta 3.2b
253 ants scan time = 95 seconds
Speed increased 3.5-4.0 times.
No multi-segment scan.
No test 3 digit IP (192.168.001.002 - 001.253) sorted the problem, the problem actually is not too important.
Please try the latest version: MAntMonitor32rc2.zipI suggest setting the display refresh value to 5 and the thread count to at least 24. M |
|
|
|
Hi M, The 3.2rc did try to gp web based reboot, but unable. below the log: 9/1/2014 11:09:50 PM: ERROR when querying S1:2.117:80 (step 1): Object reference not set to an instance of an object. 9/1/2014 11:09:50 PM: Attempting to reboot S1: 192.168.2.117:80 via the web because the API query errored out. 9/1/2014 11:09:50 PM: REBOOTING S1: 192.168.2.117:80 9/1/2014 11:09:53 PM: An error occurred when parsing the web output for http://192.168.2.117/cgi-bin/luci/;stok=/admin/system/reboot?reboot=1: Object reference not set to an instance of an object. That first error message is curious. You say that goes away after you reboot it? M |
|
|
|
Version 3.2 release candidate is now available. MoreBloodWine: You might want to try this one. It still won't save properly for you, but I think reboots will work for you now. The web code is cleaner as well. This also includes the ability to attempt to reboot an Ant via the web if the API call generates an error. MAntMonitor32rc.zipM |
|
|
|
That is not what I expected. You're saying it's accessible via the web, but not via the API? In other words, you need it to rebooted via the web when this happens, not the API. M When ERROR appear, I still can use Ant Monitor to reboot it by use API setting. Okay. For now I have it written to use web reboot if the API fails. M |
|
|
|
I have $301 USD worth of Southwest (airline) vouchers that I probably won't be able to use. They need to be "flown" by 9/21/2014.
I'm selling at face value for BTC. At current price that's about 0.63 BTC.
M
Does the voucher need to be flown by or booked by 9/21? Flown. That's why I'm stuck with it. I thought it was booked by! M |
|
|
|
|
Show Posts
