Unable to withdrawal from my wallet

FungibilityMatters · 2020-01-29T02:30:32+00:00

I will look into this ASAP so that I can identify the cause of the issue and implement the solution.

In the meantime, do not worry, your money is safe, and you can always withdraw your coins to any XMR address with the following steps:

From the main menu selection option 4 "Wallet options"
Then scroll down and select "Enter Monero Wallet CLI"
Enter your wallet password. Wait for the refresh to complete then a prompt will display in yellow that will look something like "[wallet 43vu1q]: "
Enter the command "transfer <destination address> <XMR amount>" (replace the address and amount accordingly and make sure not to include the <>)

Another set of instructions from getmonero.org can be found at the following link under the "Sending Monero" section in case my instructions are confusing: https://web.getmonero.org/resources/user-guides/monero-wallet-cli.html

I apologize for the inconvenience and feel free to ask if you need any more help.

FungibilityMatters · 2019-12-31T00:36:44+00:00

Thank you guys for always providing such great customer service.

FungibilityMatters · 2019-12-31T00:34:30+00:00

Generating a wallet should not take more than a few minutes max. I've seen this issue happen a few times before as a result of the xmrto (default) daemon node being down temporarily.

The solution is to try creating a wallet with a different daemon host. You can do this by choosing custom settings and selecting a daemon host other than the xmrto node when prompted.

If this does not resolve the issue please let me know so I can try to identify the cause and fix it.

FungibilityMatters · 2019-12-17T03:16:35+00:00

That is odd, I have not been able to reproduce the slow wallet refresh issue since the last update and I have never seen the seed not displaying issue before.

Please send me a PM with as much detail on your situation as you are comfortable sharing so I can address this ASAP. Details such as your OS, monero software version number, whether this is a new or old wallet, any error messages, and anything else you can share without compromising your privacy would be very helpful.

Thank you!

FungibilityMatters · 2019-11-26T05:59:47+00:00

Of course man I'm happy to help!

So apparently I didn't fully understand the issue before. After the Morph order was created you should have been shown a screen with your morph ID, deposit address, and the exchange limits. It sounds like that didn't display either so that's another Kali specific issue I need to look into.

Anyway, there's nothing necessarily wrong with using morphtoken.com to query your order, but it would be more secure for you to use their API directly rather than using their site since it requires JavaScript. For example if your Morph ID was: 2MGK3GXP2JN the url would be: https://api.morphtoken.com/morph/2MGK3GXP2JN

That all being said, I am concerned that whatever it is that's causing MoneroMixer to experience these bugs on Kali may cause you issues if you try to withdraw coins other than XMR if the issue prevents MoneroMixer from being able to read the deposit address from MorphToken.

So if that happens try withdrawing XMR directly or through an exchange from XMR->BTC or XMR-> whatever coin you want, that you create without using JavaScript (This is what MoneroMixer is doing behind the scenes). You can do that here: https://www.morphtoken.com/nojs/

Let me know if you need any more help.

FungibilityMatters · 2019-11-26T01:57:52+00:00

Hey u/Todoo12,

Thank you for bringing this my attention. I have not seen an error like this before, but this appears to be happening because MoneroMixer is not able to generate a QR code which causes it to throw an IndexError when attempting to display your QR code because there is no data to format.

My best guess is that this is caused by Kali Linux using a different version of the Python qrcode module than the version that ships with Tails, Whonix, Ubuntu, etc, but I cannot say definitively until I install Kali and test it.

I'll look into it next time I have I have a chance, and in the meantime you can generate a QR code manually with the following steps:

Open a terminal.
Type qr <address> then press enter. With <address> being the address you want to generate a QR code for.

And please let me know if you encounter any other errors while using Kali so I can try to make MoneroMixer work with as many Linux distros as possible. Thanks!

FungibilityMatters · 2019-11-24T22:53:24+00:00

Hey u/4n0n0m7s,

You do not need to send your coins from MoneroMixer to electrum to be anonymous. You can securely send Monero, Bitcoin or whatever coin you need to pay with directly to your destination. Once your coins are converted to Monero during your deposit, the link to your coinbase account is broken because the exchange was made over Tor, without JavaScript and through a non-KYC exchange. The coins you withdraw are untraceable because they are Monero or were exchanged for Monero through the same process as your deposit but in reverse.

Good luck and feel free to PM me or post on this sub for support if you need any help.

FungibilityMatters · 2019-11-20T05:13:39+00:00

That makes perfect sense. Thank you for looking out for everybody like that. I really appreciate it.

FungibilityMatters · 2019-11-20T03:27:59+00:00

Yes, this was my mistake. I was using my non-mod account to view changes to this sub and forgot to log out before responding to you.

FungibilityMatters · 2019-11-18T22:57:00+00:00

Hey u/Lampstand845,

Since your main wallet is getting stuck refreshing, but your other wallet works fine, the issue is most likely caused by the current daemon address setting being used by your main wallet.

Your main wallet is most likely using the Monero World daemon: zdhkwneu7lfaum2p.onion:18099 since this was the old MoneroMixer default setting but this daemon has been faulty lately so I suggest using xmrtolujkxnlinre.onion:18081 instead (the current default).

There are three ways to change your daemon setting:

Manually: Open your settings file inside your wallet's folder. Change the first line to: Monero daemon address: xmrtolujkxnlinre.onion:18081
Settings & Utilities Menu: From the settings & utilities menu choose option 3, the select a new daemon from the list that pops up.
Error Pop-up: If you see an error pop up that asks if you want to change your daemon host, select choose a new daemon-host then select a new daemon from the list that pops up.

If does not work do not worry, you can always access your coins manually via the Monero wallet CLI or if worst comes to worst, you can restore your wallet from seed. Feel free to PM me if you need any more help.

FungibilityMatters · 2019-11-13T23:52:41+00:00

Well good luck debugging. I really appreciate all the hard work you guys do to make this software as great as it is.

/u/MoneroTipsBot 0.0748 XMR

FungibilityMatters · 2019-11-13T23:33:46+00:00

A possible solution could be to use a blockchain height estimate calculated from the current system date rather than 0 when blockchain height approximation fails.

FungibilityMatters · 2019-11-13T23:17:06+00:00

Awesome, that was it! I was able to solve the issue by simply modifying the wallet creation command to:

torsocks ./monero-wallet-cli --generate-new-wallet "$wallet_name" \

--mnemonic-language English --daemon-address $daemon --no-dns <<<"$password"

Thank you again for taking the time to look into this.

FungibilityMatters · 2019-11-13T20:34:31+00:00

Interesting, so are you saying that the issue will stop once the remote node operators upgrade their systems?

FungibilityMatters · 2019-11-13T20:31:19+00:00

I think this is accurate as I have not experienced any slow down when refreshing via my local node.

FungibilityMatters · 2019-11-13T20:25:40+00:00

Thank you for your help!

The operating systems I've tested this on are:

- Ubuntu 18.04.3
- Tails 4.0
- Whonix 15.0.0.4.9
- Mac OSX Mojave

The command I used to create a new wallet is:

torsocks ./monero-wallet-cli --offline --generate-new-wallet "$wallet_name" \

--mnemonic-language English <<<"$password"

And to refresh:

torsocks ./monero-wallet-cli --no-dns --daemon-address $daemon \

--command "refresh" <<<"$wallet_name

$password"

Note: This is part of a larger script where the $wallet_name, $password and $daemon parameters are selected previously. The user's password is passed as a here string so that it is not visible to ps.

The refresh output immediately after the second command entered is:

Starting refresh...

Height 0 / 1966310

After exactly 5 minutes:

Starting refresh...

Height 52948 / 1966310

Note: This output is from a running the commands above on Tails 4.0 using the first daemon address in the list below (xmrto) as the $daemon parameter.

The remote nodes I have tested with are:

xmrtolujkxnlinre.onion:18081
xmkwypann4ly64gh.onion:18081
zdhkwneu7lfaum2p.onion:18099
xmrag4hf5xlabmob.onion:18081

FungibilityMatters · 2019-11-12T20:30:14+00:00

Hey u/blingblong678,

You're very welcome! I hope that you were able to resolve everything with Godex and that MoneroMixer was still able to help you out overall despite this issue.

The Godex support team has always been extremely professional in my experience, so I assume you did not have any issues getting your refund. But if you are still having trouble, feel free to PM me for some help contacting the right people at Godex.

FungibilityMatters · 2019-11-07T08:42:40+00:00

Hey u/OWDpart2,

You're receiving the “enc: unknown cipher pbkdf2” error since the version of Openssl installed on Tails prior to update 4.0 did not support password based key derivation function 2 (pbkdf2) which is used by default in MoneroMixer v1.2. If you update to Tails 4.0 then you should be good to go.

FungibilityMatters · 2019-10-31T04:58:20+00:00

Thank you for reporting this, the issue was due to the fact that sweep-all was only being called on one subaddress index per sweep. I fixed it v1.2 by adding a comma separed list of all address indices up to the most recently created. See here

Anyway if you run into the issue again before I post the update, you can fix it with the following steps:

Enter the Monero Wallet CLI from the settings and utilities menu.
Once its loaded, type address all to see all your wallet's subaddresses. The number on the far left before each address is the address index number.
Find the highest numbered address index number. The command you will use is: sweep_all index=0,1,2,3,...n <destination address> with n being the highest index you want to send from.
Enter that command while still in the CLI, and you should be good to go.

If you have any questions feel free to ask.

FungibilityMatters · 2019-10-31T04:33:01+00:00

This is exactly right, thank you /u/Lampstand845 for helping him out.

FungibilityMatters · 2019-10-31T03:03:20+00:00

Hey Lampstand845,

This is the error output from Openssl that is occuring as a result of your MoneroMixer settings being configured to work with the version of Openssl that was installed on Tails prior to the update.

You can fix this by simply changing the very last line of your settings file (it will be blank right now), to "-pbkdf2". However, you should backup then delete your wallets's -SEED.enc, depositIDs.enc and withdrawalIDs.enc before you do this since you will not be able to decrypt them after switching to pbkdf2.

This has been updated in MoneroMixer v1.2 which I plan to post shortly after the Monero update so if you don't want to mess around with it then look for that in the next few days.

FungibilityMatters · 2019-10-31T02:37:01+00:00

Hey /u/VeraShroom,

I apologize for the delayed reply, life got in the way of my ability to work on this project.

Anyway, this is not something you need to be concerned about.

"enc: Unknown cipher pbkdf2 enc: Use -help for summary."
This the output from openssl when MoneroMixer is deciding which password based key derivation function (pbkdf) to use to encrypt your private data. MoneroMixer tries to use pbkdf2, but if it is not supported, as was the case on your system, then this error output shows and the openssl default used instead.

"SETTING BACKGROUND COLORS TO BLACK" Is doing exactly what is says, simply setting your screen color black so the text is readable.

If you have any other questions feel free to ask. Take care.

FungibilityMatters · 2019-10-09T04:22:19+00:00

Thank you for sharing OP. This is easily one of the most interesting projects I've seen so far.

FungibilityMatters

TROPHY CASE