But if you have a fresh wallet that has never been exposed to a public node, then you want to only ever connect to your own node. Going private from that point onwards adds very little. Well, you can if you are testing the software or if you are using a wallet that has already been exposed to a public node. The first is to connect to a Public Server. You can now be confident that your wallet is private and you’re ready to send and receive bitcoin.At the top, you’ll see three options. You have successfully connected Sparrow to your Bitcoin Core node, and setup your wallet. Sparrow will clear the wallet history and rescan from Bitcoin Core from the date provided. You can change the start date and trigger a rescan using the Settings tab.Ĭlick on Settings, then Advanced and edit the date in the dialog that appears. If you don’t see any but expect to, you may have misconfigured your wallet, or set a scan start date that is not early enough. Once completed, the existing transactions should appear in the table. The estimated time remaining is provided in the status bar. This indicates that Sparrow is requesting Bitcoin Core to scan for the existing transactions.ĭepending on the date specified earlier, and the hardware the node is running on, this process might take awhile to complete. If this wallet has existing transactions, you should see a screen similar to the following: You can now click on the Transactions tab at the top. Once you have configured your wallet, click Apply and choose a password to secure it. Refer to the other guides for help in configuring different types of wallet.įor example, you can create a wallet using seed words using the Quick Start guide. You can also change the date and rescan later if necessary. Note you don’t need to be exact, so choose an earlier date if you are unsure. If you are creating a wallet with existing transactions, select the checkbox and choose an approximate date to start scanning from. Select File > New Wallet in the menu.Ĭhoose a name for the wallet (it must be unique). Sparrow will automatically connect to your node, and is now ready to import your wallet. Once you have successfully tested your server setup, you can close the Preferences dialog. Make sure that you are running a recent version of Bitcoin Core, and that there are no firewalls preventing the connection. If Sparrow did not successfully connect, check your configuration settings. If you see Connected to bwt instead, you are using an earlier version of Bitcoin Core (pre v24) which Sparrow connects to using the bwt library. The details you see are provided by Cormorant, a library Sparrow uses to connect to Bitcoin Core. If successful, you should see the following: Sparrow will attempt to connect to Bitcoin Core. Once you have configured Sparrow to match your Bitcoin Core setup, you’re ready to test the connection.Ĭlick Test Connection. Instead of authenticating via a cookie, you will need to select the User/Pass button and enter the username and password you configured in nf earlier. You will then need to configure the URL in Sparrow to match the IP address of the Bitcoin Core machine (the same IP you used in nf). If you are connecting to Bitcoin Core on another machine, make sure you have configured Bitcoin Core correctly as described above. onion address in the URL.īut, it will use the proxy for all other external addresses, such as fetching exchange rates or using Whirlpool.Īlthough connecting to Bitcoin Core over Tor is possible, it is fairly slow.Ĭonsider using a private Electrum server instead if you need to connect over Tor. Sparrow won’t use the proxy to connect to Bitcoin Core unless you specify a. If you have changed the data folder for Bitcoin Core, be sure to select that folder now. Sparrow will connect on localhost (127.0.0.1) using the default port, and authenticate by retrieving the cookie file that Bitcoin Core writes to the data folder every time it starts up. The good news is that with a local setup and the default configuration, you should be ready to go! Open the Preferences dialog and select the Server tab. Once your node has synced, you are ready to connect Sparrow Wallet. If you are still busy syncing your node, it’s best to wait until this is done, as you won’t have a complete ledger yet so Sparrow won’t be able to find your transactions. You can now restart Bitcoin Core to take advantage of the new configuration. Secondly, if you want to reverse this, you will need to start your full blockchain sync from the beginning again.Already scanned transactions are fine, so if your wallet reflects them (or is new) you are good going forward. Firstly, you won’t be able to scan for transactions earlier than whatever the earliest retained (unpruned) block is.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |