Update faq.md

docs/for-users/embedded-node/faq.md

@@ -97,13 +97,33 @@ First, you should try doing a rescan by going to `Settings` -> `Embedded node` -
 
 If rescan fails to correct the balance, you'll likely have to add some more Neutrino peers, especially if the LND logs display messages about peer connection timeouts.
 
+Why this could happen? Because from your location, your internet conenction have a high latency to the neutrino peer. Neutrino needs a better time response in order to be able to sync faster the blocks information. So if you will have a ping of 300ms from your device to the neutrino peer, is likely to not be able to sync well. So it is recommended to switch to another server that is closer to your location. Remember, this have nothing to do with your internet speed. Time response is not speed, is distance.
+
 To add more Neutrino peers got to `Settings` -> `Embedded node` -> `Peers` -> `Neutrino Peers`. Then uncheck `Connect only to the specified peers`, restart the app, and try another rescan. This will allow your ZEUS wallet node to find new peers to connect to automatically.
 
+You can also have a preferred list of peers if you like. Here are some well known public neutrino peers that you can switch to from the default one.
+
+These ones works better with users from North American continent:
+- btcd1.lnolymp.us | btcd2.lnolymp.us
+- btcd-mainnet.lightning.computer
+- node.eldamar.icu
+- noad.sathoarder.com
+- bb1.breez.technology | bb2.breez.technology
+
+This one works better with users from European continent:
+- node.blixtwallet.com
+
+If you want to look for some closer to your loceation, here is a full live list of4 Bitcoin neds with Neutrino activated (remember that these could change or disappear in time so review your neutrino peers ping if you notice issues and switch to better ones):
+- [https://bitnodes.io/nodes/?q=NODE_COMPACT_FILTERS](https://bitnodes.io/nodes/?q=NODE_COMPACT_FILTERS)
+
+Keep in mind that this list of public neutrino peers might not exist in the future or servers name will be changed or relocated. Also there's a new Neutrino code release in the pipeline that will improve drastically the sync issues and more tolerant to high response time. In any case, faster is better.
+
 If you have your own remote node, you may also want manually add it in the Peers list. You can [use this guide to enabled 'Neutrino mode' in Bitcoin Core](https://docs.lightning.engineering/lightning-network-tools/lnd/enable-neutrino-mode-in-bitcoin-core). BTCD has Neutrino on by default.
 
 #### If it's lightning funds that have gone missing
 
-Go to the Channels view by hitting the icon in the bottom right corner of the main view then, hit the header at the top of the Channels view to toggle between open, pending, and closed channels. Mutually closed channels should return to your on-chain balance once they settle on-chain. Force closed channels can take up to two weeks to return to your on-chain wallet. These channels will appear in the pending channels list until settled.
+Go to the Channels view by hitting the icon in the bottom right corner of the main view then, and first thing try to refresh the screen by swiping down, few times.
+If still do not appear online, hit the header at the top of the Channels view to toggle between open, pending, and closed channels. Mutually closed channels should return to your on-chain balance once they settle on-chain. Force closed channels can take up to two weeks to return to your on-chain wallet. These channels will appear in the pending channels list until settled.
 
 ## I'm having payments sending lightning payments with ZEUS
 
@@ -123,4 +143,4 @@ This typically happens when either the blockchain headers or lightning network g
 
  3. Go to `Settings` -> `Embedded node` -> `Express Graph Sync` and enable the second toggle labeled `Reset express graph sync on startup`, then restart the app. This will resync your lightning network graph data.
 
- 4. Restarting the app to jostle the state and get it online again.
+ 4. Restarting the app to jostle the state and get it online again.

docs/for-users/getting-started/tips.md

@@ -29,4 +29,32 @@ At the left hand side, we can see the the inputs and its corresponding outpoints
 
 Anchor outputs are additional outputs added to a commitment transaction in a channel, with each party having one output. These outputs are encumbered with a CSV condition, acting as timelocks, allowing parties to bump fees using Child Pays for Parent (CPFP) to facilitate transaction confirmation. This mechanism enables users to set fees for closing transactions, enhancing flexibility and security within the Lightning Network. 
 
-Anchor outputs address the challenge of delayed confirmation due to preset transaction fees at the time of crafting commitment transactions. By allowing parties to adjust fees post-transaction creation, anchor outputs empower users to adapt to changing fee dynamics, ensuring timely and efficient transaction processing. 
+Anchor outputs address the challenge of delayed confirmation due to preset transaction fees at the time of crafting commitment transactions. By allowing parties to adjust fees post-transaction creation, anchor outputs empower users to adapt to changing fee dynamics, ensuring timely and efficient transaction processing.
+
+# What is a Neutrino peer ?
+
+Neutrino is a lightweight Bitcoin Core client (that was implemented with [BIP157](https://github.com/bitcoin/bips/blob/master/bip-0157.mediawiki)) which enable our Bitcoin node to serve block data to remote LND nodes in a private P2P mode and with minimum data storage needed (almost insignificant), ideal for mobile LN nodes like Zeus.
+
+More Neutrino nodes, well distributed across the world, will help a lot the use of mobile LN nodes like Zeus, with a more decentralized distribution of neutrino peers. A lower response time (ping) it means that is closer to your location and will reduce drastically the sync issues of your Zeus node. A higher response time (in ms) it means you are too far to the neutrino peer and the communication could have a serious impact onto your Zeus sync.
+
+This can be useful if we are already running a fully synced Bitcoin node somewhere and want to use it for one or multiple remote instances of LND. If we have the additional bandwidth and storage available, we might also want to make our existing Bitcoin node available to the public as a free service. 
+
+Easily available public Neutrino instances help the network grow more robust and remove bottlenecks. Such services are a prerequisite to light clients, which do not have a copy of the Bitcoin Blockchain available locally.
+
+If you run a full Bitcoin Core node you can connect your Zeus embedded node with it by amend your Core node bitcoin.conf, add the following paramenters:
+```
+blockfilterindex=1
+peerblockfilters=1
+```
+
+Once you restart your node, it will resync the Blockchain and build the blockfilterindex. This may take a while depending on your node’s available memory and computing power.
+
+As soon as Bitcoin Core is running, it will now advertise itself to the network if you have set this in your configuration. To disable discovery, you may set `discover=0` in your bitcoin.conf.
+
+Connect from your Zeus embedded node:
+
+This option is good in case you are connecting from a location where the default Neutrino peers provided in Zeus will have a high latency that could not provide a good sync time. So connecting directly to your local node will improve a lot the use of Zeus.
+
+Go to Zeus `Settings --> Embedded Node --> Peers --> Neutrino peers` then add your Bitcoin Neutrino node IP (or FQDN if you have one). It must be delivered over clearnet.
+
+If your Bitcoin node operate only over Tor network it will not serve too much for this purpose, due to high latency offeered over Tor and will not offer more privacy anyways (Neutrino already offer enough privacy).

docs/lightning-address/fees.md

@@ -16,4 +16,16 @@ Our self-custodial lightning address incurs the following fees:
 
 You're paying not only for us to host the infrastructure and process payments, but to hold the payments up to 24 hours; there's a real cost to keeping those sats in transit and using an HTLC slot on our channel.
 
-Learn about [how Zaplocker payments work](https://github.com/supertestnet/zaplocker#how-it-works).
+Learn about [how Zaplocker payments work](https://github.com/supertestnet/zaplocker#how-it-works).
+
+# More details about Zeus fees
+
+When people send sats to your ZeusPay lightning address, that 2.5% fee applies.
+
+If you make an invoice and let them pay the invoice, the 2.5% fee does NOT apply, the payer pay the fees. Same with payments you do, no 2.5% fee.
+
+It is receiving via your ZeusPay lightning address only.
+
+Zeus doesn't receive only through a LN address and only through a single channel.
+
+You can make LN invoices and receive through multiple channels with many different routing fees. Learn more about channel fees [here](https://docs.lightning.engineering/lightning-network-tools/lnd/channel-fees).

docs/lsp/fees.md

@@ -29,3 +29,15 @@ Our self-custodial lightning address incurs the following fees:
 | <= 20 sats                                 | 10%           |
 | <= 100 sats                                | 5%            |
 | > 100 sats                                 | 2.5%          |
+
+# More details about Zeus fees
+
+When people send sats to your ZeusPay lightning address, that 2.5% fee applies.
+
+If you make an invoice and let them pay the invoice, the 2.5% fee does NOT apply, the payer pay the fees. Same with payments you do, no 2.5% fee.
+
+It is receiving via your ZeusPay lightning address only.
+
+Zeus doesn't receive only through a LN address and only through a single channel.
+
+You can make LN invoices and receive through multiple channels with many different routing fees. Learn more about channel fees [here](https://docs.lightning.engineering/lightning-network-tools/lnd/channel-fees).