| 1 |
--- |
| 2 |
title: First start |
| 3 |
nav_title: First start |
| 4 |
category: getting-started |
| 5 |
weight: 0 |
| 6 |
--- |
| 7 |
|
| 8 |
This section will guide you through the short wizard that shows up when you start Feather for the first time. |
| 9 |
|
| 10 |
If you are looking to install Feather, see the **Installation** section in the sidebar. |
| 11 |
|
| 12 |
--- |
| 13 |
|
| 14 |
- If you experience any difficulties while using Feather, have a question related to this documentation, or want to submit a feature request, please feel free to [contact](report-an-issue) the developers. |
| 15 |
|
| 16 |
- In the sidebar, near the bottom, is a **Troubleshooting** section that will help you solve common issues. |
| 17 |
|
| 18 |
--- |
| 19 |
|
| 20 |
## How do you want to connect to the Monero network? |
| 21 |
|
| 22 |
Feather must connect to a node in order to scan for your transactions. A node is a computer hosting a copy of the Monero blockchain. (For more information, see [Nodes](nodes).) |
| 23 |
|
| 24 |
Connecting to node hosted by a third party comes with some privacy risks. Please review the information in [Nodes](nodes) to learn if these risks are relevant to your threat model. |
| 25 |
|
| 26 |
### Auto connect |
| 27 |
|
| 28 |
Feather has a built-in list of high-performance nodes hosted by the Feather team and trusted members of the Monero community. In most cases you want to let Feather pick one of these nodes at random. |
| 29 |
|
| 30 |
We recommend using this option for **most** users. |
| 31 |
|
| 32 |
### Connecting to a custom remote node |
| 33 |
|
| 34 |
If you do not want to connect to one the built-in nodes, select **Select node manually**. |
| 35 |
|
| 36 |
Enter the address and port in the textbox. For example: `node.monerodevs.org:18089`. |
| 37 |
|
| 38 |
### Connecting to a local node |
| 39 |
|
| 40 |
Feather automatically detects the presence of a [local node](local-node) on the default port. |
| 41 |
|
| 42 |
Feather does not manage a local node for you. |
| 43 |
If you want to run a local node, follow the steps in [this guide](https://moneroguides.org/tutorials/01x02-setting-up-your-own-node/) to set one up. |
| 44 |
|
| 45 |
## How should Feather route its network traffic? |
| 46 |
|
| 47 |
By default, Feather routes all network traffic over Tor, except for wallet synchronization. Synchronization requires a lot of data transfer and is therefore very slow over Tor. A remote node does not learn much about your wallet during synchronization (for more information see [Nodes](nodes)). We believe this is a reasonable privacy / convenience trade-off. |
| 48 |
|
| 49 |
We recommend using the default option unless: |
| 50 |
|
| 51 |
- You are unable to connect to the Tor network, or |
| 52 |
- Your threat model requires always connecting over Tor |
| 53 |
|
| 54 |
For information see: [Tor support](tor-support) and [Network traffic](network-traffic). |
| 55 |
|
| 56 |
## Do you want to obtain third-party data? |
| 57 |
|
| 58 |
For more information, see: [Websocket](websocket). |