![]() ![]() Wallpaper with blurred or averaged background for X11 902 Next › Last »Ī simple calendar application with reminders for XfceĪ semi-automatic merge tool for pacnew files. Also, donations are recommended for using remote nodes, hence it is not a good idea to rely on them all the time for free.« First ‹ Previous 1 . Everybody suggests that the best is if you have a local node. The conclusion is that you can try to synchronize remotely while you are waiting for your local node to be build up. Please make sure daemon is running or restart the wallet with the correct daemon address. Daemon either is not started or wrong port was passed. If you do not connect the server, you will have this for example:Įrror: wallet failed to connect to daemon:. This is the case when you do not have coins If you have coins, you will not have only zeros but some positive numbers as well. ![]() When the refresh is done, the block counter will disappear and you will see something like this:īalance: 0.00000000000, unlocked balance: 0.000000000000 Now, you have to put the name of the wallet, the password and if the client connects to the remote node you will see (after a while) a message that you are synchronizing: You can find other options here (by the way, read the whole page, it is full of helpful information) ,where the ADDRESS.OF.HOST:18089 option could be for example: monero-wallet-cli -daemon-address ADDRESS.OF.HOST:18089 You can open the client using this option by typing: So, if you are in my situation, when time is very precious you can go around with this issue! You can leave the daemon synching and open the client with the option of using a remote node which will reduce the time of synchronization to about 20-30 minutes in my case. This is what you have to wait until the last block is synchronized! In my case it takes very long time, 2 days and still not done as you see (16GB RAM, Intel i5, but slow and not very stable internet). After the yellow lines you will start seeing lines like those: There will be some green lines with information about ERRORs, INFOs and WARNINGs, then some yellow lines where you will be informed that the synchronization process will start. The option I had chosen was the console version of the wallet.įirst thing you should do is to start the daemon by going to the directory of the XMR wallet (using the Terminal) by typing: So, if you want to buy Monero (XMR) you need a wallet in order to obtain an XMR address. ![]() I would like to say few words to other newbies (Linux users) that may face my situation. Yes, the case is closed, everything is fine at the end! monero-wallet-cli -daemon-address :8880, do I need to wait for this? Can I expect my funds at my address, since my address was generated by the client when the daemon wasn’t properly connected? So I will need 20 hours with the same speed in order to reach 1269875 but until then the Bitsquare operation will be timed out. So the current situation is, I got Synced 57000/1269875 for 1h:10min of running. Then, I paid attention on a message that says, “… make sure you have started the daemon …”! So I started the daemon and realized that the simplewallet is not that simple. Thus, I started waiting for the coins to be received by repeating the refresh and the balance command until I realized that there is something wrong. Thus, I have used the generated XMR address for the Bitsquare buying operation. Unfortunately, I didn’t know that I have to run the daemon beforehand, hence, about the time consuming synchronization routine too. I opened the client, set a wallet and generated an address. So far, I downloaded the simplewallet and both the daemon and the client are the latest version. However, now I have to confirm a XMR payment from a seller on Bitsquare and I need a bit of help from someone more experienced, I got 14hours left I am new to Monero, didn’t know that setting up a wallet and receiving XMR will be more involving than DASH for example and I am learning on the fly. ![]()
0 Comments
Leave a Reply. |