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. |
|
|
|
What are the approximate dimensions (L x W x H) of a single packaged S3 and it's approx weight in lbs ?
Ty.
The packing box is around 14 or 15 inches long and 9 by 9 so 14 by 9 by 9 the box weighs 13 lbs Ty for that philip. |
|
|
|
|
What are the approximate dimensions (L x W x H) of a single packaged S3 and it's approx weight in lbs ?
Ty.
|
|
|
|
I say screw it and just publicly discuss it because we already know s0br will make up for whatever he can if something turns out to be his fault. If it turns out to actually be MP's fault then we will know that too and then get watch him try to save face.
I've said it before and I still stand by it. Sure the pool is far from perfect, but it is still rather new. That said there are bound to be issues. So can we all just try to play nice, myself included, and try to fix whats wrong as a group or we can all continue our childish ways.
On any new pool there are obviously bound to be issues. Which is why the attempt to blame third parties for the issues confuses me. Full disclosure is the best policy and inspires the most confidence in the pool operator(s). Well I know I've directed a few things at you to which I have no valid excuse so I wont even try lol. That being said. if we can actually just try to work together as a whole for a change I do think we can figure out just wtf went wrong. |
|
|
|
|
I say screw it and just publicly discuss it because we already know s0br will make up for whatever he can if something turns out to be his fault. If it turns out to actually be MP's fault then we will know that too and then get watch him try to save face.
I've said it before and I still stand by it. Sure the pool is far from perfect, but it is still rather new. That said there are bound to be issues. So can we all just try to play nice, myself included, and try to fix whats wrong as a group or we can all continue our childish ways.
|
|
|
|
|
These are the approximate earnings of a single X3 module under current diff / BTC per price of $477 @ 1,000Gh/s.
per Day 0.01833509 BTC $8.76
per Week 0.12834566 BTC $61.29
per Month 0.55807441 BTC $266.49
|
|
|
|
|
Well, whatever reason I think we can all agree that whoevers fault it is needs to get it fixed. I know I've said and done a lot but as messed up as it sounds. The issues with pools does seem to follow multipool, so all bs aside. What harm would it come for you (flound) to hire someone who knows their shit to go over your backend. I know a lot of trust comes in to play but I'm sure doc from bitminer or eleuthria from btcguild would be willing to help and welome you in to their pools if the problems that seem to follow you can be fixed.
|
|
|
|
|
Even if it is a scrypt device, until we have system details and a price point we don't know if it will be a good or bad thing.
|
|
|
|
I heard that this list was cut down where can I view to see whos currently in the campaign I don't know if I was cut or not.
Anyone below Sr rank was cut. |
|
|
|
|
Lol at the last one, thats actually going a little too far with the whole nazi germany poke.
|
|
|
|
Or Bitmaintech is hashing against its customers....  Anythings possible but I would expect that from say BFL or BlackArrow before BMT. |
|
|
|
|
Can we all just agree to let the bitching and moaning go ?
This is a new pool, it's not perfect but what pool is when it starts out ?
In any event, time will tell / decide the fate of the pool so lets just let things unfold as they will.
|
|
|
|
Seems as if Bitmaintech took over snowball.io and is offering now cloud mining... don't know, though, if this is good....
Only time will tell but it could easily turn in to another ghash. |
|
|
|
Here's another beta of 3.2. This version adds a slider bar on the config screen where you can configure how many threads you want to use (2 to 64). It defaults to 5 (1 dispatch, 4 worker). You can change it midstream, however it'll abort the existing threads regardless of what they're doing. For best results you shouldn't do it while it's rescanning, but I think it'll continue to work either way. Of course you can save your thread setting so next time it'll start out at your new value It also tweaks a few more spots that could cause some data corruption because they weren't synchronized across threads. Download link: MAntMonitor32b1.zipYou're going to have to experiment with whatever threadcount works best for your configuration. Please keep me posted on your findings. Thanks! M Here's hoping the next release is geared towards me ;-p |
|
|
|
Getting close to 24 hours with normalized payouts. This is great to see.
Once the stability in payouts returns, I have a feeling that will alleviate a lot of peoples concerns. I know it does for me.
See what happens when MultiProxyPool.us ery left everything magically fixes itself back to normal with no coders fixing anything need I say more! If a user submitting shares completely breaks a pool's payout system, then I don't have much hope for that pool. So that means every pool you've ever jumped on has a bad system them ? Eligus, Bitminter, BAN, to name a few. |
|
|
|
FWIW, here are our shares and payouts while we were on the pool. This is with about 270-290TH and BAN always reported within 5% of our hashrate.
+-------------+--------------------+
| sum(shares) | sum(btc) |
+-------------+--------------------+
| 19440313760 | 15.393149373587221 |
+-------------+--------------------+
At the standard PPS rate (without the claimed bonus) we should have made about 17.8 BTC. With the bonus we should have made ~20 BTC.
So we are currently owed about 2.4 BTC at the standard PPS rate ignoring the bonus.
Let me know when you get things worked out and we'll be back.
Did your pool leave about 18 hours ago roughly? That is when the payouts normalized. If this is the case, maybe it is worth contacting the operator to see if something can be done technically to fix the issue. What he has is no where close to a pool, I mean a pool of miners with no actual pool anyway. But yes when he left is when payments normalized, the same thing happened on bitminter which I hear hes banned from. Also caused issues on eligus and btcguild. |
|
|
|
Left a week plus ago to let things get addressed, have the payouts (amount and time for payout) and bonus been fixed yet? Don't care about all the S3 controversy. Thanks.
Payments are still jacked for some people but my last three have normalized. Now whether or not this continues remains to be seen. As for backpay, I doubt we will see that fixed until s0br is back online. |
|
|
|
This payment situation is getting kinda ugly. Just got back to my 'wallet' PC and uhhhh....  My last two payments were normal for my hash with bonus, 0.0054x I doubt it'll last though even though I hope it does. That being said, hopefully when s0br is back he can chime in on this patch I hear about. |
|
|
|
Seems like payouts are still around 15% short, not including the bonus.. Will these be fixed soon?
You just have bad luck with Bitcoin pools, don't you? Maybe you should just make your own Bitcoin pool. You've got a pretty big user base as it is, I bet you could do it. It's not really an issue of luck and yes I just might do that. All jokes and jabs aside, it would more than likely solve a lot of the problems you run in to since you would control the backend etc. |
|
|
|
Seems like payouts are still around 15% short, not including the bonus.. Will these be fixed soon?
Sure wish we knew what started the payout problem  |
|
|
|
|
Show Posts
