About my problem with wrong private key.
Solved, by a miracle! 
Of course, the mistake was not mine, I had no doubt about it.
So, all wallets and validators refused to accept my private key received at ICO, they say, "Invalid private key". I tried many wallets, and tried stupid "fallback" procedure (which is often recommended to the dolts who lost their private key), it did not lead to anything, only to generate a new key pair without balance. I wrote to Block.one support, to fifteen top block producers, to developers of popular wallets, to Larimer’s Twitter: all that I received - either general advices like trying another wallet, carefully checking the private key, and blah blah blah. Or simply ignoring. When I wrote to Block.one - I thought they would definitely help me - but I received all the same general advices, and excuse like "we will study the problem", and then I was sent to the telegram group EOS911 - "you will find pros there, they will help". Oh, yeah… I didn’t find any help there, but I was contacted by a couple of obscure personalities who wish to “help”, but in reality they simply wanted to lure my Ethereum, so they were sent far away.
Recently, in the hopelessness, I googled my problem again, and found this post -
https://www.reddit.com/r/eos/comments/b4rwp4/invalid_private_key/ -
man writed that, by some unknown reason, case of one letter of his private key changed. Already not hoping for anything -
I also began to try changing letter’s case one by one, and the seventh letter from the end worked!!! So account was returned.
And reasonable question - what the hell??? When generating, I used only the official site eos.io. When private key was created, like any literate person, I copied it (Ctrl+C, Ctrl+V) to Notepad and encrypted it. (I didn’t use any validators or generators then - why to shine my key in some third-party services when it could be easily created through an official site. And I didn’t bother with checking offline) If someone says that my PC could be buggy and to change one letter from 51 – no, it’s from fantastic. A PC with such level of errors would simply not start, Windows would immediately fall into BSOD. And yes, I tested my PC with stress tests, many hours, both memory and CPU – no any error. And no overclocking. And there are some similar complaints on the network about broken private keys.
Obviously, generator on official site fed ICO participants with invalid private keys with one letter changed (at least). Maybe in one case out of 100 or out of 200. It’s hard for me to come up with a word to name “Block.one” company.
P. S. It would be great if somewhere in archives there is saved that page from site eos.io, on which the key pairs were generated. Then could be tested to receive proof.
