and to load the config properties do you have to always have the option -conf=
and the peers.dat file holds the know peers so far. So it checks that and establishes connections right? So the peers list should grow right, making connecting faster eventually? correct me if i am wrong.
Whats a sensible amount of connections to have,because mine is quite low? (more nodes would be appreciated)
Thanks
Once your wallet connects to *one* other wallet, it will request the peer list from that wallet and then try to connect to those peers itself, quickly building a large number of reachable IP addresses with Sync wallets.
If your port configuration does not allow incoming connections, then the number of peers tend to stay around a dozen, connections that your wallet makes *to* others. If you allow incoming connections, you can have many dozens connections from your wallet. Indeed the found IP addresses are stored in the peers.dat file. You can dump a list of some of the recent IP addresses with a console command.
The config file should load automatically if you store it in the default place (same directory as wallet.dat) and give it the default name:
Sync.conf
You can quickly see the status of your wallet connections, staking and block nr by hovering your mouse over the symbols in the bottom right corner of the wallet (while the wallet is the active application). You can also see more info by going to Help -> Console -> Information
Your wallet will work with even 1 connection, but I typically see around a dozen in my wallet.