Thanks a lot well.attenuated, this is exactly what I was looking for.

Quote from: well.attenuated on October 15, 2015, 08:48:22 PM
The option to export a private key is still missing, but it's planned to add it. In the meantime, you can do this:

In the javascript console of your browser type, when the wallet is unlocked

WalletDb.getPrivateKey(PublicKey.fromPublicKeyString("BTS...")).toWif()

Where BTS is your owner public key. This can be imported into the CLI wallet or another web wallet.

Edit: Credit to mindphlux for this post

No I also tried on a new computer. There is a problem with the wallet that's why I ask a way to recover the private keys, at least to verify all is ok.

try something else...

have you backup the problematic wallet and restored it again?...If not do it and then try to sent again with memo...If yes:
backup your problematic wallet and restore it on a new machine or at least on a different browser , and try again...

So, I created a new account : ok

I sent a few BTS to this new account from my problematic wallet :
this wallet has two accounts,
one from 0.9 migration : transfert to new account ok
one created at 2.0 launch : transfert to new account "Failed to broadcast the transaction"

The new account is able to send to poloniex with BTS received from 0.9 migration.
and poloniex received BTS from new created account.

To sum up :
My wallet with 2 accounts is unable to send BTS with memo for the two accounts and unable to send with or without memo for the account created at 2.0 launch.

Quote from: brads on October 15, 2015, 05:26:47 PM
Yes, as soon as I will be able to create a new account because LightWallet refuse it (failed to create account : unknown error) and https://bitshares.openledger.info/ Bad Gateway 502.

have same problem with gateway   >:(

Yes, as soon as I will be able to create a new account because LightWallet refuse it (failed to create account : unknown error) and https://bitshares.openledger.info/ Bad Gateway 502.

Quote from: brads on October 15, 2015, 03:59:50 PM
Ah I understand, this is an intentionnal bug to block dump at poloniex ;D
Well done guys.

I had no problem sending with memo on poloniex

Can you open a new account on a different browser 
then sent from your "problematic" account without memo to your new account
then sent with your new account with memo to poloniex (until somebody figure out what the problem is...)

Ah I understand, this is an intentionnal bug to block dump at poloniex ;D
Well done guys.

Same behavior with LightWallet (Windows) : no MEMO transfert seems ok, but with MEMO (I tried FOO) is doesn't work, no message, nothing (but in browser javascript console you can see error message).

Ok it is a memo problem because if I left memo box empty, when I press SEND button I have a box showing me details with fees.

When I try to create a new account (to test transfert to it) :

Failed to broadcast the transaction

Indeed poloniex memo is an hex value. I tried copy/paste then by entering characters one by one, same result.

Quote from: testz on October 15, 2015, 03:27:19 PM

Quote from: brads on October 15, 2015, 03:24:43 PM
I tried everything you asked, lock, send, unlock before send...

Error: Missing private memo key for sender: 1.2.xxxxx

g</<.value/<@https://bitshares.openledger.info/graphene_ui/app.js:51:10699
z/</l@https://bitshares.openledger.info/graphene_ui/app.js:2:153
z/<@https://bitshares.openledger.info/graphene_ui/app.js:2:288
d@https://bitshares.openledger.info/graphene_ui/app.js:2:2704

Just an idea, check if you have memo without space at beginning and end. As I remember Poloniex memo usually looks like hex number 0d67e56a9

brilliant, nice idea

Quote from: brads on October 15, 2015, 03:24:43 PM
I tried everything you asked, lock, send, unlock before send...

Error: Missing private memo key for sender: 1.2.xxxxx

g</<.value/<@https://bitshares.openledger.info/graphene_ui/app.js:51:10699
z/</l@https://bitshares.openledger.info/graphene_ui/app.js:2:153
z/<@https://bitshares.openledger.info/graphene_ui/app.js:2:288
d@https://bitshares.openledger.info/graphene_ui/app.js:2:2704

Just an idea, check if you have memo without space at beginning and end. As I remember Poloniex memo usually looks like hex number 0d67e56a9

I tried everything you asked, lock, send, unlock before send...

Error: Missing private memo key for sender: 1.2.xxxxx

g</<.value/<@https://bitshares.openledger.info/graphene_ui/app.js:51:10699
z/</l@https://bitshares.openledger.info/graphene_ui/app.js:2:153
z/<@https://bitshares.openledger.info/graphene_ui/app.js:2:288
d@https://bitshares.openledger.info/graphene_ui/app.js:2:2704