Difference between revisions of "Connecting to your own Bitcoin node"
m (→Connecting to a local Bitcoin node: LTC incompatibility at startup.) |
Plebeian9000 (talk | contribs) (remove general node configuration requirements, to be placed in another section) |
||
| Line 9: | Line 9: | ||
If you're running a Bitcoin full node on the same machine as Bisq, Bisq should connect to your node on startup—it will look for Bitcoin Core or <code>bitcoind</code> running on <code>localhost</code> on port 8333. | If you're running a Bitcoin full node on the same machine as Bisq, Bisq should connect to your node on startup—it will look for Bitcoin Core or <code>bitcoind</code> running on <code>localhost</code> on port 8333. | ||
| − | + | Just make sure to not be running any other Bitcoin-based altcoin nodes (like LTC) while starting Bisq. | |
| − | |||
| − | |||
| − | |||
= Connecting to another Bitcoin node = | = Connecting to another Bitcoin node = | ||
Revision as of 19:30, 10 February 2021
Bisq will connect to your local Bitcoin node if it finds it upon starting up. This article contains the requirements for this to work correctly.
You can also specify the addresses of particular Bitcoin nodes in Settings > Network Info.
Connecting to a local Bitcoin node
If you're running a Bitcoin full node on the same machine as Bisq, Bisq should connect to your node on startup—it will look for Bitcoin Core or bitcoind running on localhost on port 8333.
Just make sure to not be running any other Bitcoin-based altcoin nodes (like LTC) while starting Bisq.
Connecting to another Bitcoin node
By default, Bisq maximizes your privacy by connecting to nodes run by trusted Bisq contributors.
If you'd like to connect to another node, you can specify its address in Settings > Network Info. Bisq will validate the address and connect to the specified node the next time it starts.
