diff --git a/source/support/FAQ/bitcoin-faq.rst b/source/support/FAQ/bitcoin-faq.rst index 3659de3..b802d6a 100644 --- a/source/support/FAQ/bitcoin-faq.rst +++ b/source/support/FAQ/bitcoin-faq.rst @@ -9,20 +9,16 @@ You can learn more about the Initial Block Download in `this video `_ and select the tutorial based on your operating system. + +More guides, particularly in video form, are forthcoming. + +Is BlueWallet an option? +------------------------ +BlueWallet requires a separate backend service called LNDHub, which is not available on the Embassy at this time. + +I want to use my hardware signer, such as Coldcard or Trezor, with my Embassy. How does this work? +--------------------------------------------------------------------------------------------------- +You do not use hardware signers directly with your node. Hardware signers interface with wallets, and wallets interface with nodes. + +Node (Embassy) <— Wallet (Specter, Sparrow, Electrum) <— Hardware signer (Coldcard, Trezor) + +You would use your hardware signer with your wallet, then instruct that wallet to use Embassy as its node. + +- Nodes are for interacting with the Bitcoin network: enforcing consensus rules, validating and relaying blocks/transactions, and broadcasting transactions. + +- Wallets are for constructing and viewing transactions, as well as generating addresses. + +- Signers are for generating and storing keys, as well as signing transactions. + +The reason there is so much confusion about these 3 concepts is that the Bitcoin Core Node comes with its own Wallet (which you should not use), and that wallet is also a signer. In fact, most wallets double as signers, and most wallets do NOT support connecting to your own node. So, most wallets are actually serving as a wallet, a node, and a signer, which might be convenient, but it is neither trustless nor maximally secure. Ideally, you are using a wallet that supports both integrating with a hardware signer (like Coldcard or Trezor) AND a backend node (like on the Embassy). + +Please note: of the wallets listed (Specter/Sparrow/Electrum), only Specter is currently able to use Embassy as it's node, but the other two should be available soon. + + Why would I want to run a lightning node? ----------------------------------------- The Lightning Network (LN) is a second 'layer,' built on top of the Bitcoin Protocol. As a result all transactions on LN are backed up by the full security of the Bitcoin network. Lightning is designed for instant payments between nodes, but similar to running a Bitcoin node, running your own is the only way to be sovereign. When you have your own node, you will have the convenience of linking a Lightning wallet, for use on the go. It is also possible to earn an income (granted a very small one at this time), if you are willing to learn how to become a 'routing node.' @@ -53,55 +109,6 @@ Is there a solution to this? ---------------------------- Yes, the concept of a Watchtower was originally conceptualized in the LN whitepaper. A Watchtower is simply a lightning node to which you can give the authority to monitor transactions associated with your open payment channels. -Is a wallet vulnerable to hacking if it’s always online?? ---------------------------------------------------------- -Funds are not stored on the node typically. The node simply serves as a source of truth for the state of the blockchain. Attacks depend on where the keys are and where the signing happens. You can use something like a hardware wallet for better security. Though, to be fair, a lot of attacks depend on you or your machine being targeted specifically, and a whole bunch of attack vectors are highly theoretical and obscure. -Most successful attacks seem to be either fake/doctored software or a social attack (tricking you into installing some malware or giving your seed outright or something like that). -Keep in mind, however, the more value there is out there to steal, the more sophisticated attacks will get automated (bots, crawlers etc). So its not just the risk profile of today, but also tomorrow you have to consider. That’s why something like a hardware wallet or dedicated mobile device for key signing is a good idea. -Even if your wallet is plugged into your Embassy, whether your wallet is hot or cold depends on the hardware that stores the keys. - -How does Bitcoin Proxy request (and verify) data when that data is needed by some app using it? ------------------------------------------------------------------------------------------------ -Proxy fetches blocks from your pruned node if it still has them, and fetches them from peers when it does not. Proxy can ensures the fetched block is valid by comparing it to its header, which is retained by the pruned node. The header is a product of the hash of the block itself, amongst other things, so it can't be - -What is the difference between the Bitcoin Wallet Tracker and the Electrum Personal Server? -------------------------------------------------------------------------------------------- -Bitcoin Wallet Tracker and Electrum Personal Server are 2 services that do the same thing, similar to bitcoind vs btcd, or lnd vs c-lightning. -Both work with your Bitcoin node to provide a richer set of information to wallets than could be done with bitcoind alone. They are basically identical in purpose, their differences are notably in the software memory requirements and how snappily they can answer the same questions. -Electrum (and some other wallets) require more than just a Bitcoin node to run in a sovereign way, they require an “Electrum Server”. Both Electrum Personal Server and Bitcoin Wallet Tracker are “Electrum servers”. - -I want to use my hardware signer, such as Coldcard or Trezor, with my Embassy. How does this work? ---------------------------------------------------------------------------------------------------- -You do not use hardware signers directly with your node. Hardware signers interface with wallets, and wallets interface with nodes. - -Node (Embassy) <— Wallet (Specter, Sparrow, Electrum) <— Hardware signer (Coldcard, Trezor) - -You would use your hardware signer with your wallet, then instruct that wallet to use Embassy as its node. - -- Nodes are for interacting with the Bitcoin network: enforcing consensus rules, validating and relaying blocks/transactions, and broadcasting transactions. - -- Wallets are for constructing and viewing transactions, as well as generating addresses. - -- Signers are for generating and storing keys, as well as signing transactions. - -The reason there is so much confusion about these 3 concepts is that the Bitcoin Core Node comes with its own Wallet (which you should not use), and that wallet is also a signer. In fact, most wallets double as signers, and most wallets do NOT support connecting to your own node. So, most wallets are actually serving as a wallet, a node, and a signer, which might be convenient, but it is neither trustless nor maximally secure. Ideally, you are using a wallet that supports both integrating with a hardware signer (like Coldcard or Trezor) AND a backend node (like on the Embassy). - -Please note: of the wallets listed (Specter/Sparrow/Electrum), only Specter is currently able to use Embassy as it's node, but the other two should be available soon. - -Which wallets can I use that sync with my Embassy Bitcoin node? ---------------------------------------------------------------- -There are many wallets that support linking to your own full node. You will need one that supports Tor. Here are a few options that are compatible: FullyNoded, Samourai, Specter, Wasabi, Zap, and Zeus. - -Is there a guide for connecting Specter Wallet to my Embassy? -------------------------------------------------------------- -There is. Please follow the integration guide `here `_ and select the tutorial based on your operating system. - -More guides, particularly in video form, are forthcoming. - -Is BlueWallet an option? ------------------------- -BlueWallet requires a separate backend service called LNDHub, which is not available on the Embassy at this time. - Is it possible to run c-lightning and lnd parallel on the Embassy? ------------------------------------------------------------------ Yes, you may run both. They will operate in their own environments and allow you to run services that depend on either.