Yes, you're right. You figured it out but I'll repeat here for others who might be confused.

This is a bulk transaction in which sub-0.001 balances were transferred from CM1 to CM2. On your payouts list you see an actual value which was transferred for your username, but when you click to look in the block explorer there's a bulk value of all user balances combined. If you see this, it means that this "payout" was credited to your CM2 account.

Yes, old unexchanged balances were explained here: https://bitcointalk.org/index.php?topic=448649.msg13714576#msg13714576

In short: they were post-fork blocks for some small coins from 2015 and even 2014 which were mostly orphan blocks but CM1 software failed to mark them automatically as orphans (because some of them might not be orphans). I reviewed them manually and recovered all valid blocks in January and they were paid out at that time. Invalid blocks were recently corrected to zero after confirming that they were actually orphans.

100.00% of actually valid blocks from CM1 were exchanged and paid out (actually, even more, because when doing manual review I found out that some invalid blocks were also paid out in 2015 before they were marked as invalid; so the pool actually mistakenly paid ~0.45 BTC more than it mined).

Hi everyone,

it's great to see that you're happy with CM2 and that profitability returned back to high levels. Great work PPanther!

I just wanted to let you know that I made the final settlement and that the final payout from CM1 was sent yesterday in this transaction: http://btc.blockr.io/tx/info/8e246297cdf63be825f0b47ca1207e23aaf977bc066768bd0e30a7391c0d18b2

All users with balances at least 0.001 BTC at CM1 were paid in the above payout.

For amounts lower than 0.001 BTC, it's not feasible to send such low payouts because transaction fees would be too high compared to payout amounts. I didn't want to leave you with unpaid balances even if they were 0.00025 BTC or $0.10, so sub-0.001 balances of all "somehow active" users were transferred to CM2. I sent them to PPanther in this transaction: http://btc.blockr.io/tx/info/949554f2f34beb64a06c8ffea58a4230fc461d0572a995d0258ed944788955c5 and also sent him list of usernames and their balances. He added these amounts to your CM2 balances.

There were ~600 active users at the beginning of the March when the switch to CM2 was made. I transferred balances of all users who were active up to three months before, so for anyone who submitted even a single valid share since Dec 1st, 2015 (this is how I define "somehow active" usernames). There were 1993 usernames satisfying this criteria, including 1622 usernames with sub-0.001 balances, so balances of 1622 usernames were transferred to CM2 with a total of 0.43319776 BTC (so on average 0.000267076 BTC per user). This way everyone should keep their balance, while we won't clutter CM2 database with thousands usernames unused since 2014.

Once again thank you for being part of CleverMining during my ownership and I wish you amazing profits and experiences in the future at CM2!

Hi everyone, I have a major announcement to make. We’re launching CleverMining 2.0 today!

Here’s what changing:

• CleverMining 2.0 is launching today.
• It uses the same state-of-the art stratum server and the best profitability engine it always had, but improved to achieve even greater profitability.
• It introduces new website, new mining stats and most importantly new coin exchanging+accounting engine which should improve exchanging process.
• Much more coins are added again, heavily extending number of our supported coins to further improve profitability.
• A new but experienced pool operator will ensure pool support and development will return to its best levels (welcome PPanther).
• All the above should greatly increase profitability and quality of support.
• To celebrate these changes, fee will be reduced to 0% for the first week of CM 2.0.
• After that, payout model will change to PPS, making your earnings more predictable.

As you know, in recent months I did not have enough time for active development of CleverMining and for proper support for users who had questions or problems. This was caused by personal, non-pool-related issues. I decided that the pool and you, the users, deserve only the best and I didn’t want to continue running the pool half-time with average results. I found an experienced and skilled pool operator who agreed to take over the pool and invest significant amount of his time and energy to develop it further. He spent most of his time since beginning of the year to improve CM and develop CleverMining 2.0. The visible changes on the outside are small, but they’re huge on the inside and all this has only one goal in mind - to improve profitability, bring back great customer support and improve your overall experiences with the pool. Please welcome PPanther as the new owner and operator of CleverMining. He’s been operating LTCRabbit mining pool for years. You’re in very skilled and capable hands and I’m really happy that CleverMining will be actively developed and the great legacy will continue despite me not being able to be part of it. I believe you will also be very satisfied with the change. Thank you for more than two years of using and supporting the pool and I wish you even better and more satisfying years of using the pool in the future.

From technical perspective, the change to CleverMining 2.0 will be quick and smooth. You don’t need to do anything and most likely you won’t even notice anything at your miners. Your miners will be disconnected and they will reconnect to CM 2.0 servers to continue mining. The old website and all historic stats will still be available at http://old.clevermining.com and final payouts of all remaining balances from CleverMining 1.0 will be made over the weekend, after last CM 1.0 mined coins will be exchanged.

If you have any questions, we’re both here to help.

Your account has regular payouts as soon as you meet required payout threshold.

You currently have 0.0001 BTC immature, 0.0001 BTC unexchanged and 0.0012 BTC ready for payout. Everything looks fine to me and you should receive your payout when the next >= 0.001 BTC payouts will be sent.

Thank you all for kind words. It's great to see users coming back to the pool

Hello everyone, I'm back.

I started processing unexchanged balances and was able to recover ~17 BTC mined in 2015 and stuck since then. They were manually exchanged and paid out earlier in January in few batches. Since beginning of the year until yesterday we mined ~98 BTC but we paid out ~115 BTC. The additional ~17 BTC were recovered unexchanged balances.

I'll be reviewing remaining unexchanged balances after the weekend, but preliminary checks show that most of what's left are orphaned blocks from 2014 (~29.4 BTC) and 2015 (~12.7 BTC). These were crazy days of altcoins with dozens of altcoins popping up and dying every month and their blockchains were forking like crazy sometimes. In cases of forks which were not resolved quickly, but were having competing blockchains living concurrently for dozens or even hundreds of blocks, our software didn't zero-ed blocks which it thought to be orphaned (mined on the wrong chain) but left them for manual review, just in case. I am going to manually check all these remaining chains and correct their statuses to orphaned (worth zero). Of course if any of them were not really orphaned, they will be exchanged manually and paid out as were the recovered blocks earlier in January.

Overall, I estimate there will be ~42 BTC unexchanged balances corrected to 0 BTC. This is only an accounting loss. As I explained before, these blocks were not correctly mined blocks and were wrongly marked as unexchanged in the database (while they should be marked as orphaned). We already did a similar correction of post-fork orphans in 2014 when we wrote off ~19 BTC. In summary, these total ~61 BTC written off now and then, in the entire CleverMining history, make only 0.15% of our total 39,271 BTC paid out in the entire history. In reality they make approximately no more than 0.03% of entire hashrate, because when such forks happened, post-fork blocks difficulty was very low and we instantly mined dozens of worthless blocks (but theoretically worth 300-1000% profitability) before our software switched off from the forked coin. So in reality, much less than 0.15% hashrate was wasted on this, I estimate it at 0.03%. This is a cost of running a multipool - the more altcoins, the more forks and you sometimes lose a 0.01% here or there due to forks. My fault was to leave these blocks unchecked for such a long time instead of deal with them instantly.

After this accounting correction will be done, I will be adding some new coins (and re-adding previously disabled coins) in the next week to improve current results. The pool currently does not suffer any issues and I encourage everyone who mined here before but stopped to switch back to CleverMining.

If anyone has any unresolved issue, unanswered question or needs any support, please PM me and I'll try to help!

Please stop spamming with others pools advertising in this thread.

Mining is a random game. Miners are trying to brute-force the next block hash and they do it with various luck. Your calculation shows expected/average number of LTC earned / blocks solved if miners' luck was 100%. Actual number of blocks solved will vary in short term (days), but it will be according to expectations in long term (weeks or months, depending on pool hashrate). If the pool is expected to find 10 LTC blocks per day (this is not a real number for CM, just a round number for example), it might as well find 5 blocks or 15 blocks in any given day.

Additionally, after mining coins, we exchange them to BTC and payouts are not always covering exactly 24-hour periods. If latest withdrawal from exchanges before sending payout was at 23:00 two days ago but at 19:00 yesterday, it means that yesterday's payout covered only 20 hours between 23:00 and 19:00 (and the next payout might cover 28 hours between 19:00 and 23:00 next day).

tr;dr: you should look at long-term stats and don't worry about daily stats as they are vulnerable to mining luck and other minor factors.

We are mining LTC every time when there are no more profitable altcoins. It's just variance - sometimes we find more LTC blocks than expected and sometimes less than expected. It's normal at every pool. Today's profits are already better.

Regarding payouts which blockchain.info block explorer didn't found at first: blockchain.info has an issue that they don't like transactions with more than 200 outputs (and we send payout to ~1000 users in one transaction). They ignore such transactions before they are confirmed. The result is that shortly after being sent, these transactions cannot be found on the blockchain.info webpage (they can be found on any other decent block explorer though). Blockchain.info will show them after the first confirmation. There's nothing to worry. You simply need to wait until the transaction is confirmed or use a different block explorer.

I just changed our website to use links to a different block explorer instead of blockchain.info.

You can point any number of miners you like to the same address and all their earnings will be added up and paid together. You seem to be connected to the EU server at the moment.

You were probably trying to mine SHA-256 algorithm with a bitcoin-compatible miner. You need to mine using scrypt algorithm with a litecoin-compatible miner.

Your balance is 0.00100648 BTC. Balances below 0.01 but above 0.001 BTC are paid weekly on weekends, so you should receive the payout on Sunday.

Please check for wardware errors reported by your mining software. If you have anything above zero, then it's most likely causing the issue. Perhaps your gridseeds are overclocked and you get less hashrate (due to errors) than if you used lower voltage?

Manual difficulty has been temporarily restricted to minimum 1024, so it was set to 1024 if you tried to use lower value. I can't remember why - probably there were some issues with bandwidth usage in the past. I will check it and re-enable lower difficulties tomorrow. Vardiff still goes as low as 256 so perhaps it's best to use it for now (it's best to use it anyway unless your miner has some technical issues). It will start with 1024 but should lower the difficulty after few minutes.

It's my fault. After finishing maintenance and running manual payout on July 15th I re-enabled automated payouts but forgot to restart the application so the change didn't actually took place. I restarted it yesterday and automated payout ran this night: https://blockchain.info/tx/f1dd7aa0ae60245641da1ec78d09bce26ae59c5c09060c74737d38d08a17e54a

It's all back to normal with automated payouts now.

I won't tell you about GPU errors, but assuming that everything else works fine on your end, you shouldn't worry about "requested work restart". It simply means that your miner got new work to hash from the pool.

It was included in the first block mined after transaction was sent and blockchain.info shows it now: https://blockchain.info/tx/3cf3c92ff0615cedf3647db4bddb9c0fa98ae69439798941a7130023b45cc779

Blockchain.info doesn't really shine these days. I need to change website links to use a different block explorer.

Transaction was sent with 0.00460157 BTC fee (which makes it 0.000148438 BTC per 1 kB) and I think it should be mined soon.