[daisyhotsauce]

Are there any tried and true type wallets to help avoid this?

[btcmacroecon]

(03-07-2015, 11:41 AM)Tsquared Wrote: The lesson here, to check the functionality of a wallet before depending on it to function properly, is a good message for everyone, regardless of what actually happened with your situation.

That said, I have two suggestions:

You said that the brute force attempts tried different variations on the characters in your passphrase. Did you try variations in your spaces? Two spaces instead of one or no spaces at all? I'd try this randomly between the words in the passphrase.

More obscure possibly could be this: I deal with text files quite a bit in my job. I am aware that the hexadecimal encoding of "ENTER" is different between ASCII and EBCDIC. This causes problems for us sometimes when someone creates a text file on a mainframe machine because the "end of line" representation on a main frame (EBCDIC) has a hex value of 0A (Line Feed) but most modern systems represent the end of line as 0A0D (Carriage Return, Line Feed).

Maybe this is all BS, but you mention a non-standard keyboard, so I'm wondering if it's possible that you hit Enter after putting in your passphrase, and it added an invisible character, a Line Feed (hex 0A) to the end of the passphrase.

This is really a long shot, but I think you can type a LF only (instead of CRLF) on a modern keyboard as alt+10 (http://www.theasciicode.com.ar/ascii-control-characters/line-feed-ascii-code-10.html) so maybe try it by entering the passphrase then alt+10, then hit the regular Enter key or Okay button or whatever and see what happens.

​TT

I'll try the long shot! What the hell! Yah the keyboard deal....who knows...that's where it just goes right over my head. I don't intend on becoming a keyboard layout expert and the amount of time at this point, it's a LOSS. Total loss, though I will go with the long shot....but yah let the lesson be learned (I know I did) but also for future reference for ANY coin, surely the developers of the coin can start this as a disclosure on their homepage where people download the QT for safe measures. That should be the first protocol for all coin developers and to help cryptocurrency in general, but that disclosure is better than someone having a problem and then all the blame goes on the user when in reality it could be easily disclosed BOLDLY. There will be many more people entering cryptocurrency, why not show a little proactive concern for supporters of the coin?

[btcmacroecon]

That's my point! Before you load ANY wallet, and before you encrypt it, test it with a small amount from like a Faucet or something, and make sure it SENDS & RECEIVES BEFORE ENCRYPTION, AND THEN TEST IT AFTERWARDS IF YOU ARE GOING TO ENCRYPT IT. THE RESPONSIBILITY WILL BE ON YOU,  SO TEST IT AND DONT ASSSUME THAT BECAUSE IT RECEIVES THAT IT WILL SEND. THIS ALL COULD BE AVOIDED IF THERE WAS A DISCLOSURE JUST LIKE THIS, BUT THERE ISN'T. SO BE WELL AWARE YOU NEED TO TEST IT.