I'm having a hard time following what you're saying exactly, but I believe you're upset because we had issues with SUM.
To clarify, actually 'everyone' did not know SUM was coming and/or that it would be popular.
Additionally, if you take a look at the BTC Talk thread regarding SUM, you'll see that over the first 90 or so pages, most pool operators had issues getting anything working with this coin.. it is because they made a mandatory donation come out of every block found. We use stratum software that does not have this programmed in. To alleviate this, we setup shared mining with one of the 3 working pools that has this setup. That pool could not handle the number of connections we created when we put SUM on the multiport, so the port was taken down.
I do apologize that you rented hash for this, and chose only TMB to mine with -- we were very late in adding SUM, and there are other pool options out there for you.
I do my best to get all the higher profit coins added to TMB as timely as I can, but in situations like this, there wasn't much else I could do. When mining profitable coin launches such as SUM, you should definitely setup more than one pool as pools have issues quite often. In fact, with SUM, all 3 of the working pools have had significant outages since the launch.. and none of the main 'stable' pools have picked up the coin at all.
Estimated BTC/Mhash/Day as listed on our website is just that, its an estimate. There is no telling how the market will react with a bunch of coins being sold, nor is there a way of foreseeing stratum issues.
Again, I do sincerely apologize if you did not or have not got the return you were hoping for.. but I can't make any guarantee's regarding ROI.
I accept your apologize, but you did not need to apologize. From beginn on first 24 hours I assumed some malfunction in a pool. At this time I was already 3 times in loss. The only reason I went for 24 hours more was to see how it performs for next 24 hours (especially because of the launch of SUM (which I indeed expected earlier)).
Like I said, i was not only mining on tmb and I always have backup pools and normally they are never same coins. That's the reason why I am not totally in red, still, the loss is big.
Maybe I expressed myself wrong, not everybody is up to date. I assumed that you are prepared for sum because I know you are mostly up to date.
I am not upset of the issue with sum or in loss of some investment. This would be silly. TMB had low rates, did you ever hear me complaining about payouts? This case if totaly different!
In this case something is not correct. Let's put sum back and talk about first 24 hours, >70mh/s (mostly JUG) and only 0.06 after 24 hours (unconfirmed was something over 300 JUG's at this time). It just does not fit to any calculation and for me this is not explainable and NO I do not orient myself on speculative value posted. I always assume that this is ~expected/current value. if I count 50mhs => 0,006/50=0,00012. This was my rate in first 24 hours, real one and not speculative.
I did not ask you to pay me back my loss, but I would if my coins went to someone's else account. It's quite suspicious what happend. With two rigs I am almost from beginn on with TMB. Never something like that happend. If there is an issue with the pool which makes losses for me like last one and other people have good profits on same pool (I was on both US and EU servers), then you should take closer look at it. Taking into count that my hashrate was ~5-10% of pools hashrate, how much should I have had for first 24 hours? I would like to see some numbers and accounting explaining 0.00012/Mhash/day. Really, I can't explain it in numbers, can you?