It worked! 
Topic: BTC-e LTC withdrawal issue: "Wrong address!" error message (Read 1592 times)
Thanks for the help! It worked!
It worked! 
"If you get a message - "Error: wrong address!" You need to clear the cache in the browser."
https://btc-e.com/news/100
https://btc-e.com/news/100
I had this problem the other day trying to withdraw btc, it looked like when I pasted my address it was adding an extra space to it so I hit the backspace key once making sure I didn't delete any characters and it worked after that.
I'm getting same message - on an address used before a few times and pasted via notepad so no dodgy characters in it (have had the non-printable characters issue before - and it's not that). So looks like a glitch at their end.
A quick forum search found someone with a similar issue last year when trying to draw BTC to a valid address and receiving the "Wrong address!" error from BTC-e. I am currently facing this trying to withdraw LTC 98,99 to: LhBsKsZo5z5KAxHc3me2uGXrrDVHStNEEF
Is this just a temporary BTC-e hiccup or am I missing something?
Is this just a temporary BTC-e hiccup or am I missing something?
There is the possibility that your copy and paste includes a non-printable character. This happens with Facebook, for instance, where they insert some character so that the browser will wrap the address to the next line if it is too long. The Bitcoin.org client was modified to strip and discard any non-printable characters. It is possible the Litecoin client didn't include this same fix.
Try copy and paste to something like notepad. Then copy and paste from there into BTC-e. The problem might go away then.
If that doesn't fix it, you might try contacting their support on BTC-e's real-time chat.
A quick forum search found someone with a similar issue last year when trying to draw BTC to a valid address and receiving the "Wrong address!" error from BTC-e. I am currently facing this trying to withdraw LTC 98,99 to: LhBsKsZo5z5KAxHc3me2uGXrrDVHStNEEF
Is this just a temporary BTC-e hiccup or am I missing something?
Is this just a temporary BTC-e hiccup or am I missing something?
Jump to: