<!-- This issue tracker is only for technical issues related to Bitcoin Core. General bitcoin questions and/or support requests are best directed to the Bitcoin StackExchange at https://bitcoin.stackexchange.com. For reporting security issues, please read instructions at https://bitcoincore.org/en/contact/. If the node is "stuck" during sync or giving "block checksum mismatch" errors, please ensure your hardware is stable by running memtest and observe CPU temperature with a load-test tool such as linpack before creating an issue! -->
Describe the issue:
Bitcoin-Qt generates non-Tor network traffic on initial launch before allowing the user to change proxy settings. This is an anonymity leak for users who aren't aware of the command-line or bitcoin.conf flags for proxy settings.
What behavior did you expect?
As part of the "Welcome" dialog on initial launch (which currently lets the user choose the data directory), Bitcoin-Qt should ask the user whether they'd like to set proxy settings.
What was the actual behavior (provide screenshots if the issue is GUI-related)?
Bitcoin-Qt doesn't prompt the user to set proxy settings before it starts connecting to the P2P network.
How reliably can you reproduce the issue, what are the steps to do so?
Run bitcoin-qt on a machine that has never run bitcoin-qt before.
What version of Bitcoin Core are you using, where did you get it (website, self-compiled, etc)?
Bitcoin Core 0.16.2, downloaded from https://bitcoincore.org/en/download/
What type of machine are you observing the error on (OS/CPU and disk type)?
GNU/Linux x86 64-bit (Whonix 13, based on Debian Jessie, running under Qubes 3.2). Haswell i7. HDD.
<!-- Any extra information that might be useful in the debugging process. -->
<!--- This is normally the contents of a `debug.log` or `config.log` file. Raw text or a link to a pastebin type site are preferred. -->
