There were two changes we made to this yesterday, one of them has been reverted to previous settings (essentially a lower overall difficulty). Please let me know if this helps, the second change we made is definitely a health improvement and would like to keep it as long as its not effecting MRR. We will continue to tune to make it possible for as many devices/services as possible to work on sha, the range of devices stemming from back in 2012-2013 to today is a vast range to cover when they computationally don't work close enough. Ideally we want to find a solid middle ground while making sure we are set going forward.The S9s that physically connect look healthy on our end, something about how MRR splits up jobs to their rented rigs must be a cause for them specifically having issues.

Regardless thanks for letting me know about the MRR issue, hopefully this helps and if not we'll try to get it optimized asap.

Ok, thank you for the feedback. From our end, what we have seen it terms of S9 performance (and similarly powered machines) has been an improvement. In regards to the d= field, the pool still supports this, its just that it only recognizes values that are close to the new overall difficulty (basically low and impossible values are ignored), this is probably what is happening to your MRRentals. I believe you had them set to d=20000 before the change, if that was the case, can I ask that you try omitting a set difficulty for now, just having c=BTC in the password field and we can see if that baseline approach functions fine? With the changes we made today, the pool should respond more effectively at setting a difficulty for the machine at a 6x improved rate of accuracy.

What we did today is meant to improve beyond what we have seen over the past several weeks and set everything up as best as possible for the next several months (assuming no hardware producer releases far advanced iterations of their tech). The numbers from our end seem promising, but we don't see how it is physically affecting machines, so we rely on input from you and others to fine tune the settings to support as many devices as possible. I definitely appreciate you being vocal with real-time data on how your machines respond to our changes, it helps us to know how we can make things better for you. 

In this case, we had several days worth of changes/improvements ready to deploy, but an issue that we deemed important to upgrade as soon as possible for the benefit of miners was the reason we didn't give advanced notice. Ideally we want to ensure that normal updates have advanced notice, but for issues where we believe an immediate deployment is the best case for everyone then we'll use best judgment going forward.

As for the 14 2Pacs, there is a change to diff that we implemented which could be causing that. I'll go ahead and look into it further to see if tuning the difficulty down in the range of the 2Pacs can be accomplished without hurting S9s and capabilities of that nature. I can manually make a change now and if you wouldn't mind giving me performance feedback tomorrow after it has had some time for you to see results,  I can then tune it further to optimize things.

Update: We made another change based on your feedback, so apologies that it probably knocked your MRRentals again, but based on what I'm seeing so far, it seems to be a decent health improvement for S9s based on difficulty. That being said we are going to spend more time the next few days coming up with a plan on how best to allow the 2Pacs and devices of that nature. With the current network situation of all sha256 coins, we want to make sure that finding blocks is efficient and as profitable for miners as we can make the pool from our end. The changes we made today allow smoother operation of S9s, Nicehash rentals and further tech as network difficulty keeps rising. I'll continue monitoring and adjust as I can to benefit you and others on the pool, at the same time we won't restart unless necessary from this point forward.

Yeah exchange support does seem to be increasing, but still not enough to make LCC that profitable. Also the hashrate and difficulty of the LCC network appear to have pretty volatile swings that just wouldn't be decent for profitability at the moment. At the time of this writing its about 3-4x more difficulty to find than DGB and its value is down a decent amount as well. With BTC up again the ratio is dwindling with people dumping LCC, not enough buy support on the exchanges to prop up value. Also some exchanges don't even allow deposits even though they have their markets for LCC open. We'll still keep watching to see if the situation changes, but for now we are doing a lot more coin evaluations to add/swap in when it makes profitability better.

Hello,

Pending balance is the amount of blocks that you are continuously finding, it seems like you had been mining steady and as a result your pending balance is growing. Also, it appears you had a period of downtime around 16-40 hrs ago at the time of this post and yesterday your balance wasn't moving because of the period of time you didn't mine on the pool. As you have returned, the balance begins to move again after the 24hr mark of your return of finding blocks with the pool. The pending "catching" the balance is all based on when blocks confirm and also how steady you stay connected to the pool to actually earn balance. Everything is working as it should and hopefully that answers your question.

I mentioned in my last post that we were going to be focusing on x11 and attempting to improve what we are able to improve. Since our last post, we have added a few new coins into the rotation and disabled a few that were causing "luck" to play too much of a factor. The results so far look promising as we have seen x11 go from hovering between 0.02-0.023 actual yesterday to now today it is currently sitting at 0.03393 mBTC/GH/day. We are still monitoring and helping out when and where we can.

A few notes, looking at your account that you listed previously, you have some periods of downtime (scrypt) and some on x11 as well. Not being live will of course affect daily rates. Also LTC is up in value 8-11% over the past 24hrs while Bitcoin and most x11 alts have stagnated or dropped so that exchange rate will naturally be a cause in daily difference. Another point I'd like to make is that even though you were paid 0.16156037 LTC today, you have 0.56LTC pending confirmation. In reality you have earned more than 0.16 in the past 24hrs, its just that the other x11 blocks haven't been confirmed or exchanged yet and are pending. Once they confirm and exchange it gets added to the balance.

We spent a lot of time recently researching x11 coin options that are able to be deployed. There are definitely a few more under evaluation to add if and when they become a confirmed benefit, but for now we have what we believe to be the best options that are sustainable. There aren't many things on your end that would improve the situation, its just where the x11 network is compared to months or even weeks ago. My goal is to make sure that you and the rest of our community can be mining the best options and we won't stop trying to get to that goal. The changes in the last 24 hrs will definitely help.

Absolutely and trust me we try to ensure that which coins we offer have the best outlook going forward. Each day becomes a different story based on not only coin difficulty, but also the profitability of those coins for that moment when it is found. On x11 specifically many coins have decreased in value relative to BTC's growth for the past few days and a couple have increased. The other factor becomes how many miners show up each day as they earn a share of what is found. The only factor that we have control over is what coins are put out there for our users to try and find. Everything else, price, difficulty, luck, etc is all external and we wish prices were where they were at in December, but with this rising difficulty prices haven't grown in parallel. We'll always be on the lookout for ways to improve things, especially what we think is the best fit for our community.

The number .27 you gave is based on how much is confirmed and paid to you in that day from your last matured balance payout. From what I can see, you still have a decent pending balance that is awaiting confirmation and also it seems you turn some machines on and off, so its hard for me to speculate what is going on without knowing your hashrate/machine average beyond the past 24hrs.

Regardless, our goal is to make sure we put good opportunities out there for everyone to find and we'll continue that.

There is nothing wrong that I can see, SaveTheOcean (STO) reports a bit differently where it doesn't immediately notify the wallet page that is has been found like the other cryptos do. It takes roughly 15-25 minutes to mature and report as found. At the moment I'm seeing around 26 blocks (3 of those being STO), so I assume that the last hour had a few more that are in the maturation process. Some hours are slow as we try to find higher difficulty blocks, some hours produce many small ones. It all varies on hashrate and what coins the pool is trying to find based on the profitability of that moment.

We've been monitoring it closely as well, many aspects of LCC are very volatile right now and make it difficult to support until things become predictable. If things do change to the point where we feel comfortable knowing that it won't affect miner's earnings negatively, then it'll be considered for deployment soon after.

We've added a decent amount of cryptos in the past few days and are working through our list to see what else would be viable. Lots of options, just need them to actually benefit our community.

Each day is a different story, when BTC directly is up around 31% in value over a week it affects exchange rates of alts. Depending on if those alts follow BTC in value, stagnate, or fall effects their "profitability". Luck plays a factor, time, hashrate, momentary difficulty and much else. That being said, we have quite a few sha256 coins in testing right now to add which we believe will help. They will be rolled out as they appear ready for live usage. 3-4 have already been pushed live in the last few hours. We constantly look for new options, but my past experience shows that most of the time there are sha256 alts that are more profitable to mine than direct BTC.

The past few days have been generally rough for most of the coins on x11 in terms of value/exchange rate while LTC and BTC have risen during the whole LitecoinCash pump. With the downtime of x11 and the MONK issue yesterday x11 did not perform ideally, but we are looking at what other options as far as coins are a solid option. The 24hr estimate right now is promising and whatever else we can find on top of that will be helpful. We are going to be more strict in our deployment of new coin options to ensure issues stay to a bare minimum.

Thank you for catching that, we are in the process of creating a knowledgebase for the site to further explain such things. Now that I know you are interested in those two specifically we'll try to support them sooner than others. Also we only disabled DGB for mining on sha256 as it was affecting profitability. It is still on Scrypt, but doesn't have great profitability at the moment so we don't search for it too often. That changes daily, and also they have a rather important update happening soon which will force an upgrade at that time.

The "in-stock" amount we have of those coins is based on how well the pool does at finding them. As we grow it will become a lot easier to find and provide those as an alternative to just our current guaranteed payout coins. Its difficult to currently guarantee many beyond the main two of BTC/LTC, but everything is logged regardless and if we notice that someone selects a different coin, we'll see about making it an option if the situation changes in favor.

We are looking at a list of algos that we would like to support especially those that open opportunities for GPU/dual mining, etc. One of my main priorities is to ensure that if we do grow in that direction, that enough care is still given to the already existing algos and thoroughly test everything. We are close, but any issues that pop up are given immediate priority to fix and then monitor.

If you have any specific algo/coin requests, let us know and we'll see what we can do.

Correct, I have disabled it as soon as that occurred and will do testing before pushing it live again. It was working fine and passed our initial tests for the past 4-5 hours and then had issues again creating orphans.

I took a look at the address you linked previously, and in the backend it appears that for the past few hours the mature balance is growing while your pending total is being converted into the confirmed balance ready for payout. The movement/confirmations you see now is all related to what happened exactly 24 hrs ago and what you found while active during that time period. The graph should be much more clear tomorrow once the MONK issue is no longer visible (the y-axis should adjust scaling and show your pending/balance movements more clearly). Everything is working as intended since we fixed the MONK issue several hours ago and should continue to. Regardless, we will continue monitoring to ensure everything is correct.

We do have plans to support equihash in the near future, needs to go through a bit of testing to ensure smooth opening as it uses a couple different techniques than other algos. While we want to expand, I also want to make sure the foundation is solid, systems produce very little error and that the userbase is satisfied with what we offer.

At the moment we guarantee payouts in BTC and LTC, the other currencies are based on available stock and how well our pool does with finding those block rewards. We see a fair number of people signup and try to be rewarded in specific currencies besides the main two when we don't have those in stock at that specific time. That being said we'll notice and try to see what can be done to fill those if possible.

Any feedback/suggestion is always welcome and we'll see when we can put things into effect in as proper an order as possible.

Hello,

For a period of about an hour, the MONK coin daemon created orphan blocks that artificially grew balances when the system believed they were real for a short period. The issue was fixed as soon as possible and it should now be functioning properly from this point on. MONK is a pretty large profit coin and is usually very difficult to find in comparison to other options that bring in regular and stable growth. The live x11 status page is the best place to see when these orphaned blocks happen if they do. The wallet page does not reflect any orphan blocks, but we leave them visible on the other page so you know what actually happened to each specific block.

We are working on something to make it more clear if situations like this ever do happen, but it is very rare regardless. I apologize for not updating site status sooner to inform of the situation, but we wanted to review everything on the backend to ensure it is fine moving forward.

A few days ago we tried using Nicehash for sha rentals again and have confirmed that one of our previous plans is a good option. Basically we want to be able to support a broad array of devices. People who still have miners operating in the GH/s range need a lower difficulty option and those using S9s or as high as Nicehash demands need a separate option so each category can run smoothly. I know we have been testing what would work best for everyone and we want to go through some further testing before making anything public. Making sure earnings are properly recorded is a big thing to ensure before making this live. Occasionally some of the sha restarts have been to apply some of these changes to see how machines adjust or improve with changes based on pool hashrate and machine type.

We are going through each algo and looking at what can be improved, many cryptos have increased in difficulty or decreased in profitability so we will continue monitoring each option as efficiently as possible. After many years in mining, I know how important it is to maximize your miner's efforts for time spent. There are a lot of things in the works that we think will help with that.

On your note about scrypt, we haven't adjusted anything difficulty-wise on our end, but the available selection of what cryptos the profit-switching is trying to find has a bit to do with what var diff is selecting. Certain coins just have better performance in job relay and we try to adjust depending on availability.

We do have an API, more info is located here.

As far as Litecoin Cash, we already have it on our list for review. It needs to pass a certain number of checks to be added, such as is it stable, what exchanges support it, how difficult will it be on sha256, is the profitability worth it, etc. If it passes our verification and seems like a decent fit, then we will support it and add it as soon as we can. I'll announce more here and on the site if/when we have an update on it.


After looking at the wallet you provided, the y-axis balance figures are still immature for your x11 earnings. It takes roughly 24 hrs after you first turn on the machine for immature earnings to confirm. Since your scrypt rig is not nearly as powerful as the x11, it isn't pushing the balance line up as much as it used to since turning on x11. Based on what I see, the balance should start confirming around 10pm EST tonight and the combined balance graph should grow more parallel.

Absolutely, and no problem, there are many things going on so even with what I listed there are other factors like BTC exchange rate as its risen quite a bit in the past few days. Some alts follow while others are stagnant at the moment.

As far as MRR locations, I'd say USA is probably a best bet for multiple reasons besides just latency such as stability. Latency plays a bit of a factor when the pool is sending job shares to each miner and needs to speak back and forth to the equipment especially when being relayed through MRR in a "hands-off" sort of approach. The cost effectiveness of a plan then also needs to be taken into account, if Singapore for example were to be a much cheaper option to rent over a period of 24hrs, then you would need to decide if that latency is going to reduce the hashrate earnings beyond what other locations would.