Note that this is a preliminary thread to inform community members about the upcoming scheduled protocol upgrade. This thread will be replaced once the binaries are released.
First and foremost, you should upgrade to v0.13.0.0 once the binaries are released or the tag has been created
The binaries, once they are released, can be found here:
https://getmonero.org/downloads/ // CLI released (ARMv7 & ARMv8 forthcoming), GUI forthcoming
Alternatively, you can use the Github link:
CLI: https://github.com/monero-project/monero/releases/tag/v0.13.0.2 // Released (ARMv7 & ARMv8 forthcoming)
GUI: https://github.com/monero-project/monero-gui/releases/tag/v0.13.0.0 // Forthcoming
Note that this is a scheduled and consensual network upgrade. Thus, unlike the BCH / BTC split, a new coin won't be created.
Approximately the 18th of October there will be a scheduled network upgrade on the Monero network. To be sufficiently prepared, a user, service, merchant, pool operator, or exchange should run CLI v0.13.0.2 or GUI v0.13.0.0. The scheduled network upgrade introduces four major changes. First and foremost, a new form of range proofs called Bulletproofs, which will replace the old Borromean range proofs and thereby significantly (i.e. by approximately 80%) reduce the transaction size (and thus fees). Second, a PoW tweak to curb any potential threat of ASICs and further preserve ASIC resistance. As a result, miners will have to update their miners (i.e. mining software) as well. Third, the minimum ring size is bumped to 11 (mixin 10) and will be static / fixed. Therefore, pool operators need to ensure that payouts use a ring size of 11 (mixin 10), otherwise they will get rejected by the network.
A blog about Monero compatible Bulletproofs can be found here:
More information about the second PoW tweak can be found here:
The blog that set out a formal stance on ASIC resistance and the intention to maintain ASIC resistance can be found here:
In addition, more information about the ring size bump and the decision to make it a static parameter can be found here. Lastly, all changes have been discussed extensively in the last few dev meetings, which can be read here:
Due to variance the scheduled network upgrade will take place on or around the 18th of October. There is, however, no specific date as the hard fork will be triggered by a specific blockheight. The specific blockheight for the hard fork can be found here. That is:
// version 8 starts from block 1685555, which is on or around the 18th of October, 2018. Fork time finalised on 2018-09-02.
Note that there technically will be two hard forks (i.e. one on approximately the 18th of October and one on the approximately the 19th of October). This provides a grace period on the network where transactions in the transaction pool that still use the old Borromean range proof are allowed to be included in a block by miners. Fortunately, running v0.13.0.0 ensures that one is sufficiently prepared for both hard forks.
First and foremost, we encourage users to check the integrity of the binaries and verify that they were signed by Fluffypony's GPG key. A guide that walks you through this process can be found here for Windows and here for Linux and Mac OS X.
CLI: // ARMv7 and ARMv8 binaries are forthcoming
If you are using the CLI you ought to perform the following steps:
Extract the new binaries to a new directory of your liking.
Copy over the wallet files from the old directory (the one that contains the v0.12.0.0, v0.12.1.0, v0.12.2.0, or v0.12.3.0 binaries).
monero-wallet-cli (in case you have to use your wallet).
Note that a blockchain resync is not needed. Thus, if you open
monerod-v.0.13.0.2, it will simply pick up where it left off. Note, however, that the daemon (monerod) will have to upgrade the database version to accommodate the changes required for the initial pruning implementation.
GUI: // Forthcoming
If you are using the GUI you ought to perform the following steps:
Extract the new binaries to a new directory of your liking. This is the easiest and recommended way. Alternatively, however, you can overwrite the old binaries.
monero-wallet-gui1. It should automatically load your "old" wallet and you should be set for the upcoming scheduled network upgrade.
(1) On Linux you ought to start the GUI with the
start-gui.sh script, i.e.,
Note that a blockchain resync is not needed, i.e., it will simply pick up where it left off. Note, however, that the daemon (monerod) will have to upgrade the database version to accommodate the changes required for the initial pruning implementation.
You don't have to do anything. However, if you want to restore a wallet after the scheduled network upgrade, you need to use the new binaries.
You don't have to do anything, as MyMonero will be properly upgraded in advance of the scheduled network upgrade.
Its presumed that MyMonero will release a new version of the desktop wallet in advance of the scheduled network upgrade such that the user is sufficiently prepared. Basically, their new version has to use ring size 11 as minimum default, otherwise users will get their transactions rejected.
Its presumed that the third-party mobile wallets (Monerujo, Cake, Xwallet, MyMonero, and Edge wallet) will release a new version in advance of the scheduled network upgrade such that the user is sufficiently prepared. Basically, their new version has to use ring size 11 as minimum default, otherwise users will get their transactions rejected.
This process is similar to the CLI upgrade process. Thus, see aforementioned CLI steps.
Your pool operator should upgrade to the new version. In addition, you should update your mining software to the latest version (the one that includes code to accommodate the second PoW tweak).
It's in our best interest that the upcoming scheduled network upgrade transits as smoothly as possible. Therefore, it is imperative that we, as community, contact economically sensitive nodes (exchanges and services) and inform them about the new version, the upcoming scheduled network upgrade, and that they should run v0.13.0.0 to be sufficiently prepared. A list of exchanges that have integrated Monero can be found here:
In addition, services that have integrated Monero are, for example, XMR.to, Bisq, LocalMonero, and Morphtoken.
Lastly, if you have any questions or need any assistance with upgrading, please leave a comment in this thread and the community and I will help you out.
There are multiple Monero wallets for a wide range of devices at your disposal. Check the table below for details and download links. All wallets listed below are open source. Attention: for extra security make sure to calculate and compare the
checksum of your downloaded files.
|"Official" GUI / CLI||Windows, Mac OS X, Linux||The default implementation that is maintained by the core team. Use this one to run a full node and obtain maximum privacy.Has Ledger (hardware wallet) integration. Current version: 0.12.3.0.||GetMonero.org|
|MyMonero||Windows, Mac OS X, Linux||MyMonero is a lightweight wallet, which means you don't need to download the blockchain and run a node. MyMonero was developed with the assistance of the core team. They also have web-based and iOS versions.||GitHub|
|Monerujo||Android||Popular Android lightweight wallet that has very cool features, like integration with xmr.to which lets you send payments in BTC using your XMR. It also has Ledger (hardware wallet) integration. Website: https://www.monerujo.io/.||Google Play / F-Droid / GitHub|
|MyMonero||iOS||iOS version of the MyMonero wallet. All versions have interoperability.||App Store|
|Cake Wallet||iOS||Popular iOS lightweight wallet that has integration with MorphToken, which means you can instantly exchange your XMR to other coins and tokens. Website: https://cakewallet.io/||App Store|
|X Wallet||iOS||Another iOS lightweight wallet. Website: https://xwallet.tech/||App Store|
|Edge Wallet||Android / iOS||This is a multi-assets wallet, meaning you can store Monero, Bitcoin, Ethereum and other tokens in one single app. https://edge.app/ ⚠️ Relatively new - use with caution! ⚠️||Google Play / App Store|
|MyMonero||Web version of the MyMonero wallet. All versions have interoperability.||Web|
|XMRWallet||Web wallet with TOR support. ⚠️ Relatively new - use with caution! ⚠️||Web / Onion URL|
Your balance is unlocked after 10 confirmations (which means 10 mined blocks). A block is mined approximately every two minutes on the Monero network, so that would be around 20 minutes.
There are dozens of exchanges that trade Monero against Bitcoin and other cryptocurrencies. Check out the list on CoinMarketCap and choose the option that suits you best.
The correct place to ask questions and discuss the Monero mining scene is in the dedicated subreddit r/MoneroMining. That being said, you can find a list of pools and available mining software in the GetMonero.org website.
Before any action there are two things to check:
Because Monero is different from Bitcoin, wallet synchronization is not instant. The software needs to synchronize the blockchain and use your private keys to identify your transactions. Check in the lower left corner (GUI) if the wallet is synchronized.
You can't send transactions and your balance might be wrong or unavailable if the wallet is not synced with the network. So please wait.
If this is not a sufficient answer for your case and you're looking for more information, please see this answer on StackExchange.
This answer is beautifully answered on StackExchange.
You have decided to use Monero's wallet and run a local node. Congratulations! You have chosen the safest and most secure option for your privacy, but unfortunately this has an initial cost. The first reason for the slowness is that you will need to download the entire blockchain, which is considerably heavy (+60 GB) and constantly growing. There are technologies being implemented in Monero to slow this growth, however it is inevitable to make this initial download to run a full node. Consider syncing to a device that has an SSD instead of an HDD, as this greatly impacts the speed of synchronization.
Now that the blockchain is on your computer, the next time you run the wallet you only need to download new blocks, which should take seconds or minutes (depending on how often you use the wallet).
Be advised that when using a public remote node you lose some of your privacy. A public remote node is able to identify your IP and opens up a range for certain attacks that further diminish your privacy. A remote node can't see your balance and it can't spend your XMR.
To restore your wallet with the 25 word mnemonic seed, please see this guide.
To restore your wallet with your keys, please see this guide.
If you want to support other Monero users by making your node public, you can follow the instructions on MoneroWorld, under the section "How To Include Your Node On Moneroworld".
This answer is beautifully answered on StackExchange.
Running a node is easy - but only if you know how. You will soon...
Nodes store a copy of the Monero blockchain and share it with each other. No nodes = no Monero. And we don't want that.
A Monero wallet app (like Monerujo, but also the official GUI & CLI) needs to connect to a node to talk with the Monero network. So running your own node also increases your level of privacy and security since no one else will know you are using your wallet.
This guide will show you how to run one on Ubuntu 18.04.
Just get one from a VPS provider like
or hetzner - let a friend help you! The
only real constraint is the space needed for the blockchain.
At the time of writing the blockchain database is around 65GB. So you
should be aiming for a VPS with 100GB storage. Other VPS parameters are
not critical (1CPU, 1GB RAM is fine). Setup your user to be a
sudoer and don't call it
monero as we will be setting that
up specifically for running the node.
You probably want to give your new VPS a hostname by registering it with your DNS provider. If you don't have one, you can add your host to a billion domains at afraid.org, including moneroworld.com!
Make sure you are connecting through
ssh. You should disable
password logins for root (and probably all users) and only use an ssh key
(this is beyond the scope here - ask your friend how to do this).
Most setups don't have a firewall enabled. Firewalls are a good idea in general.
Enable SSH traffic in so you don't kick yourself out:
sudo ufw allow ssh
And then enable the firewall with
sudo ufw enable
You can check the status with
sudo ufw status
The node software for monero is called
monerod - the monero
deamon. It is part of the official Monero distribution which can be
downloaded from the
Monero Downloads page.
We will be working with the Linux, 64-bit Command-Line Tools Only
Note that you may need the *ARMv8** package if the VPS you selected is an ARMv8 model.*
wget -O monero.tar.bz2 https://downloads.getmonero.org/cli/linux64 sha256sum monero.tar.bz2
This will give you the checksum of the download, which you can use to verify authenticity by comparing the result to the SHA256 Hash (CLI) on the Monero Downloads page.
tar xfj monero.tar.bz2 ls -l
This shows the folder which was unpacked containing the monero
applications - at the time of writing we see
Copy the files in there to their final destination:
sudo cp monero-v0.13.0.2/* /usr/local/bin
rm monero.tar.bz2 rm -r monero-v0.13.0.2
Now we create the configuration for the monero daemon service.
sudo nano /etc/monerod.conf
Paste this in there:
data-dir=/var/lib/monero log-file=/var/log/monero/monero.log log-level=0 no-igd=true rpc-bind-ip=0.0.0.0 rpc-bind-port=18081 restricted-rpc=true confirm-external-bind=true
Save it with
^O and exit with
This basically tells the
monerod where to store it's data (in
/var/lib/monero) and that it should only accept safe commands so
you can expose your node to the internet without worrying that people
will be mining with your node!
Now we create the service definition for the monero daemon service.
sudo nano /lib/systemd/system/monerod.service
Paste this in there & save & exit as before.
[Unit] Description=Monero Full Node After=network.target [Service] User=monero Group=monero WorkingDirectory=~ RuntimeDirectory=monero Type=forking PIDFile=/run/monero/monerod.pid ExecStart=/usr/local/bin/monerod --config-file /etc/monerod.conf \ --detach --pidfile /run/monero/monerod.pid Restart=always [Install] WantedBy=multi-user.target
Create a new user
monero for running the service. This is overall
safer than running the service under you working user. You can call
this user whatever you want, but you would need to change some of the
commands & configs in this guide to reflect your choice.
sudo adduser --system --group monero
Create some folders the service needs & set their ownership:
# logfile goes here sudo mkdir /var/log/monero sudo chown monero.monero /var/log/monero # blockchain database goes here sudo mkdir /var/lib/monero sudo chown monero.monero /var/lib/monero
As we have a firewall set up, we need to enable incoming connections to the node:
sudo ufw allow 18080 sudo ufw allow 18081
Enable the service:
systemctl enable monerod
And start it!
systemctl start monerod
If you get errors here - you're doomed! Start off by running
sudo -H -u monero /usr/local/bin/monerod --config-file /etc/monerod.conf --pidfile /run/monero/monerod.pid
which runs the
monerod as the service would and see what errors
You can watch the daemon doing it's thing by looking at the log:
tail -f /var/log/monero/monero.log
You can stop this at any time with
Ok, here comes the frustrating part: waiting to sync. Watch the log until it says
********************************************************************** You are now synchronized with the network. You may now start monero-wallet-cli. Use the "help" command to see the list of available commands. **********************************************************************
This may take a few days - you will see progress in the logs though.
Fire up your trusted Monerujo (or other client) and enter your IP or hostname in the "Node" field. Open a wallet and enjoy.
Or change the port of the daemon service to
18089 so that it is automatically included in the
node.moneroworld.com node pool by changing
and restarting the service:
systemctl restart monerod
Again, we need to allow this in the firewall:
sudo ufw allow 18089
And delete the old rule:
sudo ufw delete allow 18081
If you do this, you will need to add
:18089 to the hostname when
connecting to it (e.g.
As the Monero code is ever evolving, you will need to keep it up to date. When there is a new version available, you will need to stop the service:
systemctl stop monerod
Then download & deploy as we did above, and then restart the service:
systemctl start monerod
There are a bunch of other options you can include in the
/etc/monerod.conf configuration file. Running
monerod --help will list all command-line options -
these can be included (one per line) in the configuration file as well!
You may, for example, want to limit the upload speed in case you have a
limit-rate-up=8192 (in kB/s).
After more than ten months of being available to the public at no cost, the X Wallet will now be a paid app. Why this change?
We’re continuously adding new features, such as multi-factor authentication, in order to improve the security and performance of your X Wallet, without ever sacrificing your financial privacy and sovereignty. We think that these improvements are definitely worth building, maintaining, and paying for. We hope you do too!
You can download the fresh new version of the X Wallet here: https://itunes.apple.com/us/app/x-wallet-monero-wallet/id1335168711?ls=1&mt=8
In case one runs a monero node for solo mining: is it necesary to open port 18080 for solo-mining? Is opening the port absolutely required? Why does a monero node have incomming connections?
Thanks for your clarification!
So I heard a funny joke today, and the punch line is the title of this post.
Now, I'm gonna tell the information so you can understand why it is such a funny joke.
Sidechains have to be secured via mining: there is very little incentive to do so because the fees will be near zero. Sidechains cannot have a block reward so they need to be based on the transaction fees of the sidechain. Transaction fees are dictated via blockspace scarcity & demand. Since you can trivially copy and create another sidechain with the same technical capabilities, there is no ability to demand high fees in a sidechain, or it has some equilibrium which is extremely low. Miners won't mine every single sidechain to pop into existence for this minsecule payment and may now have incentives to attack other sidechains. (sidechains compete with on chain transactions, which actually do create value for the miners)
Sidechains require you trust the parties of those who created the sidechain not to steal ALL the coins. They work via multisig addresses and someone has to have those. Imagine how people reject zcash for their trusted setup. This is a million times worse. https://mobile.twitter.com/peterktodd/status/1051636666899845120
Any flaws monero has with a risk of undetectable inflation is still present on the side chain. Sure a Monero implementation in a sidechain can't damage the main chain, but it can affect the main chain by altering perceived supply and demand, plus it can completely ruin it for everyone who was holding/using coins on the sidechain. This could be significant if the sidechain was popular because it had a high utility.
The combined consequence of all these issues means you won't want to hold your coins on a sidechain. There is much higher risk of everything from 51% attack, theft, and flaws then in a main chain. This will result in sidechains being less valuable, where 1 BTC does not equal 1 BTC on a sidechain... Making bitcoin LESS fungible then ever before.
A bonus feature is since sidechains can't persist forever, or you wouldn't want them too as the risk of having the trusted parties having their keys lost or compromised, or dying increases. So the anonymity set will never be as large as Monero.
So yeah. Next time you hear someone say this, hold your side and laugh because it's a joke. A mighty funny joke.
Edit: But actually, am I wrong in this? Can sidechains be deployed in a trustless manner? Did I get anything else incorrect, or mislead?
I'd be keen to hear the skeptical thoughts and counter-arguments of side-chain proponents in this thread.
Building on Debian 9.
Monero builds successfully with hardware support:
$ ldd build/Linux/_HEAD_detached_at_v0.13.0.2_/release/bin/monerod|grep hid
libhidapi-libusb.so.0 => /usr/lib/x86_64-linux-gnu/libhidapi-libusb.so.0
Monero-gui finds hidapi but fails to link.
-- Found HIDAPI: /usr/lib/x86_64-linux-gnu/libhidapi-libusb.so
-- Using HIDAPI include dir at /usr/include/hidapi
g++ -m64 -fstack-protector -fstack-protector-strong -pie -Wl,-z,relro -Wl,-z,now -Wl,-z,noexecstack -Wl,-O1 -o release/bin/monero-wallet-gui main.o filter.o clipboardAdapter.o oscursor.o WalletManager.o Wallet.o PendingTransaction.o TransactionHistory.o TransactionInfo.o QRCodeImageProvider.o oshelper.o TranslationManager.o TransactionHistoryModel.o TransactionHistorySortFilterModel.o BitBuffer.o QrCode.o QrSegment.o AddressBookModel.o AddressBook.o SubaddressModel.o Subaddress.o zxcvbn.o UnsignedTransaction.o Logger.o MainApp.o DaemonManager.o qrc_translations.o qrc_qml.o moc_filter.o moc_clipboardAdapter.o moc_oscursor.o moc_WalletManager.o moc_Wallet.o moc_PendingTransaction.o moc_TransactionHistory.o moc_TransactionInfo.o moc_Transfer.o moc_NetworkType.o moc_oshelper.o moc_TranslationManager.o moc_TransactionHistoryModel.o moc_TransactionHistorySortFilterModel.o moc_AddressBookModel.o moc_AddressBook.o moc_SubaddressModel.o moc_Subaddress.o moc_UnsignedTransaction.o moc_MainApp.o moc_DaemonManager.o -L/usr/X11R6/lib64 -L/home/user/xm/monero-gui/monero/lib -lwallet_merged -lepee -lunbound -leasylogging -ldl -lboost_serialization -lboost_thread -lboost_system -lboost_date_time -lboost_filesystem -lboost_regex -lboost_chrono -lboost_program_options -lssl -llmdb -lsodium -lcrypto -Wl,-Bdynamic -Wl,-Bdynamic -lunwind -lQt5Quick -lQt5Widgets -lQt5Gui -lQt5Qml -lQt5Network -lQt5Core -lGL -lpthread
/home/user/xm/monero-gui/monero/lib/libwallet_merged.a(device_io_hid.cpp.o): In function \hw::io::device_io_hid::disconnect() [clone .localalias.298]':`
device_io_hid.cpp:(.text+0x2e): undefined reference to \hid_close'`
/home/user/xm/monero-gui/monero/lib/libwallet_merged.a(device_io_hid.cpp.o): In function \hw::io::safehid_error(hid_device*)':`
device_io_hid.cpp:(.text+0x2ce): undefined reference to \hid_error'`
/home/user/xm/monero-gui/monero/lib/libwallet_merged.a(device_io_hid.cpp.o): In function \hw::io::device_io_hid::init()':`
device_io_hid.cpp:(.text+0xa2a): undefined reference to \hid_init'`
/home/user/xm/monero-gui/monero/lib/libwallet_merged.a(device_io_hid.cpp.o): In function \hw::io::device_io_hid::connect(unsigned int, unsigned int, unsigned int, unsigned int, bool)':`
device_io_hid.cpp:(.text+0x1a20): undefined reference to \hid_close'`
device_io_hid.cpp:(.text+0x1a4a): undefined reference to \hid_enumerate'`
device_io_hid.cpp:(.text+0x1dbc): undefined reference to \hid_free_enumeration'`
device_io_hid.cpp:(.text+0x2c30): undefined reference to \hid_open_path'`
device_io_hid.cpp:(.text+0x2c40): undefined reference to \hid_free_enumeration'`
/home/user/xm/monero-gui/monero/lib/libwallet_merged.a(device_io_hid.cpp.o): In function \hw::io::device_io_hid::exchange(unsigned char, unsigned int, unsigned char, unsigned int)':`
device_io_hid.cpp:(.text+0x7599): undefined reference to \hid_write'`
device_io_hid.cpp:(.text+0x7e2e): undefined reference to \hid_read_timeout'`
device_io_hid.cpp:(.text+0x7e7c): undefined reference to \hid_read_timeout'`
collect2: error: ld returned 1 exit status
Makefile:278: recipe for target 'release/bin/monero-wallet-gui' failed
make: *** [release/bin/monero-wallet-gui] Error 1
Retry without hardware support by
apt-get remove libhidapi-dev will build and function but cannot connect to hardware wallets.
Given the success of the previous MAAMs (see here), let's keep this rolling.
The principle is simple: ask anything you'd like to know about Monero, especially the dumb questions that you've been keeping for you every other days, may the community clarify it all!
Finally, credits to binaryFate for starting the concept!
Monerujo v1.8.4 "Bullets And Octane-Pirates" has been released.
It will not work with v7 nodes. You need to upgrade your node (or use one which is upgraded). Please check out this reddit thread if you don't have one or would like to share yours to help others until all nodes are upgraded.
If you like what I'm doing, support me through the Monero FFS (OpenAlias: ffs.monerujo.io).
Anyone who has not yet done so - WRITE DOWN YOUR SEED (because it's the right thing to do)!
Listen to the soundtrack of this release!
Major changes since the last production version (v1.7.3):
Get support on the /r/Monerujo.
Shout outs to all contributors & supporters!!
Also, check out our fantastic (nearly) content-free website at monerujo.io! Beware of the "Team" page - it's the worst page in all the internet!
Donations: 4AdkPJoxn7JCvAby9szgnt93MSEwdnxdhaASxbTBm6x5dCwmsDep2UYN4FhStDn5i11nsJbpU7oj59ahg8gXb1Mg3viqCuk (OpenAlias: monerujo.io)
I sent some of my Monero to ohters and I found some interesting observation.
Some group has recent-only ring members but many of others has various distribution which has some from recent days and others from past.
I wonder how Monero selects their ring members. I googled it and I got some helpful article about it, but in upper-link, there are just recent outputs. Does it follows preferences?
Please stay on topic: this post is only for comments discussing the uncertainties, shortcomings, and concerns some may have about Monero.
NOT the positive aspects of it.
Discussion can relate to the technology itself or economics.
Talk about community and price is not wanted, but some discussion about it maybe allowed if it relates well.
Be as respectful and nice as possible. This discussion has potential to be more emotionally charged as it may bring up issues that are extremely upsetting: many people are not only financially but emotionally invested in the ideas and tools around Monero.
It's better to keep it calm then to stir the pot, so don't talk down to people, insult them for spelling/grammar, personal insults, etc. This should only be calm rational discussion about the technical and economic aspects of Monero.
"Do unto others 20% better than you'd expect them to do unto you to correct subjective error." - Linus Pauling
How it works:
Post your concerns about Monero in reply to this main post.
If you can address these concerns, or add further details to them - reply to that comment. This will make it easily sortable
Upvote the comments that are the most valid criticisms of it that have few or no real honest solutions/answers to them.
The comment that mentions the biggest problems of Monero should have the most karma.
As a community, as developers, we need to know about them. Even if they make us feel bad, we got to upvote them.
To learn more about the idea behind Monero Skepticism Sunday, check out the first post about it:
That being said, I'm looking forward to the day when I can no longer do it because of my laptop no longer being able to handle the traffic. That would mean Monero is a success and is actually being used by people. With bulletproofs, there's lots of room for growth.
Blockchain bloat, bring it on.
Hi there !
I downloaded the latest version of GUI and CLI Monero client
GUI Current Version: 0.12.3.0 Beryllium Bullet
CLI Current Version: 0.13.0.2 Beryllium Bullet
Perfectly complete the installation following installation process for Mac
But when I run Monero GUI, I can see in background the following message : "Wallet is not connected to daemon", knowing that in the procedure it is written "Step 12 - You may, after the CLI has generated your wallet, get an error about the wallet not being connected to the daemon. You can ignore that for now."
>>Is there any link between the message I got and the message in background when I'm tryng to connect?
As it doesn't stop me from going further, I select the .keys file and type my password but I get the message "
Couldn't open wallet: Fail SCard API : (-2146435069) Invalid handle. Device=0, hCard=0, hContext=1"
>>I tried during hours to find the discussion that provides a simple solution to that but I can't find it. Is there any problem between the version of GUI anc CLI. Can anybody help the novice I am?