I think you might have misinterpreted what I said. The fact that 30% coins moved from a benevolent to a possibly malevolent actor(s) and that PoS is in effect is opening a lot of unwelcomed scenarios in case the devs do not rollback. So I understand why they have decided to do so. However, if PoW or PoW/PoS were in effect instead of pure PoS, the number of unwelcome scenarios would have been much less.

Given that about 30% of total VRC have been stolen and that 51% of staking coins are sufficient to gain control of the blockchain, I would guess that it is a pretty high possibility that use of the stolen coins to fork the chain would be successful. So, I understand why the devs would roll back the chain, as the loss of control would likely be permanent otherwise.

Now, about the viability of BC clone PoS coins, you've just seen a major weakness in an attack that didn't cost a lot with regard to fiat currency spent to accomplish it. Investors should think long and hard about what happened here, this could be a death blow to this type of PoS...

@ipominer, TRUST has reached block 12800 and beyond, so mining now should be over...

Stealth addresses (Sx) are a mechanism that provides transactions with better privacy protection than regular transactions. A receiving party generates a key that it shares with the sending party which becomes the basis for the transaction. The transaction is obfuscated on the blockchain. As far as I understand it, there is no mixing of any kind. It seems they have implemented it in a way that is relatively simple to use; if you think that the reddit explanation is complicated, try http://coin.cubeconnex.com/poollist and click on Stealth Address for alternative one.

With regard to the Sx code being closed source, I think that is due to VTC team's frustration that some of their code was being aped by other coins without giving proper credit. From their thread it seems they want to publicize the fact that they are the first to implement Sx and once that is done they would open the code. I would give them the benefit of the doubt here, that team has been one of the few that has been on the up and up with regard to promoting open source development.

Edit: Some of the screenshots reference Monocle, which the VTC team released to support merged mining with other N-scrypt coins. The Sx feature was first released on the Monocle mainnet, and today on Vertcoin's. Don't let the references to Monocle in the screenshots confuse you, the mechanics of a end user utilizing Sx are identical.

[I truncated the previous conversation so it does not take too much space]

The fact that you are asking me this probably means that you are running only one, but here is how you can check.

In Windows, go to Control Panel, and from there to Region and Language (this is true on Win7). From the dialog box that will appear click on the Keyboards and Language tab, and once there click on the Change Keyboards button. A new dialog box will appear. If on the list in the Installed Services frame you see a single keyboard format like US or whatever your input language is, then you do not need to worry multiple keyboard layouts, you only have one. If you have more than one in that list, then you can cycle through them with Left Alt + Shift once you cancel out of the all dialog boxes you just opened.

Just a thought... Are you running multiple keyboard (language) layouts in Windows? Is it possible that you might have entered the password using one keyboard layout, and are now using another one i.e. having a separate English and your particular language keyboard layouts?

Same thing happened to me when I decided to give up on maintaining a local wallet + stake and tried to move everything to Bittrex. I kind of followed what mindfox recommended while back:

1. Run checkwallet in the debug window. Given that the message is about coin mismatch, you are likely to get back a message that some amount of coins is out of sync.
2. Run repairwallet in the same window.
3. Retry transaction. It is possible that the amount you originally tried to transfer might not be available, but it should become available after waiting a little bit. If the original amount was less than 1/2 of the value of your wallet, it is likely that on the next try you will succeed (i.e. will use coins from other inputs in your wallet). If you don't have enough funds, just wait for the coins from the original transaction to be "returned" to your wallet.
4. In case 3 fails again, repeat starting from 1. You will eventually succeed.

By free estimate, I had to do this 8-10 times until I moved the whole content of my wallet. You also might need to close and reopen the wallet as well for the missing amount to appear.

As always, back up your wallet before attempting anything.

Good luck!

The 0.3 XMR should be sent back in your wallet. If you haven't yet done so, when you refresh it, you should observe a number of spent inputs for the 1.3 XMR + one 0.3 XMR incoming input being reported in the block number you observed in the block explorer. The 0.3 XMR is just your change from the transaction. You can also look at the simplewallet log to see the refresh output, if you have already refreshed and missed seeing this.

The x64 VC++ 2013 redistributable from your link fixed it, thanks!

Yes, I get the same error.

I am sorry to hear that. I enjoyed my experience mining at your pool, the least amount of hassle and regular payouts. Hopefully, it may be worth your while in the future.

Thank you for that, much appreciated!

So, I am one of the 12 miners on your pool, been mining for the past three days and I am likely the one with lowest hashrate. Is it possible that a link to the improved Win64 simpleminer executable is provided either on your pool or here? I have no way to build the binary...

Did you account for orphans? Look at your pool and see what the percentage of orphans is. Subtract that percentage, and you probably will end up close to what you got paid.

I hope I am interpreting your screenshot correctly, but if you are moving XMR to Poloniex, you will also need to add the Payment ID, which seems to be missing from your commands. Your friend or you (if you have access to his account) should generate the Payment ID at the Poloniex's Balances page. Once you generate this, you send XMR with the following:

transfer 0 <Deposit Address> <amount> <Payment ID>

I put mixin count of 0, but you can replace it with whatever you prefer. Of course, remove the < and > when typing the actual transfer command

Hadn't opened the wallet in more than a month, staking like crazy now with the new one  

This just got resolved. Thank you for fixing it.

I am not sure whether this has to do with your restart of the pool server, but blocks that are shown as matured are not being classified as valid or orphans and it seems they are not getting paid either. Can you please check?

Make a batch file with the following content and run it from the folder where you unzipped the miner:

setx GPU_MAX_ALLOC_PERCENT 100
NsGpuCNMiner.exe -o mine.moneropool.org:1111 -u 47..... -p x

940 H/s with 3x280x  Nice job!