Can't get dash from paper wallet into Jaxx
- Thread starter surgeo
- Start date
- Status
Hi Surgeo.
Not yet redeemed is a good thing. Like a coupon, or a ticket you haven't used. You haven't redeemed it. That means you haven't spent it.
You used paper.dash.org. Did you encrypt it with a passphrase? 'cuz I bet you did!
You need to just convert the encrypted wif to an unprotected wif.
I'll edit this post with details shortly.
Not yet redeemed is a good thing. Like a coupon, or a ticket you haven't used. You haven't redeemed it. That means you haven't spent it.
You used paper.dash.org. Did you encrypt it with a passphrase? 'cuz I bet you did!
You need to just convert the encrypted wif to an unprotected wif.
I'll edit this post with details shortly.
Try the compressed version. Jaxx may be finicky. This test will at least prove your key is valid.
This url is safe, I vouch for it:
open https://walletgenerator.net/?currency=Dash click skip under the progress bar on the right
click 'wallet details' tab
paste your wif in and punch 'view details'
scroll down to the Private Key WIF section
copy the Private Key WIF Compressed WIF
It'll start with X
see if jaxx accepts that. It won't get you your coin, but it'll prove jaxx just doesn't support uncompressed wifs.
This url is safe, I vouch for it:
open https://walletgenerator.net/?currency=Dash click skip under the progress bar on the right
click 'wallet details' tab
paste your wif in and punch 'view details'
scroll down to the Private Key WIF section
copy the Private Key WIF Compressed WIF
It'll start with X
see if jaxx accepts that. It won't get you your coin, but it'll prove jaxx just doesn't support uncompressed wifs.
If the walletgenerator webpage happily processed your wif and showed you a page with that wif appearing on the left side, the problem is with jaxx.
I suggest you import that wif into another wallet for the sole purpose of moving the funds into jaxx.
And, you're welcome.
Sorry you're having jaxx issues, but rest assured your dash are safely where you left them.
I suggest you import that wif into another wallet for the sole purpose of moving the funds into jaxx.
And, you're welcome.
Sorry you're having jaxx issues, but rest assured your dash are safely where you left them.
Is it ok to use the android app 'dash wallet'? play.google.com/store/apps/details?id=hashengineering.darkcoin.wallet
I don't care which wallet I use for the purpose of getting my dash to an online exchange as long as it is reasonably secure.
Also is it best to scan the Q code (left side - WIF) or use 'Private Key Hexadecimal Format' OR 'Private Key Base64'?
I don't care which wallet I use for the purpose of getting my dash to an online exchange as long as it is reasonably secure.
Also is it best to scan the Q code (left side - WIF) or use 'Private Key Hexadecimal Format' OR 'Private Key Base64'?
Sure, that wallet is fine to use.
Doesn't matter, they're the same number.
Super happy thanks so much for the help mc! Just got my dash into dashwallet 
was so worried I would never see it again
was so worried I would never see it again 
You could of also tried CoinomiSuper happy thanks so much for the help mc! Just got my dash into dashwallet
i have some problem how can i withdraw my dash paper wallet to jaxx or other online wallet who accept paper wallet i need btc now instantly can someone guide me
You can try Electrum-Dash to import paper wallet private key https://electrum.dash.org/
PS. "btc" and "instantly" in one sentence looks... like a nonsense
until the recent JAXX recent "Liberty" new version, I think all previous JAXX versions output invalid DASH keys, (i.e. not complying with any of the 5 valid DASH priv key formats. So you can't use older priv keys or paper wallets to recover your dash coins. if you lost your jaxx phrases, like I stupidly did, but carefully did retain your jaxx-exported priv keys, you're f'ed. Priv keys do NOT round trip in JAXX, until the new July Liberty beta version. Quite negligent sw development in their export. BTW - BTC priv exported from JAXX priv key DID work for recovery in other wallet (Exodus), so it's def a bad formatted, non-compliant DASH format they exported. 4 other coins were badly exported from JAXX as well. Shame on programmer and QA engr (or no QA was done) who worked on JAXX export function.
I installed version 1.3.7, one of the oldest github releases, and didn't find anything to suggest anybody's f'ed as you say. You may not be able to import those keys into jaxx, but they're the exception. Those keys work everywhere else.
There are 4 coins with Jaxx-buggy-exported-privkey-formats that I've tested/lost funds on - but let's focus on DASH as the illegal export priv-key formatting is so obvious and I've analyzed that behavior the most. Multiple wallets such as Exodus complain that import of the jaxx-exported key is invalid.
I've duplicated the export-priv-key bug in both older and quite recent JAXX pre-Liberty version (been trying every release since a year) with bug showing consistently, AND verified that new Liberty beta version indeed FIXED the DASH-priv-key-export-illegal-formatting bug. It doesn't get much clearer than that, buggy/illegal DASH-format... then export-bug-fixed. Unfortunately, Liberty lacks the paper-wallet-transfer feature so i can't try recovering my DASH that way, and Liberty would have to honor an illegal legacy-exported DASH priv-key format to boot.
I welcome any help in recovering my DASH via somehow algorithmically translating the illegal-formatted-by-JAXX priv-key I got out of Jaxx export, into a legal DASH format (any of the 5 legit DASH formats).
All pre-Liberty JAXX versions AFAIK export DASH priv key with two glaring mistakes. (1st evidence) no leading 'X' char, just illegal L or K leading chars were exported from JAXX, (2nd evidence) not 52 chars -- both are illegal in DASH priv-keys!
DASH valid priv key formats are listed below: JAXX exported DASH keys are non-compliant with any of the 5 formats (until Jaxx Liberty beta)
(vs only 52 char keys exported by JAXX, and invalid leading chars 'L' or 'K' )
• private Key WIF 51 characters base58, starts with a '7' <<< NOT 52 chars!, not 'L' or 'K'
• Private Key WIF Compressed 52 characters base58, starts with a 'X' <<< NOT 52 chars!, not 'L' or 'K'
• Private Key Hexadecimal Format (64 characters [0-9A-F]): <<< NOT the 52 chars that JAXX exported! not 'L' or 'K'
• Private Key Base64 (44 characters): <<< NOT the 52 chars that JAXX exported!
BTW - I've also verified that jaxx exported illegal format DASH keys in several other wallets paper wallet/private key features. Exodus and others. They all return 'invalid format'.
I've duplicated the export-priv-key bug in both older and quite recent JAXX pre-Liberty version (been trying every release since a year) with bug showing consistently, AND verified that new Liberty beta version indeed FIXED the DASH-priv-key-export-illegal-formatting bug. It doesn't get much clearer than that, buggy/illegal DASH-format... then export-bug-fixed. Unfortunately, Liberty lacks the paper-wallet-transfer feature so i can't try recovering my DASH that way, and Liberty would have to honor an illegal legacy-exported DASH priv-key format to boot.
I welcome any help in recovering my DASH via somehow algorithmically translating the illegal-formatted-by-JAXX priv-key I got out of Jaxx export, into a legal DASH format (any of the 5 legit DASH formats).
All pre-Liberty JAXX versions AFAIK export DASH priv key with two glaring mistakes. (1st evidence) no leading 'X' char, just illegal L or K leading chars were exported from JAXX, (2nd evidence) not 52 chars -- both are illegal in DASH priv-keys!
DASH valid priv key formats are listed below: JAXX exported DASH keys are non-compliant with any of the 5 formats (until Jaxx Liberty beta)
(vs only 52 char keys exported by JAXX, and invalid leading chars 'L' or 'K' )
• private Key WIF 51 characters base58, starts with a '7' <<< NOT 52 chars!, not 'L' or 'K'
• Private Key WIF Compressed 52 characters base58, starts with a 'X' <<< NOT 52 chars!, not 'L' or 'K'
• Private Key Hexadecimal Format (64 characters [0-9A-F]): <<< NOT the 52 chars that JAXX exported! not 'L' or 'K'
• Private Key Base64 (44 characters): <<< NOT the 52 chars that JAXX exported!
BTW - I've also verified that jaxx exported illegal format DASH keys in several other wallets paper wallet/private key features. Exodus and others. They all return 'invalid format'.
Last edited:
Putting text in bold doesn't make it truer.
I see a lot of claims and zero data to back it up.
Provide real data or I can't do anything for you.
I see a lot of claims and zero data to back it up.
Provide real data or I can't do anything for you.
I'm confused. what do you need to be considered real data? screen shots? publicly post here the private keys exported by Jaxx and Jaxx liberty to prove the differences I cite? other evidence? I thought I was pretty specific about the 2 very discrete differences between Jaxx exported private keys, and the 5 legal DASH formats listed on dash.org. Please advise how to supply what you consider real data. I'll gladly give a reward for solving my DASH recovery problem.
Last edited:
I thought I'd give this a try as well. I was unable to replicate your reported bug in both an older version of Jaxx (1.3.3), the latest version of Jaxx (1.3.18) and in Jaxx Liberty (2.0.1.0). All versions returned private keys in the standard 52-character compressed WIF format, starting with X. I was able to send balance, import the privkeys in Dash Core and see the balance imported with no issues at all.
I think what moocowmoo is asking here is to help us understand how you are exporting keys that start with L or K. A partially blurred screenshot and/or a specific version number and platform would be very helpful for us to try and replicate your problem. Until you do so, we have to assume user error or a corrupt Jaxx installation is also a possible explanation for this. Are you sure you aren't looking at the keys for another coin? I'm happy to have a look at the keys for you in PM - several users here can attest to me having helped them in the past with wallet recovery.
I think what moocowmoo is asking here is to help us understand how you are exporting keys that start with L or K. A partially blurred screenshot and/or a specific version number and platform would be very helpful for us to try and replicate your problem. Until you do so, we have to assume user error or a corrupt Jaxx installation is also a possible explanation for this. Are you sure you aren't looking at the keys for another coin? I'm happy to have a look at the keys for you in PM - several users here can attest to me having helped them in the past with wallet recovery.
Strophy - Your guidance on next steps on my end is super clear. Now I understand how to proceed to give the type of data needed. Thanks!
My limitation is lack of access to the 2017 Chrome Jaxx version that I believe exported my saved off non-Dash-compliant priv keys. Jaxx did an automatic upgrade back then (without asking permission or asking if new backup desired first, which would have been a nice SW coding practice at upgrade time). It just did the upgrade and instantly un-paired all my coins. Jaxx had been super reliable for about a year of constant use before then.
I was able to use my 2017-exported priv keys saved off, to recover my BTC (yay) only, but not DASH or 4 other coins :-( The BTC recovery success makes me think I indeed saved off faithfully the jaxx-exported keys for the 5 other coins I had in Jaxx.
So, I'm pretty sure I saved off accurately the 2017 private keys from Jaxx. Had 6 coins in 2017 at auto-un-pair time, and have 6 sets of keys saved off back then - never want to have single point of failure for backups. (so back then I copy-pasted keys into an encrypted doc stored offline with paper backup, back in 2017) i.e. That backup is where I get the offending leading L//K char'ed 52-char Dash private keys. (want to shoot myself for somehow losing my jaxx backup phrases, me = idiot). I'm normally meticulous, but blew the phrases save somehow.
My results today:
Current version non-Liberty/regular Chrome Jaxx. Created new wallet. Dash wallet initialized but empty.
- Exports legal Dash private key format. from a zero value Dash wallet.
(haven't tried putting a small value of Dash there and then exporting keys).
- Regular Jaxx refuses to import my 2017-Jaxx-exported Dash priv key, seems
to test its not a valid key format so no NEXT button shows up.
Liberty Jaxx beta: new wallet, Dash wallet initialized but empty.
- also exports DASH-legal-format priv keys.
- Liberty Jaxx lacks the paper-wallet-transfer feature yet in the beta so cannot test importing my 2017 illegal-format Dash key.
per recent Jaxx support suggestion, i also used the https://walletgenerator.net/?currency=Dash# tool to convert my badly-formatted Dash keys into properly formatted private keys - but the converted keys point to zero-value of Dash unfortunately.
As a trusted Dash admin, I'm willing to send you my 2017 priv keys if that has a potential path to success. Or I'd welcome any other next-step suggestion. Glad to send non-trivial amount of Dash for success.
Cheers,
Leigh
My limitation is lack of access to the 2017 Chrome Jaxx version that I believe exported my saved off non-Dash-compliant priv keys. Jaxx did an automatic upgrade back then (without asking permission or asking if new backup desired first, which would have been a nice SW coding practice at upgrade time). It just did the upgrade and instantly un-paired all my coins. Jaxx had been super reliable for about a year of constant use before then.
I was able to use my 2017-exported priv keys saved off, to recover my BTC (yay) only, but not DASH or 4 other coins :-( The BTC recovery success makes me think I indeed saved off faithfully the jaxx-exported keys for the 5 other coins I had in Jaxx.
So, I'm pretty sure I saved off accurately the 2017 private keys from Jaxx. Had 6 coins in 2017 at auto-un-pair time, and have 6 sets of keys saved off back then - never want to have single point of failure for backups. (so back then I copy-pasted keys into an encrypted doc stored offline with paper backup, back in 2017) i.e. That backup is where I get the offending leading L//K char'ed 52-char Dash private keys. (want to shoot myself for somehow losing my jaxx backup phrases, me = idiot). I'm normally meticulous, but blew the phrases save somehow.
My results today:
Current version non-Liberty/regular Chrome Jaxx. Created new wallet. Dash wallet initialized but empty.
- Exports legal Dash private key format. from a zero value Dash wallet.
(haven't tried putting a small value of Dash there and then exporting keys).
- Regular Jaxx refuses to import my 2017-Jaxx-exported Dash priv key, seems
to test its not a valid key format so no NEXT button shows up.
Liberty Jaxx beta: new wallet, Dash wallet initialized but empty.
- also exports DASH-legal-format priv keys.
- Liberty Jaxx lacks the paper-wallet-transfer feature yet in the beta so cannot test importing my 2017 illegal-format Dash key.
per recent Jaxx support suggestion, i also used the https://walletgenerator.net/?currency=Dash# tool to convert my badly-formatted Dash keys into properly formatted private keys - but the converted keys point to zero-value of Dash unfortunately.
As a trusted Dash admin, I'm willing to send you my 2017 priv keys if that has a potential path to success. Or I'd welcome any other next-step suggestion. Glad to send non-trivial amount of Dash for success.
Cheers,
Leigh
My recommendation at this point would be to track down an older copy of the software (a Jaxx extension for Chrome?) that created those keys, and see if it will import the L/K format privkeys. If you install it and disconnect from the internet, you might be able to prevent it from auto-updating again. You should theoretically then be able to use that version of Jaxx to move the balances to a wallet that functions normally. I think your best bet is to contact Jaxx support at this point to try to figure out which Jaxx version might have created those keys.
If you can find the source code for the wallet that generated the invalid keys, it might also be possible to see how they were generated and potentially convert them to a valid key. Sounds like a bit of a stretch though.
If you can find the source code for the wallet that generated the invalid keys, it might also be possible to see how they were generated and potentially convert them to a valid key. Sounds like a bit of a stretch though.
- Status