GITBOOK-26: No subject

SUMMARY.md

@@ -20,7 +20,7 @@
   * [2.1 Bitcoin client: Bitcoin Core](bitcoin/bitcoin/bitcoin-client.md)
   * [2.2 Electrum Server: Fulcrum](bitcoin/bitcoin/electrum-server.md)
   * [2.3 Blockchain explorer: BTC RPC Explorer](bitcoin/bitcoin/blockchain-explorer.md)
-  * [2.4 Desktop wallet: Sparrow wallet](bitcoin/bitcoin/desktop-wallet.md)
+  * [2.4 Desktop signing app: Sparrow Wallet](bitcoin/bitcoin/desktop-signing-app-sparrow.md)
 
 ## ⚡ Lightning
 

bitcoin/bitcoin/desktop-wallet.md → bitcoin/bitcoin/desktop-signing-app-sparrow.md

@@ -15,7 +15,7 @@ layout:
     visible: true
 ---
 
-# 2.4 Desktop wallet: Sparrow wallet
+# 2.4 Desktop signing app: Sparrow Wallet
 
 We install [Sparrow wallet](https://github.com/sparrowwallet/sparrow) on a computer and connect it to your Electrum server on your node for private Bitcoin on-chain transactions.
 
@@ -95,7 +95,7 @@ Let's go back to the wallet and check that it is connected to our own Electrum s
 
 You're set! Sparrow is now configured to connect to your Electrum server from within your local network.
 
-For maximal privacy, we highly recommend that you set up the Tor proxy when using Sparrow within your local network over clearnet. Check the [optional section](desktop-wallet.md#optional-set-up-a-tor-proxy-for-external-services) at the end of this guide.
+For maximal privacy, we highly recommend that you set up the Tor proxy when using Sparrow within your local network over clearnet. Check the [optional section](desktop-signing-app-sparrow.md#optional-set-up-a-tor-proxy-for-external-services) at the end of this guide.
 
 ## Sparrow in action
 

bitcoin/bitcoin/electrum-server.md

@@ -19,11 +19,7 @@ layout:
 
 [Fulcrum](https://github.com/cculianu/Fulcrum) is a fast & nimble SPV server for Bitcoin created by [Calin Culianu](https://github.com/cculianu). It can be used as an alternative to Electrs because of its performance, as we can see in Craig Raw's [comparison](https://www.sparrowwallet.com/docs/server-performance.html) of servers.
 
-<div data-full-width="false">
-
-<figure><img src="../../.gitbook/assets/Fulcrum_logo" alt="" width="375"><figcaption></figcaption></figure>
-
-</div>
+<div data-full-width="false"><figure><img src="../../.gitbook/assets/Fulcrum_logo" alt="" width="375"><figcaption></figcaption></figure></div>
 
 ## Requirements
 
@@ -451,14 +447,10 @@ sudo systemctl start fulcrum
 
 **Example** of expected output on the first terminal with `journalctl -fu fulcrum` ⬇️
 
-<div data-full-width="false">
-
-<figure><img src="../../.gitbook/assets/fulcrum-index.PNG" alt=""><figcaption></figcaption></figure>
-
-</div>
+<div data-full-width="false"><figure><img src="../../.gitbook/assets/fulcrum-index.PNG" alt=""><figcaption></figcaption></figure></div>
 
 {% hint style="info" %}
-> Fulcrum must first fully index the blockchain and compact its database before you can connect to it with your wallets. This can take up to \~1.5 - 4 days or more, depending on the hardware. Only proceed with the [Blockchain explorer: BTC RPC Explorer](blockchain-explorer.md) and [Desktop Wallet Section](desktop-wallet.md) once Fulcrum is ready.
+> Fulcrum must first fully index the blockchain and compact its database before you can connect to it with your wallets. This can take up to \~1.5 - 4 days or more, depending on the hardware. Only proceed with the [Blockchain explorer: BTC RPC Explorer](blockchain-explorer.md) and [Desktop Wallet Section](desktop-signing-app-sparrow.md) once Fulcrum is ready.
 
 > Fulcrum will now index the whole Bitcoin blockchain so that it can provide all necessary information to wallets. With this, the wallets you use no longer need to connect to any third-party server to communicate with the Bitcoin peer-to-peer network.
 {% endhint %}
@@ -484,9 +476,9 @@ sudo rm -r /data/fulcrum/fulcrum_db/*
 sudo systemctl start fulcrum
 ```
 
-\-> You should see the logs of the [Run process](electrum-server.md#run) before again
+-> You should see the logs of the [Run process](electrum-server.md#run) before again
 
-\-> The troubleshooting note could be helpful after experiencing **data corruption due to a power outage** during normal operation
+-> The troubleshooting note could be helpful after experiencing **data corruption due to a power outage** during normal operation
 {% endhint %}
 
 * When you see logs like this `SrvMgr: starting 3 services ...`, which means that Fulcrum is fully indexed
@@ -521,7 +513,7 @@ tcp   LISTEN 0      50      127.0.0.1:8000       0.0.0.0:*    users:(("Fulcrum",
 ```
 
 {% hint style="success" %}
-Congrats! Now you have a high-performance and self-hosted Electrum Server on your node. Now you can process installing the [Blockchain Explorer: BTC RPC Explorer](blockchain-explorer.md) or connect your [Desktop wallet: Sparrow wallet](desktop-wallet.md) or [Electrum Wallet ](../../bonus/bitcoin/electrum-wallet-desktop.md)[Desktop](../../bonus/bitcoin/electrum-wallet-desktop.md)
+Congrats! Now you have a high-performance and self-hosted Electrum Server on your node. Now you can process installing the [Blockchain Explorer: BTC RPC Explorer](blockchain-explorer.md) or connect your [Desktop signing app: Sparrow Wallet](desktop-signing-app-sparrow.md) or [Electrum Wallet ](../../bonus/bitcoin/electrum-wallet-desktop.md)[Desktop](../../bonus/bitcoin/electrum-wallet-desktop.md)
 {% endhint %}
 
 ## Extras (optional)

bonus-guides/system/nym-mixnet.md

@@ -17,6 +17,10 @@ layout:
 
 The NYM mixnet technology ensures enhanced privacy and anonymity for online communications. It utilizes a decentralized network to encrypt and route data, ensuring that the origin and destination are concealed. By implementing the NYM mixnet, users can protect their online activities and sensitive information, safeguarding their privacy from surveillance and censorship. This advanced networking technology provides a secure environment for transmitting data and maintaining anonymity.
 
+{% hint style="danger" %}
+Notice: This guide is out of maintenance, the following steps may not be correct
+{% endhint %}
+
 {% hint style="danger" %}
 Status: Not tested on RaMiX
 {% endhint %}
@@ -684,7 +688,7 @@ If you have installed the NYM socks5 client installed in a machine inside of you
 
 #### Sparrow desktop
 
-Follow the [Desktop wallet: Sparrow Wallet](../../bitcoin/bitcoin/desktop-wallet.md) until the [(Optional) Set up a Tor proxy for external services](../../bitcoin/bitcoin/desktop-wallet.md#optional-set-up-a-tor-proxy-for-external-services), which could be used for these 2 cases of uses:
+Follow the [Desktop wallet: Sparrow Wallet](../../bitcoin/bitcoin/desktop-signing-app-sparrow.md) until the [(Optional) Set up a Tor proxy for external services](../../bitcoin/bitcoin/desktop-signing-app-sparrow.md#optional-set-up-a-tor-proxy-for-external-services), which could be used for these 2 cases of uses:
 
 1. If you don't have your node and you want to **proxy** all connections (**The Electrum Servers** of the wallet & **third-party server connections**) using the NYM mixnet
 

bonus/bitcoin/README.md

@@ -25,9 +25,9 @@ layout:
 
 * [**Electrs**](electrs.md) - an efficient re-implementation of Electrum Server in Rust
 
-### Wallets
+### Signing apps
 
-#### Desktop wallets
+#### Desktop
 
 * [**Electrum Wallet Desktop**](electrum-wallet-desktop.md) - a feature-rich desktop wallet for power-users
 
@@ -46,7 +46,7 @@ layout:
 
 ### Testnet
 
-* [**Running a Testnet RaMiX Node**](ramix-on-testnet.md) - configure your RaMiX for use on testnet
+* [**Running a Testnet RaMiX node**](ramix-on-testnet.md) - configure your RaMiX for use on testnet
 
 ### Payment processors
 

bonus/bitcoin/electrs.md

@@ -36,7 +36,7 @@ Difficulty: Medium
 
 ## Preparations
 
-\-> Make sure that you have followed the [Activate mempool & reduce 'dbcache' after a full sync](../../bitcoin/bitcoin/bitcoin-client.md#activate-mempool-and-reduce-dbcache-after-a-full-sync) section.
+-> Make sure that you have followed the [Activate mempool & reduce 'dbcache' after a full sync](../../bitcoin/bitcoin/bitcoin-client.md#activate-mempool-and-reduce-dbcache-after-a-full-sync) section.
 
 ### Install dependencies
 
@@ -456,7 +456,7 @@ sudo systemctl start electrs
 </details>
 
 {% hint style="success" %}
-Electrs will now index the Bitcoin blockchain to provide all necessary information to wallets. With this, the wallets you use no longer need to connect to any third-party server to communicate with the Bitcoin peer-to-peer network
+Congrats! Now you have a self-hosted Electrum Server on your node. Now you can process installing the [Blockchain Explorer: BTC RPC Explorer](../../bitcoin/bitcoin/blockchain-explorer.md) or connect your [Desktop signing app: Sparrow Wallet](../../bitcoin/bitcoin/desktop-signing-app-sparrow.md) or [Electrum Wallet ](electrum-wallet-desktop.md)[Desktop](electrum-wallet-desktop.md)
 {% endhint %}
 
 ### Validation
@@ -487,7 +487,7 @@ tcp   LISTEN 0   511   0.0.0.0:50022   0.0.0.0:*    users:(("nginx",pid=719,fd=5
 ```
 
 {% hint style="info" %}
-Electrs must first fully index the blockchain and compact its database before you can connect to it with your wallets. This can take a few hours. Only proceed with the [next section](../../bitcoin/bitcoin/desktop-wallet.md) once Electrs is ready
+Electrs must first fully index the blockchain and compact its database before you can connect to it with your wallets. This can take a few hours. Only proceed with the [next section](../../bitcoin/bitcoin/desktop-signing-app-sparrow.md) once Electrs is ready
 {% endhint %}
 
 ## Extras (optional)

bonus/bitcoin/ramix-on-testnet.md

@@ -38,7 +38,11 @@ The great news is that most of the RaMiX guide can be used as-is. The small adju
 
 ## Bitcoin
 
-### [Bitcoin client: Bitcoin Core](../../bitcoin/bitcoin/bitcoin-client.md) (mainnet + testnet simultaneous mode)
+### [Bitcoin client: Bitcoin Core](../../bitcoin/bitcoin/bitcoin-client.md)
+
+{% hint style="info" %}
+Mainnet + testnet simultaneous mode
+{% endhint %}
 
 * Follow the complete RaMiX guide from the beginning [(Bitcoin client included)](../../bitcoin/bitcoin/bitcoin-client.md), when you arrive at the ["Configuration section"](../../bitcoin/bitcoin/bitcoin-client.md#configuration)
 
@@ -153,7 +157,11 @@ Use the flag `--testnet4` when you use the `bitcoin-cli` commands, e.g `bitcoin-
 The rest of the Bitcoin client guide is the same as the mainnet mode
 {% endhint %}
 
-### [Electrum server: Fulcrum](../../bitcoin/bitcoin/electrum-server.md) (only testnet mode)
+### [Electrum server: Fulcrum](../../bitcoin/bitcoin/electrum-server.md)
+
+{% hint style="info" %}
+Only testnet mode
+{% endhint %}
 
 Follow the complete Electrum server guide from the beginning, when you arrive at the ["Configure Firewall"](../../bitcoin/bitcoin/electrum-server.md#configure-firewall) section:
 
@@ -257,7 +265,7 @@ You should now be able to connect to your Fulcrum server remotely via Tor using
 The rest of the **Fulcrum** guide is the same as the mainnet mode
 {% endhint %}
 
-### [Blockchain Explorer: BTC RPC Explorer](../../bitcoin/bitcoin/blockchain-explorer.md) (not Testnet4 compatible)
+### [Blockchain Explorer: BTC RPC Explorer](../../bitcoin/bitcoin/blockchain-explorer.md)
 
 {% hint style="danger" %}
 #### Not Testnet4 compatible yet, the next steps are not valid!
@@ -332,7 +340,7 @@ lncli --network=testnet --tlscertpath /data/lnd/tls.cert.tmp create
 ```
 
 {% hint style="info" %}
-Note that it has [a list of testnet aliases](https://raw.githubusercontent.com/minibolt-guide/minibolt/main/resources/.bash\_aliases) related to these commonly used commands to make it easier to introduce in the terminal. Follow the ["Aliases bonus guide"](../system/aliases.md) to install it
+Note that it has [a list of testnet aliases](https://raw.githubusercontent.com/minibolt-guide/minibolt/main/resources/.bash_aliases) related to these commonly used commands to make it easier to introduce in the terminal. Follow the ["Aliases bonus guide"](../system/aliases.md) to install it
 {% endhint %}
 
 {% hint style="success" %}
@@ -414,7 +422,11 @@ Be careful to add `--nocert` parameter only to the onion and Wireguard VPN netwo
 
 ## Bonus section
 
-### Bitcoin: [Electrs](electrs.md) (only testnet mode)
+### Bitcoin: [Electrs](electrs.md)
+
+{% hint style="info" %}
+Only testnet mode
+{% endhint %}
 
 Follow the complete guide from the beginning, when you arrive at the [Reverse proxy & Firewall](electrs.md#reverse-proxy-and-firewall) section, follow the next steps:
 

bonus/bitcoin/sparrow-server.md

@@ -23,6 +23,10 @@ layout:
 
 Sparrow Server is a stripped down version of Sparrow that can be run on systems without displays. It's primarily intended as a configuration utility for running Sparrow as a server daemon.
 
+{% hint style="danger" %}
+Notice: This guide is out of maintenance, the following steps may not be correct
+{% endhint %}
+
 {% hint style="danger" %}
 Status: Not tested on RaMiX
 {% endhint %}

bonus/system/aliases.md

@@ -33,7 +33,7 @@ Difficulty: Easy
 
 ## Introduction
 
-The following list of aliases was derived from contributions by [RobClark56](https://github.com/robclark56) and [2FakTor](https://github.com/twofaktor).
+The following list of aliases was derived from contributions by [RobClark56](https://github.com/robclark56).
 
 ## Installation
 
@@ -109,7 +109,7 @@ nginx version: nginx/1.18.0 (Ubuntu)
 Follow again the [Set up Aliases](aliases.md#set-up-aliases) section again to overwrite aliases.
 
 {% hint style="info" %}
-You can see if the aliases have a recent update by entering [here](https://github.com/minibolt-guide/minibolt/commits/main/resources/.bash\_aliases)
+You can see if the aliases have a recent update by entering [here](https://github.com/minibolt-guide/minibolt/commits/main/resources/.bash_aliases)
 {% endhint %}
 
 ## Uninstall

index-1/privacy.md

@@ -30,11 +30,7 @@ True, it's only your IP address that is revealed, but using services like [iploc
 
 ## Tor Project
 
-<div align="left">
-
-<img src="../images/tor-logo.png" alt="" width="166">
-
-</div>
+<div align="left"><img src="../images/tor-logo.png" alt="" width="166"></div>
 
 We use Tor, a free software built by the [Tor Project](https://www.torproject.org). It allows you to anonymize internet traffic by routing it through a network of nodes, hiding your location and usage profile.
 
@@ -207,18 +203,14 @@ Removed /etc/systemd/system/multi-user.target.wants/tor.service.
 {% endhint %}
 
 {% hint style="info" %}
-\-> If you want to **avoid your ISP knowing you are using Tor**, follow the [**Add obfs4 bridge to the default Tor instance**](../bonus-guides/system/tor-services.md#add-obfs4-bridge-to-the-default-tor-instance) section on the Tor services bonus guide to use ofbs4 bridges
+-> If you want to **avoid your ISP knowing you are using Tor**, follow the [**Add obfs4 bridge to the default Tor instance**](../bonus-guides/system/tor-services.md#add-obfs4-bridge-to-the-default-tor-instance) section on the Tor services bonus guide to use ofbs4 bridges
 
-\-> You can host [**your Tor obfs4 bridge**](../bonus-guides/system/tor-services.md#obsf4-bridge) or connect to an external one as mentioned before
+-> You can host [**your Tor obfs4 bridge**](../bonus-guides/system/tor-services.md#obsf4-bridge) or connect to an external one as mentioned before
 {% endhint %}
 
 ## I2P Project
 
-<div align="left">
-
-<img src="../images/i2pd.png" alt="" width="150">
-
-</div>
+<div align="left"><img src="../images/i2pd.png" alt="" width="150"></div>
 
 [I2P](https://geti2p.net/en/) is a universal anonymous network layer. All communications over I2P are anonymous and end-to-end encrypted, participants don't reveal their real IP addresses. I2P allows people from all around the world to communicate and share information without restrictions.
 
@@ -475,7 +467,7 @@ You also need to have Tor installed on your regular computer where you start the
 
 * **Windows**:
 
-To enable Tor in the background follow the same instructions for the [preparations](../bitcoin/bitcoin/desktop-wallet.md#preparations-on-your-computer) section of the Desktop Wallet guide.
+To enable Tor in the background follow the same instructions for the [preparations](../bitcoin/bitcoin/desktop-signing-app-sparrow.md#preparations-on-your-computer) section of the Desktop Wallet guide.
 
 * PuTTy:
   * Follow the same instructions of the [remote access section](remote-access.md#access-with-secure-shell) for Putty, but this time type the `.onion` address on the hostname.
@@ -609,12 +601,12 @@ Click on the OK button, and try to navigate to some clearnet domain like [https:
 {% hint style="info" %}
 You can also go to this [website](https://check.torproject.org/) and see "_Congratulations. This browser is configured to use Tor."_
 
-Also, you can use the Tor proxy connection to reach clearnet or third-party address connection on Sparrow wallet. Check out the [Desktop wallet: Sparrow wallet](../bitcoin/bitcoin/desktop-wallet.md) guide to get instructions.
+Also, you can use the Tor proxy connection to reach clearnet or third-party address connection on Sparrow wallet. Check out the [Desktop wallet: Sparrow wallet](../bitcoin/bitcoin/desktop-signing-app-sparrow.md) guide to get instructions.
 {% endhint %}
 
 ## Upgrade Tor and I2P
 
-The latest release can be found on the [official Tor web page](https://gitweb.torproject.org/tor.git/plain/ChangeLog) or the [unofficial GitHub page](https://github.com/torproject/tor/tags) and for I2P on the [PPA page](https://launchpad.net/\~purplei2p/+archive/ubuntu/i2pd). To upgrade type this command:
+The latest release can be found on the [official Tor web page](https://gitweb.torproject.org/tor.git/plain/ChangeLog) or the [unofficial GitHub page](https://github.com/torproject/tor/tags) and for I2P on the [PPA page](https://launchpad.net/~purplei2p/+archive/ubuntu/i2pd). To upgrade type this command:
 
 ```sh
 sudo apt update && sudo apt upgrade
@@ -700,9 +692,9 @@ sudo systemctl start tor
 ```
 
 {% hint style="info" %}
-\-> If your new set of entry guards still produces the stream error, try connecting to the internet using a cable if you're using Wireless. If that doesn't help, I'd suggest downloading [Wireshark](https://www.wireshark.org/) and seeing if you're getting drowned in TCP transmission errors for non-Tor traffic. If yes, your ISP is who you need to talk to
+-> If your new set of entry guards still produces the stream error, try connecting to the internet using a cable if you're using Wireless. If that doesn't help, I'd suggest downloading [Wireshark](https://www.wireshark.org/) and seeing if you're getting drowned in TCP transmission errors for non-Tor traffic. If yes, your ISP is who you need to talk to
 
-\-> If not, try using [obfs4 bridges](../bonus-guides/system/tor-services.md#add-obfs4-bridge-to-the-default-tor-instance) and see if that helps. Your ISP, the company's network, your country, etc, could be censoring completely your Tor access, use of obfs4 bridges could help to avoid this censorship
+-> If not, try using [obfs4 bridges](../bonus-guides/system/tor-services.md#add-obfs4-bridge-to-the-default-tor-instance) and see if that helps. Your ISP, the company's network, your country, etc, could be censoring completely your Tor access, use of obfs4 bridges could help to avoid this censorship
 {% endhint %}
 
 **Example** of Tor censorship output: