14 |
15 | This will restart MyNode and open the Clone Tool after rebooting. In this state, Bitcoin and other apps will not be running.
16 |
17 |
18 |
19 |
20 |
21 |
22 |
23 | Once open, the Clone Tool will wait for two drives to be attached. Two drives can require more power than small, embedded devices like Raspberry Pis can provide via USB, so it is recommended to attach both drives via a powered USB hub to ensure both drives have sufficient power.
24 |
25 |
26 |
27 |
28 |
29 |
30 |
31 | After attaching both drives, you will be promoted to confirm the clone process. You can also reboot to go back to normal MyNode operation or rescan the drives if something doesn't seem correct. If rebooting, detach the second drive first.
32 |
33 | **Be sure to verify the source and destination drives are correct!** After confirming, the destination drive will be erased and data from the source drive will be copied to it.
34 |
35 |
36 |
37 |
38 |
39 |
40 |
41 | After confirming, the clone process will begin! There are a several stages and it may take a few minutes to start seeing progress while it shows 0% complete.
42 |
43 |
44 |
45 |
46 |
47 |
48 |
49 | Once complete, you should see a success screen and can reboot the device back into normal operation! Disconnect the source/old drive before rebooting.
50 |
51 |
52 |
53 |
54 |
55 |
56 |
57 | **Note:** After using the new drive, be cautious about reverting to the old drive and using Lightning. Using old channel state can cause loss of funds.
--------------------------------------------------------------------------------
/docs/advanced/custom-app-versions.md:
--------------------------------------------------------------------------------
1 | # Customize App Versions
2 |
3 | In some situations, like in the case of contentious forks, you may want to use a specific application version and not upgrade to the one used by MyNode or upgrade to a new release prior to its inclusion in a MyNode release. If that were to happen, MyNode includes a tool to override the application version that is installed.
4 |
5 | ## Customizing an Application Version
6 |
7 | To start customizing an app version, first go to the settings page and click on the 'Customize Application Versions' button. A link it also available on the bottom of the Manage Apps page.
8 |
9 |
10 |
11 |
12 |
13 |
14 |
15 | This will open the application customization page which has a table of all applications.
16 |
17 |
18 |
19 |
20 |
21 |
22 |
23 | Each app row shows the current version (if installed) and the latest version. To customize the latest version, click the Customize button and text field will appear. You can then enter the custom version and click Save.
24 |
25 |
26 |
27 |
28 |
29 |
30 |
31 | Once saved, the application's Latest Version will be updated to the one you entered.
32 |
33 |
34 |
35 |
36 |
37 |
38 |
39 | After the custom app has been saved, the app still needs to be upgraded. To perform the upgrade, navigate to the Manage Apps page via the icon in the top left. Once on the Manage Apps page, you will see a pin icon next to the app you customized indicating it has a customized version.
40 |
41 |
42 |
43 |
44 |
45 |
46 |
47 | To upgrade the app, click the Upgrade button in the application row. Your device will begin upgrading the application before rebooting.
48 |
49 |
50 |
51 |
52 |
53 |
54 |
55 | After rebooting, you can go back to the Manage Apps page and verify the Current Version and Latest Version of the app match and both indicate the custom version you chose.
56 |
57 |
58 |
59 |
60 |
61 |
62 |
63 | Congratulations on running a custom application version!
64 |
--------------------------------------------------------------------------------
/docs/advanced/customize-config.md:
--------------------------------------------------------------------------------
1 | # Customizing Bitcoin and LND Config
2 |
3 | ## Customizing your Bitcoin Configuration
4 | MyNode generates much of the Bitcoin config automatically so it can easily communciate with other services on the device. However, you may want to tweak certain settings to control bandwidth, add specific peers, etc...
5 |
6 |
7 | To do this, you can edit the config via the Bitcoin page in the MyNode UI.
8 |
9 |
10 |
11 |
12 |
13 |
14 |
15 | Make any changes you like and click save once you are complete. Saving will reboot the device.
16 |
17 |
18 |
19 |
20 |
21 |
22 |
23 | Once a custom config is used, any future updates to the default config will not be applied. To reset
24 | and use the default config, you will need to reset the config via "Reset Config" button.
25 |
26 |
27 |
28 |
29 |
30 |
31 |
32 | Once the file has been saved or reset, the new settings will be applied to your bitcoin.conf
33 | file, even between reboots and upgrades!
34 |
35 | ## Customizing the your LND Configuration
36 |
37 | MyNode generates much of the LND config automatically so it can easily communciate with other services on the device. However, you may want to tweak certain settings to control bandwidth, peers, etc...
38 |
39 | To do this, you can edit the config via the Lightning page in the MyNode UI.
40 |
41 |
42 |
43 |
44 |
45 |
46 |
47 | Make any changes you like and click save once you are complete. Saving will reboot the device.
48 |
49 |
50 |
51 |
52 |
53 |
54 |
55 | Once a custom config is used, any future updates to the default config will not be applied. To reset and use the default config, you will need to reset the config via "Reset Config" button.
56 |
57 |
58 |
59 |
60 |
61 |
62 |
63 | Once the file has been saved or reset, the new settings will be applied to your lnd.conf file, even between reboots and upgrades!
--------------------------------------------------------------------------------
/docs/advanced/find-device-ip.md:
--------------------------------------------------------------------------------
1 | # Find your Device's IP Address
2 |
3 | In some scenarios, it can be useful to know your device's IP address. Here are several ways to find it.
4 |
5 | ## Option 1 - On the Status Page
6 |
7 | First, if you already have access to the web interface, you can navigate to the Status page and the local IP address of the device will be listed at the top, under the Info heading.
8 |
9 | ## Option 2 - Via your Router
10 |
11 | If you connect to your home router, normally via a web page or an app, there is typically a section on connected devices. Routers may vary, but the devices are typically listed by name and IP address. Look for a device with the name "MyNode" and find its IP address.
12 |
13 | ## Option 3 - Via a Network Scanner
14 |
15 | Applications like [Advanced IP Scanner](https://www.advanced-ip-scanner.com/) or [Angry IP Scanner](https://angryip.org/) can also scan your network and find devices and their IP addresses. Look for a device named "MyNode" and its IP address should be displayed.
16 |
17 | ## Option 4 - Via a Computer Monitor
18 |
19 | Finally, if you attach a monitor and keyboard to your device, you can find the IP address. After connecting the additional hardware, you should see a login prompt. Log in with the username "admin" and your MyNode password. After successful login, a banner should be displayed that includes the device IP address. Additionally, running the command "ip addr" will provide more network information.
20 |
21 |
--------------------------------------------------------------------------------
/docs/advanced/flash-sd-card.md:
--------------------------------------------------------------------------------
1 | # Flash MyNode OS Image
2 |
3 | For most types of devices, including the Raspberry Pi 4 and mini PCs, the first step in getting started is to download a MyNode image and flash it onto a USB flash drive or SD card. The the flash drive is then inserted into the device so it can run the MyNode software.
4 |
5 | This same process can be done to load new versions of software, reset your password if it was forgotten, or to swap to a new flash drive with larger storage capacity.
6 |
7 |
26 |
27 | ## Download the Software Image
28 |
29 | You will need to download the image for your device from [mynodebtc.com/download](https://mynodebtc.com/download).
30 |
31 |
32 |
33 |
34 |
35 |
36 |
37 | Once downloaded, the software needs to be written to the flash drive.
38 |
39 | ## Flash the OS Image
40 |
41 | To load software image on the USB drive or SD card, you will need to connect it to your computer. If you have an SD card, you will need a way to connect it to your computer. Some PCs and laptops have a slot to insert them, but most users will need a USB to micro SD adapter. They can be found on [Amazon](https://amzn.to/38OtQF4).
42 |
43 | Connect the flash drive to your computer.
44 |
45 | Then, download [Etcher](https://www.balena.io/etcher/), a program for writing software images, and install it on your PC or Mac.
46 |
47 | Open Etcher and click "Flash from file" and choose the recently downloaded image.
48 |
49 |
50 |
51 |
52 |
53 |
54 |
55 | After selecting the image, click "Select target".
56 |
57 |
58 |
59 |
60 |
61 |
62 |
63 | Choose the SD card or USB drive from the list and click "Select". Verify the size of the drive matches what you expect.
64 |
65 |
66 |
67 |
68 |
69 |
70 |
71 | Once selected, click "Flash!" and the image will be written to the drive. The flashing process may take 5-15 minutes.
72 |
73 |
74 |
75 |
76 |
77 |
78 |
79 | Once the image has been written to the flash drive, you can remove it from the PC.
80 |
81 |
82 |
83 |
84 |
85 |
86 |
87 |
88 | ## Insert Flash Drive into Device
89 |
90 | Finally, the last step is to take the flash drive and insert it into the unpowered device.
91 |
92 |
93 |
94 |
95 |
96 |
97 |
98 | Once, it has been inserted, reconnect the power cable and enjoy MyNode!
99 |
100 | For futher steps, try the [Getting Started](/intro/getting-started) guide.
101 |
--------------------------------------------------------------------------------
/docs/advanced/install-pc-server.md:
--------------------------------------------------------------------------------
1 | # Install on a PC or Server
2 |
3 | ## Background
4 |
5 | MyNode has been designed to protect your data by requiring two storage drives. One drive contains the operating system and applications and the other stores data, like the Bitcoin blockchain. This allows for easier data backup and enables simpler recovery.
6 |
7 | This guide suggests using a USB thumbdrive to boot the operating system and using an internal drive for data. In more advanced use cases, the MyNode image can be written to an internal drive as well using similar tools. Any existing data on the thumbdrive and data drive will be lost.
8 |
9 | **Required Hardware**
10 | - USB Thumbdrive (32GB+)
11 | - PC, Laptop or Server
12 |
13 | ## Download
14 |
15 | First, download the MyNode image for a PC or server (amd64) from [mynodebtc.com](http://mynodebtc.com/download) and save it. This should be done on a PC that is not intended to be used as the node.
16 |
17 | 
18 |
19 | ## Install MyNode
20 |
21 | Once the image has been downloaded, the image needs to be written to a drive that will be used to boot the PC or server intended to run MyNode. This can easily be done with a [USB thumbdrive](https://amzn.to/3AlIxco) and [Balena Etcher](https://www.balena.io/etcher/). If using a USB thumbdrive, make sure it is at least 32GB.
22 |
23 | Insert the USB drive into your PC. Open Etcher, click Select image and choose the downloaded image. Note, the downloaded image may need to be extracted first.
24 |
25 | Next, click Select target and select the USB drive, then click Flash! to write the image to the USB thumbdrive.
26 |
27 | 
28 |
29 | Once complete, you can remove from your PC once the image has been successfully written.
30 |
31 | ## Boot Device
32 |
33 | Now that the USB drive has been written, insert it into the PC or server to be used as your node and reboot the device. The device may need to have its BIOS settings updated to boot from the new device.
34 |
35 | 
36 |
37 | ## Running MyNode
38 |
39 | Once the PC or server has been powered on, you can access the MyNode interface by either accessing http://mynode.local via a device connected to the same network or via a monitor and keyboard connected to the device. You can login with the password `bolt`.
40 |
41 | 
--------------------------------------------------------------------------------
/docs/advanced/install-virtual-box.md:
--------------------------------------------------------------------------------
1 | # Install on Virtual Box
2 |
3 | ## Download
4 |
5 | 1. Download the virtual box manager for your operating system from [virtualbox.org](https://www.virtualbox.org/wiki/Downloads)
6 | 2. Download the virtualBox extension pack from the above website
7 | 3. Download the OVA file from [mynodebtc.com](http://mynodebtc.com/download) (3.2GB)
8 |
9 | ## Install the Virtual box manager
10 |
11 | 1. Double click the virtual box manager (.exe, .deb or .dmg file) and follow instructions to install it.
12 | 2. Double click the Extension Pack (.vbox-extpack) and follow instructions to install it
13 |
14 | **Note**: The extension pack and virtual box manager should have the same version. Please remove any old VM managers.
15 |
16 | ## Import the virtual image
17 |
18 | 1. Double click the mynode_vm_\.ova file to launch the Virtual box manager and launch the import window (as seen below).
19 |
20 | 
21 |
22 | 2. Leave the default settings and click on **Import**. Once it's imported, you should a screen like shown below
23 |
24 | 
25 |
26 | ## Launch the Virtual Box
27 |
28 | 1. By default the network settings uses the Wired connection. Change the network settings if you want to use wireless network.
29 | - Click on Settings wheel (or Ctrl+S)
30 | - Choose the Network tab
31 | - Enable Network Adapter should be checked
32 | - "Attached to" should be configured to Bridged Adapter
33 | - Change the name to appropriate network (eg. wireless network starts with wl)
34 | - Click on OK to close the settings window
35 |
36 | 
37 |
38 | 2. Double click on **MyNode** from the sidebar and let it open a new window, as shown below.
39 |
40 | 
41 |
42 | 3. Enter username as **admin** and password as **bolt**
43 | 4. Enter the password again in the Chromium window
--------------------------------------------------------------------------------
/docs/advanced/linux-terminal.md:
--------------------------------------------------------------------------------
1 | # Accessing the Linux Terminal
2 |
3 | For some issues, it can be necessary or helpful to run specific commands in Linux to diagnose or resolve issues. While this may seem complex, it is easier than you think!
4 |
5 |
6 | ## Using SSH
7 |
8 | The Linux Terminal can be accessed via SSH, which allows you to run an app or command on your PC to connect to Linux on your device.
9 |
10 | - Open a terminal on your Mac, Windows, or Linux computer
11 | - At the prompt, type `ssh admin@mynode.local` or replace mynode.local with the IP address of your device
12 | - at the password prompt, type your node's password and press enter (the password will be hidden)
13 | - Success! You are now connected to your node and can run shell commands
14 | - To exit, type `exit` and press enter
15 |
16 | Good instructions for SSH access are also available from Raspberry Pi's website. Start following this Guide at step #4.
17 |
18 | https://www.raspberrypi.org/documentation/remote-access/ssh/
19 |
20 | Once successfully connected, you should see a screen similar to this!
21 |
22 |
23 |
24 |
25 |
26 |
--------------------------------------------------------------------------------
/docs/advanced/netdata.md:
--------------------------------------------------------------------------------
1 | # Netdata
2 |
3 | ## Overview
4 |
5 | Netdata is distributed, real-time performance and health monitoring for systems and applications. It is a highly-optimized monitoring agent you install on all your systems and containers. It provides unparalleled insights, in real-time, of everything happening on the systems it's running on, using highly interactive web dashboards. A highly-efficient database stores long-term historical metrics for days, weeks, or months, all at 1-second granularity. It is fast and efficient, designed to permanently run on all systems (physical and virtual servers, containers, IoT devices), without disrupting their core function.
6 |
7 | To open the Netdata dashboard, scroll to the bottom of your MyNode homepage, and click on the **Settings** button.
8 |
9 | Next click on the `Open Netdata` button, as shown here:
10 |
11 | 
12 |
13 | Your Netdata dashboard will open in a new window, and will take a few seconds to fully populate with data.
14 | The images below show some of the comprehensive operating data that will be available to you.
15 |
16 | 
17 |
18 | 
19 |
20 | 
21 |
22 | 
23 |
24 | ## Specs
25 | - Github: [netdata/netdata](https://github.com/netdata/netdata)
26 | - Live demo: [london.my-netdata.io/](https://london.my-netdata.io/)
27 | - Ports: 19999/20000
28 |
--------------------------------------------------------------------------------
/docs/advanced/setup-base-images/setup_base_image_debian.md:
--------------------------------------------------------------------------------
1 | # Setup Base Image (Debian)
2 |
3 | 1. Setup Base OS
4 |
5 | Install Debian 10.1.0 Net-install via CD
6 |
7 | URL: [https://www.debian.org/CD/netinst/](https://www.debian.org/CD/netinst/)
8 |
9 | Follow instructions:
10 |
11 | - Graphical Install
12 | - English, US, American English
13 | - Hostname: MyNode
14 | - Domain Name:
15 | - Root Password: bolt
16 | - Full Name: MyNode
17 | - Username: mynode
18 | - Password: bolt
19 | - Timezone: Central
20 | - Partition: Guided Use Entire Disk, Continue, Continue, Continue, Yes
21 | - CDs and Packages: No, Next, Next
22 | - Software Selection: No GUI, No Print Server, Add SSH Server
23 | - Install Grub: Yes, /dev/sda
24 | - Install Complete: Continue
25 |
26 | 2. Login as root / bolt
27 |
28 | 3. Install basic Software
29 |
30 | ```sh
31 | apt-get -y install sudo
32 | useradd -p $(openssl passwd -1 bolt) -m -s /bin/bash admin
33 | adduser admin sudo
34 | ```
35 |
36 | 4. Delete mynode user
37 |
38 | ```sh
39 | deluser mynode
40 | rm -rf /home/mynode
41 | exit
42 | ```
43 |
44 | 5. Login as admin / bolt
45 |
46 | 6. Delete root password
47 |
48 | ```sh
49 | sudo passwd -d root
50 | ```
51 |
52 | 7. Update packages
53 |
54 | ```sh
55 | sudo apt-get -y update
56 | sudo apt-get -y upgrade
57 | ```
58 |
59 | 8. Install some basics
60 |
61 | ```sh
62 | sudo apt-get -y install tmux
63 | ```
64 |
65 | 9. Sync
66 |
67 | ```sh
68 | sync
69 | ```
70 |
71 | 10. Make image now (if imaging)
72 |
--------------------------------------------------------------------------------
/docs/advanced/setup-base-images/setup_base_image_other.md:
--------------------------------------------------------------------------------
1 | # Setup Base Image (Other)
2 |
3 | 1. Login as administrator
4 |
5 | 2. Set hostname
6 |
7 | ```sh
8 | hostname MyNode
9 | ```
10 |
11 | 3. Add admin user
12 |
13 | ```sh
14 | sudo useradd -p $(openssl passwd -1 bolt) -m -s /bin/bash admin
15 | sudo adduser admin sudo
16 | ```
17 |
18 | 4. Update OS
19 |
20 | ```sh
21 | sudo apt-get update
22 | sudo apt-get -y upgrade
23 | ```
24 |
25 | 5. Install some basics
26 |
27 | ```sh
28 | sudo apt-get -y install tmux
29 | ```
30 |
31 | 6. Reboot
32 |
33 | ```sh
34 | sudo reboot
35 | ```
36 |
37 | 7. Log back in as admin
38 |
39 | 8. Delete default users for your specific device (if any)
40 |
41 | ```sh
42 | # For example:
43 | # sudo deluser pi
44 | # sudo rm -rf /home/pi
45 | ```
46 |
47 | 9. Sync
48 |
49 | ```sh
50 | sync
51 | ```
52 |
53 | 10. Make image now (if imaging)
54 |
55 | Final results:
56 |
57 | - Image with SSH access
58 | - Root user disabled
59 | - Default user admin with password bolt
60 |
--------------------------------------------------------------------------------
/docs/advanced/setup-base-images/setup_base_image_raspi3.md:
--------------------------------------------------------------------------------
1 | # Setup Base Image (Raspberry Pi 3)
2 |
3 | 1. After Raspi Flash `touch` ssh file on rootfs
4 |
5 | 2. Login as pi / raspberry
6 |
7 | 3. Run `sudo raspi-config`
8 |
9 | - Update 8: Get latest configuration tool
10 | - Network Options 2: Hostname -> MyNode
11 | - Boot Options 3: Choose Desktop / CLI -> Console
12 | - Boot Options 3: Wait for Network at Boot
13 | - Localisation 4: I2 -> US -> Central
14 | - Localisation 4: I4 -> US
15 | - Advanced 7: Expand Filesystem
16 | - Advanced 7: Memory Split -> 16
17 | - Exit by selecting ``, and `` as no reboot is necessary
18 |
19 | 4. Add admin user
20 |
21 | ```sh
22 | sudo useradd -p $(openssl passwd -1 bolt) -m -s /bin/bash admin
23 | sudo adduser admin sudo
24 | ```
25 |
26 | 5. Update OS
27 |
28 | ```sh
29 | sudo apt-get update
30 | sudo apt-get -y upgrade
31 | ```
32 |
33 | 6. Install some basics
34 |
35 | ```sh
36 | sudo apt-get -y install tmux
37 | ```
38 |
39 | 7. Reboot
40 |
41 | ```sh
42 | sudo reboot
43 | ```
44 |
45 | 8. Log back in as admin
46 |
47 | 9. Delete pi user
48 |
49 | ```sh
50 | sudo deluser pi
51 | sudo rm -rf /home/pi
52 | ```
53 |
54 | 10. Install Log2Ram (Armbian has own solution)
55 |
56 | ```sh
57 | cd /tmp
58 | wget https://github.com/azlux/log2ram/archive/v1.2.2.tar.gz -O log2ram.tar.gz
59 | tar -xvf log2ram.tar.gz
60 | mv log2ram-* log2ram
61 | cd log2ram
62 | chmod +x install.sh
63 | sudo ./install.sh
64 | cd ~
65 | ```
66 |
67 | 11. Sync
68 |
69 | ```sh
70 | sync
71 | ```
72 |
73 | 12. Make image now (if imaging)
74 |
75 | Final results:
76 |
77 | - Image with SSH access
78 | - Root user disabled
79 | - Default user admin with password bolt
80 |
--------------------------------------------------------------------------------
/docs/advanced/setup-base-images/setup_base_image_raspi4.md:
--------------------------------------------------------------------------------
1 | # Setup Base Image (Raspberry Pi 4)
2 |
3 | 1. After Raspi Flash `touch` ssh file on rootfs
4 |
5 | 2. Login as pi / raspberry
6 |
7 | 3. Run `sudo raspi-config`
8 |
9 | - Update 8: Get latest configuration tool
10 | - Network Options 2: Hostname -> MyNode
11 | - Boot Options 3: Choose Desktop / CLI -> Console
12 | - Boot Options 3: Wait for Network at Boot
13 | - Localisation 4: I2 -> US -> Central
14 | - Localisation 4: I4 -> US
15 | - Advanced 7: Expand Filesystem
16 | - Advanced 7: Memory Split -> 16
17 | - Exit by selecting ``, and `` as no reboot is necessary
18 |
19 | 4. Add admin user
20 |
21 | ```sh
22 | sudo useradd -p $(openssl passwd -1 bolt) -m -s /bin/bash admin
23 | sudo adduser admin sudo
24 | ```
25 |
26 | 5. Update OS
27 |
28 | ```sh
29 | sudo apt-get update
30 | sudo apt-get -y upgrade
31 | ```
32 |
33 | 6. Install some basics
34 |
35 | ```sh
36 | sudo apt-get -y install tmux
37 | ```
38 |
39 | 7. Reboot
40 |
41 | ```sh
42 | sudo reboot
43 | ```
44 |
45 | 8. Log back in as admin
46 |
47 | 9. Delete pi user
48 |
49 | ```sh
50 | sudo deluser pi
51 | sudo rm -rf /home/pi
52 | ```
53 |
54 | 10. Install Log2Ram (Armbian has own solution)
55 |
56 | ```sh
57 | cd /tmp
58 | wget https://github.com/azlux/log2ram/archive/v1.2.2.tar.gz -O log2ram.tar.gz
59 | tar -xvf log2ram.tar.gz
60 | mv log2ram-* log2ram
61 | cd log2ram
62 | chmod +x install.sh
63 | sudo ./install.sh
64 | cd ~
65 | ```
66 |
67 | 11. Sync
68 |
69 | ```sh
70 | sync
71 | ```
72 |
73 | 12. Make image now (if imaging)
74 |
75 | Final results:
76 |
77 | - Image with SSH access
78 | - Root user disabled
79 | - Default user admin with password bolt
80 |
--------------------------------------------------------------------------------
/docs/advanced/setup-base-images/setup_base_image_rock64.md:
--------------------------------------------------------------------------------
1 | # Setup Base Image (ROCK64)
2 |
3 | 1. After Armbian Flash
4 |
5 | - Login with root / 1234
6 | - Change root password to something longish like boltbolt
7 | - Create admin user with password bolt
8 |
9 | 2. Login as admin
10 |
11 | 3. Delete root password
12 |
13 | ```sh
14 | sudo passwd -d root
15 | ```
16 |
17 | 4. Set hostname
18 |
19 | ```sh
20 | echo "MyNode" | sudo tee /etc/hostname
21 | sudo sed -i 's/rock64/MyNode/g' /etc/hosts
22 | # OR armbian-config -> Personal -> Hostname
23 | ```
24 |
25 | 5. Overclock
26 |
27 | ```sh
28 | sudo sed -i "s/MAX_SPEED=.*/MAX_SPEED=1510000/" /etc/default/cpufrequtils
29 | sudo systemctl restart cpufrequtils
30 | ```
31 |
32 | 6. Update packages
33 |
34 | ```sh
35 | sudo apt-get update
36 | sudo apt-get -y upgrade
37 | ```
38 |
39 | 7. Install some necessary tools
40 |
41 | ```sh
42 | sudo apt-get -y install network-manager tmux
43 | ```
44 |
45 | 8. Regenerate MAC Address for Rock64
46 |
47 | ```sh
48 | . /usr/lib/armbian/armbian-common
49 | CONNECTION="$(nmcli -f UUID,ACTIVE,DEVICE,TYPE connection show --active | tail -n1)"
50 | UUID=$(awk -F" " '/ethernet/ {print $1}' <<< "${CONNECTION}")
51 | get_random_mac
52 | nmcli connection modify $UUID ethernet.cloned-mac-address $MACADDR
53 | nmcli connection modify $UUID -ethernet.mac-address ""
54 | ```
55 |
56 | 9. Sync
57 |
58 | ```sh
59 | sync
60 | ```
61 |
62 | 10. Make image now (if imaging)
63 |
--------------------------------------------------------------------------------
/docs/advanced/setup-base-images/setup_base_image_rockpro64.md:
--------------------------------------------------------------------------------
1 | # Setup Base Image (ROCKPro64)
2 |
3 | 1. After Armbian Flash
4 |
5 | - Login with root / 1234
6 | - Change root password to something longish like boltbolt
7 | - Create admin user with password bolt
8 |
9 | 2. Login as admin
10 |
11 | 3. Delete root password
12 |
13 | ```sh
14 | sudo passwd -d root
15 | ```
16 |
17 | 4. Set hostname
18 |
19 | ```sh
20 | echo "MyNode" | sudo tee /etc/hostname
21 | sudo sed -i 's/rock64/MyNode/g' /etc/hosts
22 | # OR armbian-config -> Personal -> Hostname
23 | ```
24 |
25 | 5. Update packages
26 |
27 | ```sh
28 | sudo apt-get update
29 | sudo apt-get -y upgrade
30 | ```
31 |
32 | 6. Install some necessary tools
33 |
34 | ```sh
35 | sudo apt-get -y install network-manager tmux
36 | ```
37 |
38 | 7. Regenerate MAC Address for RockPro64
39 |
40 | ```sh
41 | . /usr/lib/armbian/armbian-common
42 | CONNECTION="$(nmcli -f UUID,ACTIVE,DEVICE,TYPE connection show --active | tail -n1)"
43 | UUID=$(awk -F" " '/ethernet/ {print $1}' <<< "${CONNECTION}")
44 | get_random_mac
45 | nmcli connection modify $UUID ethernet.cloned-mac-address $MACADDR
46 | nmcli connection modify $UUID -ethernet.mac-address ""
47 | ```
48 |
49 | 8. Sync
50 |
51 | ```sh
52 | sync
53 | ```
54 |
55 | 9. Make image now (if imaging)
56 |
--------------------------------------------------------------------------------
/docs/advanced/upgrade-to-beta.md:
--------------------------------------------------------------------------------
1 | # Upgrade to a Beta Release
2 |
3 | ## Beta Releases
4 |
5 | MyNode releases frequent updates, but from time to time, beta updates are available to allow users to test out specific fixes, applications, or try early versions of large updates.
6 |
7 | Updating to a beta release is simple and can be done with a couple button clicks.
8 |
9 | Premium Feature
10 |
11 | ## Steps to Upgrade
12 |
13 | First, navtigate to the settings page and scroll down towards the bottom to the Developer section. Within that section, find the subsection titled "Install Beta" and click on "Check for Updates" - this will check to see if any new beta upgrades are available. Checking for new versions may take a minute.
14 |
15 | 
16 |
17 | After checking for updates, if a beta is available, it will be shown as the Latest Beta Version and an "Install Beta" button will be displayed.
18 |
19 | 
20 |
21 | To upgrade to the beta, click the "Install Beta" button. The device will upgrade just as it does for typical new releases.
22 |
23 | 
24 |
25 | After upgrading, new versions will appear as they normally do and it is recommended to upgrade to a new release once available.
26 |
27 | Enjoy!
28 |
--------------------------------------------------------------------------------
/docs/advanced/verify-restore-bluewallet.md:
--------------------------------------------------------------------------------
1 | # Verify or Restore on-chain Lightning funds using BlueWallet
2 |
3 |
4 |
5 | ## Cautionary note
6 |
7 | Use this method to monitor the on-chain wallet, verify the seed or recover the on-chain funds in case of emergency. **DO NOT** use the wallet to make transactions while your lightning node is running. It may disrupt your node.
8 |
9 |
10 |
11 | ## Step 1: Install Bluewallet
12 |
13 | You can install Blue wallet on any of the following operating systems:
14 | - iOS
15 | - MacOS
16 | - Android
17 |
18 | Use their website [bluewallet.io](https://bluewallet.io/) to find links for the above.
19 |
20 | ## Step 2: Add new wallet
21 |
22 | Once the Bluewallet is installed, launch it and find the "Add a wallet" page, like the image shown below. Click on it.
23 |
24 |
57 |
58 | ## Step 5: View transactions
59 |
60 | A violet color wallet should appear called "Imported HD Aezeed". Click on it to view transactions. It may take a few minutes to load all transactions.
61 |
62 |
63 |
64 |
65 |
66 |
67 |
68 | 
69 |
70 | **Note**: Bluewallet only scans the first 20 addresses whereas MyNode generates a new address on every reboot, so total funds may appear to be different.
--------------------------------------------------------------------------------
/docs/bitcoin/bitcoin-status.md:
--------------------------------------------------------------------------------
1 | # Viewing Bitcoin Status
2 |
3 | Bitcoin runs automatically when your MyNode device starts. It's often be helpful to view the status of `bitcoind`, the Bitcoin daemon. Several key pieces of information are displayed on the home page.
4 |
5 | Click on the "Manage" button under Bitcoin on the home page to view the even more bitcoin information.
6 |
7 |
8 |
9 |
10 |
11 |
12 |
13 | On the Bitcoin page, you can see the current state of the Bitcoin daemon which includes recent blocks, peers, version, mempool information, and more!
14 |
15 |
16 |
17 |
18 |
19 |
20 |
--------------------------------------------------------------------------------
/docs/bitcoin/data-from-other-node.md:
--------------------------------------------------------------------------------
1 | # Using Bitcoin Data from Other Node
2 | In some cases, you may want to use Bitcoin data from a different node to get MyNode up and running faster or to save bandwidth. If you have another node that is already synced, you can copy that data to your MyNode.
3 |
4 | ## Step 1 - Start MyNode
5 |
6 | The first thing you need to do is start your MyNode and disable QuickSync. To disable QuickSync, go to the settings page and click the "Disable QuickSync" button.
7 |
8 | This will reboot your device and start syncing Bitcoin from scratch.
9 |
10 | ## Step 2 - Upload your own Data
11 |
12 | Next, you need to log into your device via SSH and copy files from your existing node.
13 |
14 | On the node with the source data, ensure the bitcoin block data is readable by the "admin" user or the user you are logging in with. Also, make sure that Bitcoin is not running. Run the following commands on each device.
15 |
16 | **On source node:**
17 | Steps may differ if source is not MyNode device
18 | ```sh
19 | # Stop Bitcoin and other services
20 | sudo /usr/bin/mynode_stop_critical_services.sh
21 |
22 | # Make sure block data is readable by the admin user
23 | sudo chmod -R 755 /mnt/hdd/mynode/bitcoin/blocks
24 | sudo chmod -R 755 /mnt/hdd/mynode/bitcoin/chainstate
25 | sudo chmod -R 755 /mnt/hdd/mynode/bitcoin/indexes
26 | ```
27 |
28 | **On destination node:**
29 | ```sh
30 | # Stop Bitcoin and other services
31 | sudo /usr/bin/mynode_stop_critical_services.sh
32 |
33 | # Make sure old data is removed
34 | sudo rm -rf /mnt/hdd/mynode/bitcoin/blocks
35 | sudo rm -rf /mnt/hdd/mynode/bitcoin/chainstate
36 | sudo rm -rf /mnt/hdd/mynode/bitcoin/indexes
37 |
38 | # Copy the blocks and chainstate folders from your existing node to /mnt/hdd/mynode/bitcoin/
39 | # For example (fill in with your own IP and path):
40 | sudo rsync -aP admin@othernode.local:/mnt/hdd/mynode/bitcoin/blocks /mnt/hdd/mynode/bitcoin/
41 | sudo rsync -aP admin@othernode.local:/mnt/hdd/mynode/bitcoin/chainstate /mnt/hdd/mynode/bitcoin/
42 | sudo rsync -aP admin@othernode.local:/mnt/hdd/mynode/bitcoin/indexes /mnt/hdd/mynode/bitcoin/
43 | sudo chown -R bitcoin:bitcoin /mnt/hdd/mynode/bitcoin/
44 | sudo reboot
45 | ```
46 |
47 | This will copy files from your remote node to your local node. After rebooting, your device will sync from the same state as your other node.
48 |
--------------------------------------------------------------------------------
/docs/bitcoin/explorer.md:
--------------------------------------------------------------------------------
1 | # BTC RPC Explorer
2 |
3 | ## Overview
4 | BTC RPC Exploter is a self-hosted explorer for the Bitcoin blockchain, driven by RPC calls to your own Bitcoin node. It is easy to run and can be connected to other tools (like Electrum servers) to achieve a full-featured explorer.
5 |
6 | Whatever reasons you may have for running a full node (trustlessness, technical curiosity, supporting the network, etc) it's valuable to appreciate the fullness of your node. With this explorer, you can explore not just the blockchain database, but also explore all of the functional capabilities of your own node.
7 |
8 | ## Links
9 | - Github: [https://github.com/janoside/btc-rpc-explorer](https://github.com/janoside/btc-rpc-explorer)
10 |
--------------------------------------------------------------------------------
/docs/bitcoin/ibd.md:
--------------------------------------------------------------------------------
1 | # Initial blockchain download (IBD)
2 |
3 | ideas:
4 | - what is it?
5 | - what is QuickSync
6 | - How to disable it and perform IBD from scratch
7 | - expected waiting time with different drive and network configuration and how to boost it?
8 | - link to dedicated QuickSync page
9 | - explain the purpose, effects and waiting time of reset / rescan / reindex blockchain (need help from experienced users)
10 |
11 | ## Overview
12 |
13 | Syncronizing the full Bitcoin blockchain can take a long time on certain devices. By default, MyNode will use *QuickSync* to download a pre-validated portion of the blockchain to greatly reduce the initial sync time. However MyNode also allows you to fully validate the blockchain yourself.
14 |
15 | ## Disable QuickSync
16 |
17 | To fully synchronize the blockchain, first disable QuickSync. Go to the settings page and click on the "Disable QuickSync" button.
18 |
19 |
20 |
21 |
22 |
23 |
24 |
25 | ## Reset Bitcoin Blockchain
26 |
27 | After disabling QuickSync, you may need to reset the blockchain. If your MyNode was already up and running, you will need to reset the blockchain as well. If your device was still performing QuickSync, you will not need to perform the following step.
28 |
29 | Next, reset the Blockchain via the settings page.
30 |
31 |
32 |
33 |
34 |
35 |
36 |
37 | Once the device reboots, it will begin syncronizing the Bitcoin blockchain from scratch.
38 |
--------------------------------------------------------------------------------
/docs/bitcoin/manage.md:
--------------------------------------------------------------------------------
1 | # Managing Bitcoin
2 |
3 | Bitcoin runs automatically when MyNode starts. By clicking on the "Manage" button under Bitcoin on the home page, you can view the current state of the Bitcoin blockchain and your node, and interact with your node. You can also reach the page by pointing to **\/bitcoind**
4 |
5 |
6 |
7 |
8 |
9 | On the Bitcoin page, you can see the current state of Bitcoin. There are several information tiles on this page which are explained below.
10 |
11 | 
12 |
13 | | Tile | Description |
14 | | :-- | -- |
15 | | Blocks | number of blocks downloaded and verified from network |
16 | | Header | number of block headers obtained from the network. It signals the state of the longest chain. |
17 | | Difficulty | the current mining difficulty which adjusts with the competition in mining world |
18 | | Disk usage | memory occupied by the blockchain on external HDD/SSD |
19 | | Version | the installed version of Bitcoin Core |
20 | | Mempool TX | number of transactions waiting in the mempool to be added to the blockchain by miners |
21 | | Mempool Size | the memory occupied by the waiting transactions |
22 | | RPC Username | the username for accessing RPC (the default is mynode) |
23 | | RPC Password | the password for accessing RPC. It is randomly generated during the setup and is revealed on clicking the Show button. WARNING: Handle RPC password with utmost care!! |
24 | | Bitcoin config | access the configuration settings of Bitcoin daemon |
25 | | Bitcoin CLI | access the web terminal to use bitcoin-cli commands |
26 | | Local Bitcoin address/port | the address and port number to access Bitcoin daemon from inside or outside the network. By default, Bitcoin daemon interacts with other bitcoin nodes through Tor network and thus have long cryptic onion address. The user doesn't have to open or forward the port in their network router to make it visible to other Bitcoin nodes. |
27 | | List of recent blocks | A list of 5 recent blocks added to the local copy of the blockchain. The age of the blocks may not be separated by intervals of 10 minutes since it fluctuates around 1-30 minutes. Number of transactions and size of the block indicate the supply/demand for block-space. |
28 | | List of peers | The onion/IP address of connected bitcoin nodes and few details about the connection. It might include few local peers (starting with 127.0.0.1) from other apps on MyNode. |
29 |
30 | ## Managing blockchain data
31 |
32 | To make more advanced changes, like resetting the blockchain, there are few more options available on the settings page. Since these options are generally required after encountering an issue, they are explained in the [troubleshooting](/bitcoin/troubleshoot) page.
33 |
34 | 
35 |
--------------------------------------------------------------------------------
/docs/bitcoin/mempool.md:
--------------------------------------------------------------------------------
1 | # Mempool
2 |
3 | ## Overview
4 | Bitcoin users broadcast their transactions via a node. Miners take these transactions, verify them and add them to the blockchain for the coinbase reward. Since the blocksize is limited, if there are more transactions waiting to be verified than can fit in a single block, they must wait in a buffer space. This buffer space is called the **mempool**. The size of the mempool indicates the demand for space on the bitcoin blockchain and directly affects the fees required to confirm transactions.
5 |
6 | Mempool is a visualization software for the bitcoin mempool. It decomposes the mempool based on transaction fees which helps in deciding fees. It also acts as an explorer for transactions and public addresses.
7 |
8 | ## Initialization
9 | Mempool can be enabled from the homepage and runs on port number 4080/4081. Initially, it takes a few minutes to load first few blocks and the graph for the most recent 2 hours of activity.
10 |
11 | ## Memory Usage
12 | The Bitcoin mempool can grow quite large which can lead to a lot of RAM usage. To mitigate any issues, MyNode does limit the total Bitcoin mempool size to be a few hundred MB.
13 |
14 | ## Links
15 | - Website: [https://mempool.space](https://mempool.space)
16 | - Github: [https://github.com/mempool/mempool](https://github.com/mempool/mempool)
17 |
--------------------------------------------------------------------------------
/docs/bitcoin/overview.md:
--------------------------------------------------------------------------------
1 | # Overview
2 |
3 | ## What is Bitcoin?
4 | MyNode's primary purpose is to run a full Bitcoin full node. Bitcoin is a revolutionary protocol to transact value between two parties without a trusted intermediary.
5 |
6 | ## What is a full-node?
7 | A full node verifies every block mined by miners and relayed by its peers before adding it to the chain. It also broadcasts transactions of users to be mined and maintains a pool of pending transactions.
8 |
9 | ## Benefits
10 | - **Trustless:** Have a personal copy of the entire verified transaction history
11 | - **Privacy:** Check your balance and transactions without leaking any information
12 | - **Censorship resistance:** It also enables broadcasting of transactions without fear of censorship.
13 | - **Network resilience:** independently validate blocks to increase security and resilience
14 |
15 |
16 | ## Features
17 | - **Private by default**: Hide your IP behind Tor
18 | - **CLI on GUI**: Use bitcoin-cli commands from your browser
19 | - **Flexible**: Customize configuration and connect any apps via RPC
20 |
21 |
22 |
23 |
24 | ## Hardware Limitations
25 | - The number of CPU cores used by MyNode is fixed at the number of available cores minus 1 to limit CPU usage.
26 | - On devices with little RAM, Bitcoin will limit RAM usage to prevent low memory issues
27 |
28 | ## Specs
29 | - **Version:** 0.21.1
30 | - **Memory required:** 335 GB (as of Aug 23, 2020)
31 | - **Data location:** `/mnt/mynode/bitcoin` which is also linked at `/home/bitcoin/.bitcoin`
32 |
33 |
34 |
35 |
36 |
37 |
38 |
39 |
48 |
50 |
--------------------------------------------------------------------------------
/docs/bitcoin/quicksync.md:
--------------------------------------------------------------------------------
1 | # QuickSync
2 |
3 | > **Warning**
4 | > QuickSync is now disabled by default and no longer recommended. The blockchain has gotten too large for QuickSync to be feasible on most devices.
5 |
6 | ## Overview
7 | QuickSync downloads a torrent for a major chunk of the blockchain from MyNode peers without verifying every block.
8 | It saves time by avoiding the initial blockchain download and this time benefit is significant when using an HDD but marginal with a SSD.
9 |
10 | QuickSync is turned on by default for HDDs and must be disabled from the settings page while setting up to trigger fully-verified blockchain download. For SSDs, QuickSync is disabled by default as long as the SSD is detected as the corret type.
11 |
12 | If you have an SSD and QuickSync starts, it is highly recommended to disable it.
13 |
14 | ## Tradeoffs
15 |
16 | - **Trust vs Time**: QuickSync downloads a torrent of the Bitcoin blockchain synced by the MyNode creator. This chunk of the blockchain saves the time in downloading verifying the blockchain from scratch. This convenience has a cost. The user is trusting that MyNode is propagating a legitimate copy of the Bitcoin blockchain. To minimize trust, one should disable QuickSync and download the blockchain from scratch. In case you have already synced the blockchain using QuickSync, you can [reset the blockchain](/bitcoin/troubleshoot.html#reset-blockchain).
17 |
18 | - **Memory vs Community support**: QuickSync downloads a compressed form of the blockchain. This compressed file is not deleted after its expanded form is used for boosting the Bitcoin sync process. Instead, this file is seeds torrent for the other MyNode users to improve their download speed. The compressed file uses around 236 GB. To save this space, you can disable QuickSync.
19 |
20 |
21 |
22 | ## Enable/Disable
23 |
24 | Once the blockchain is synced with the network, enabling QuickSync won't affect the Bitcoin blockchain. Instead, it will just download the torrent and start seeding it. This helps MyNode peers in downloading the blockchain faster during setup. The upload and download speed can be adjusted to optimize bandwidth usage, as shown in the screenshot below.
25 |
26 | **Note:** Toggling QuickSync triggers a reboot.
27 |
28 | ### Enable QuickSync
29 |
30 | 
31 |
32 | ### Disable QuickSync
33 |
34 | 
35 |
--------------------------------------------------------------------------------
/docs/bitcoin/troubleshoot.md:
--------------------------------------------------------------------------------
1 | # Troubleshooting Bitcoin
2 |
3 | ## Available options
4 | Bitcoin can run into various kinds of issues. Although MyNode aims to automatically detect these issues and fix them without user intervention, users might have to intervene. Based on the severity of the issues, there are many options available to fix common issues. Those solutions are listed below in increasing order of cost of convenience.
5 | - Reboot MyNode
6 | - Reinstall Bitcoin
7 | - Rescan blockchain
8 | - Reindex blockchain
9 | - Reset blockchain
10 | - Factory reset
11 |
12 | ## Reboot MyNode
13 |
14 | MyNode can be rebooted from the settings page with the button under Device (as shown below). Rebooting mynode is the easiest way to fix common issues.
15 |
16 | 
17 |
18 | ## Reinstall Bitcoin
19 |
20 | One can reinstall Bitcoin from the settings page with the dropdown tool under Advanced (as shown below). This maybe necessary when Bitcoin installation failed during an update.
21 |
22 | 
23 |
24 | ## Rescan blockchain
25 |
26 | This option is available on the settings page under Bitcoin (as shown below). It facilitates running `bitcoind` with the `-rescan` option. It scans the blockchain for missing transactions of the connected wallet.
27 |
28 | 
29 |
30 | ## Reindex blockchain
31 |
32 | This option is available on the settings page under Bitcoin (as shown above). It facilitates running `bitcoind` with the `-reindex-chainstate` option. To use the full `reindex` option, one has to use the command-line.
33 |
34 | Reindexing the blockchain becomes necessary when the blockchain data on HDD/SSD is corrupted, either due to disk failure or power cutoff. This is a time-consuming process and can take several hours.
35 |
36 | ## Reset blockchain
37 |
38 | This option is available on the settings page under Bitcoin (as shown above).
39 | Resetting the blockchain will delete the existing blockchain and will either download it from scratch or use the QuickSync data to get a head start. This is a time-consuming process and can take many days based on the hardware and network configuration.
40 |
41 | ## Factory reset
42 |
43 | This option is available in the Advanced section of settings page. This should be the last resort when all the options listed available has been tried. One should backup their wallet seed and channels before doing so.
44 |
45 | 
46 |
--------------------------------------------------------------------------------
/docs/btcpay-server/setup.md:
--------------------------------------------------------------------------------
1 | # BTCPay Server
2 |
3 | ## Enable and open the app
4 |
5 | - Enable the app and wait for the page to reload
6 | - Open the app from the homepage or go to [mynode.local:49393](https://mynode.local:49393), accept the risks of self-signed certificate. (Wait for few minutes if the homepage doesn’t show up.)
7 |
8 |
9 |
10 |
11 |
12 |
13 | ## Create an admin account
14 |
15 | - Create an account using your email and password. First account has admin privileges by default.
16 |
17 | 
18 |
19 | ## Create a Store
20 |
21 | 
22 |
23 | - Go to "Stores" page from the menu-bar on the top, and create a new store
24 | - Give your store a name, hit "Create"
25 | - Setup a BTC and/or lightning wallet
26 | - For BTC wallet: either import an existing wallet or create a new wallet
27 | - For this example, we’ll create a hot wallet with default settings
28 | - Backup the seed phrase, check the box and complete the process
29 |
30 | ## Create an App
31 |
32 | 
33 |
34 | - Go to the "Apps" page
35 | - Create a new app
36 | - Let the app type be "Point of Sale", give a name to your app
37 | - The BTC Pay server populates it with a default set of items, edit/delete them if you like
38 |
39 | ## Configure the router to forward ports
40 |
41 | 
42 |
43 | - Using the admin page of your router, forward the external port 443 to the internal port 49393 and the IP of your MyNode (10.0.0.19 in this example)
44 | - Verify the setting by opening the public IP your router in a browser. It should open the homepage of your BTCPay server.
45 |
46 | ## Buy a custom domain and connect it to your BTCPay server
47 |
48 | - [Godaddy](https://www.godaddy.com/) is a popular registrar
49 | - For example you bought "awesome.com"
50 | - Find the DNS Records page and add an entry
51 | - Choose "A" type
52 | - Enter the name of the subdomain, eg. store
53 | - Enter your public IP address as the value
54 | - Wait for the default TTL value
55 | - Browse to "https://store.awesome.com", it should open the homepage or login page of your BTCPay server
56 | - To open the Point of Sale app, go to Apps page and click on "View" button. You should see the default shop as seen below.
57 |
58 | 
59 |
60 | ## References
61 | - [Official guide](https://docs.btcpayserver.org/Deployment/ChangeDomain/#setting-up-your-dns-record)
--------------------------------------------------------------------------------
/docs/coinjoin/joinmarket.md:
--------------------------------------------------------------------------------
1 | # JoinMarket
2 |
3 | ## Overview
4 |
5 | JoinMarket is software to create a special kind of bitcoin transaction called a ["CoinJoin"](https://en.bitcoin.it/wiki/CoinJoin). Its aim is to improve the confidentiality and privacy of bitcoin transactions. JoinMarket differs from other popular CoinJoin implementations in a few ways.
6 |
7 | The most important differences are:
8 |
9 | 1. **Open**: Users can choose to act as a market "taker" and initiate a CoinJoin transaction on demand, or they can act as a market "maker" (and potentially earn fees) by leaving a JoinMarket wallet connected to the network for others to CoinJoin with.
10 | 2. **Decentralized**: JoinMarket has no central coordinator.
11 |
12 | JoinMarket was created by Chris Belcher in 2015, and is currently maintained by Adam Gibson [here.](https://github.com/Joinmarket-Org/joinmarket-clientserver)
13 | For a quick introduction to Joinmarket you can watch [this demonstration](https://youtu.be/hwmvZVQ4C4M) of installation and usage given by Adam Gibson during the [Understanding Bitcoin conference](https://understandingbtc.com/) on April 6 2019.
14 |
15 | ## General Usage
16 |
17 | Joinmarket is installed in MyNode and must be run via the command line. There are several Joinmarket scripts and configurations that can be utilized for various purposes, and it is important to fully understand the proper usage of each of them. Users are strongly urged to first read this [usage guide](https://github.com/JoinMarket-Org/joinmarket-clientserver/blob/master/docs/USAGE.md).
18 |
19 | To get a MyNode command line window you will need to open an SSH session from another computer.
20 |
21 | Instructions for doing that while on the same network as your MyNode can be found [here](https://mynodebtc.com/guide/debug_access_linux_terminal).
22 |
23 | There are two ways to run JoinMarket - by using JoinMarket scripts directly or by using a minimal terminal interface provided by JoinInBox.
24 |
25 | ## Usage - JoinInBox
26 |
27 | Once you have opened a terminal window in your MyNode, there is a convenient script for setting up and running JoinMarket.
28 |
29 | `sudo mynode-joininbox`
30 |
31 | You will be prompted for your password and should now see this in your terminal window:
32 |
33 | 
34 |
35 | You should now have access to JoinMarket through the interface provided by JoinInBox.
36 |
37 | * Github: [openoms/joininbox](https://github.com/openoms/joininbox)
38 |
39 | ## Usage - JoinMarket
40 |
41 | Once you have opened a terminal window in your MyNode, there is a convenient script for setting up and running JoinMarket.
42 |
43 | `sudo mynode-joinmarket`
44 |
45 | You will be prompted for your password and should now see this in your terminal window:
46 |
47 | 
48 |
49 | You are now ready to run any of the Joinmarket scripts, located at:
50 |
51 | `/home/joinmarket/joinmarket-clientserver/scripts`
52 |
53 | You can find the main configuration file, `joinmarket.cfg` at:
54 |
55 | `/home/joinmarket/.joinmarket`
56 |
57 | To exit, simply type and enter `exit`.
58 |
59 | **TIP**: If you are planning to use JoinMarket as a "maker", you will need to leave your maker script running for an extended period of time. This would normally require you to leave an open SSH session to your MyNode to keep your JoinMarket session running. This is impractical at best, and potentially unsecure if others might have access to your computer.
60 |
61 | A better way is to run your JoinMarket maker script inside of a [TMUX](https://github.com/tmux/tmux/wiki) window. You can start TMUX (after connecting to MyNode via SSH) by entering:
62 |
63 | `tmux`
64 |
65 | Next, you start the JoinMarket virtual environment as described earlier, and then your desired maker script.
66 |
67 | This will allow you to end your SSH session with your MyNode while leaving your JoinMarket maker/offer actively running.
68 | Without using TMUX, if you exit your SSH connection to your MyNode, any JoinMarket script that you have running will stop.
69 |
70 | * Github: [joinmarket/joinmarketclientserver](https://github.com/joinmarket/joinmarket-clientserver)
71 |
72 | ## Specs
73 |
74 | * Installed location: `/home/joinmarket/joinmarket-clientserver/`
75 | * IRC: [webchat.freenode.net](https://webchat.freenode.net) #joinmarket
76 |
--------------------------------------------------------------------------------
/docs/coinjoin/whirlpool.md:
--------------------------------------------------------------------------------
1 | # Whirlpool
2 |
--------------------------------------------------------------------------------
/docs/community/guides.md:
--------------------------------------------------------------------------------
1 | # Community Guides
2 | A number of written guides have been created by the amazing MyNode community detailing everything from how to get started to the details and setup of various features.
3 |
4 | ## Setup and Basics
5 | MyNode Bitcoin Node Easy Setup Guide (Raspberry Pi) by Arman the Parman
6 |
7 | ## Tor
8 | All The Reasons You’ve Failed To Connect Electrum to Your Node Via Tor by Arman the Parman
9 |
--------------------------------------------------------------------------------
/docs/developer/custom-scripts.md:
--------------------------------------------------------------------------------
1 | # Customizing MyNode with Scripts
2 |
3 | Developers or advanced users may want to run custom scripts at certain points in time to customize their expecience. This is facilitated through "hook" bash scripts. A user who puts a script in specific location will have it executed automatically by MyNode at the proper time.
4 |
5 | ## Adding a Hook Script
6 |
7 | The hook scripts can be placed at the desired location by adding the file through the Linux terminal. For example, you can use `nano` to create a script like this:
8 |
9 | Open Editor:
10 |
11 | `sudo nano /usr/local/bin/mynode_hook_pre_startup.sh`
12 |
13 | Contents:
14 | ```
15 | #/bin/bash
16 |
17 | touch /tmp/mynode_hook_pre_startup_complete
18 | ```
19 |
20 | After adding this script, the next time the device reboots, it will run the hook script during the startup process. To prove it was executed, look to see if the `/tmp/mynode_hook_pre_startup_complete` file was created. If so, your script was successfully executed!
21 |
22 | Caution: Any serious errors or infinite loops may negatively affect MyNode behavior.
23 |
24 | ## Hook Script Options
25 |
26 | | File Location | Description |
27 | | --- | --- |
28 | | /usr/local/bin/mynode_hook_pre_startup.sh | This script is executed during MyNode startup, prior to the drive being mounted. |
29 | | /usr/local/bin/mynode_hook_post_startup.sh | This script is executed during MyNode startup, after the drive being mounted and basic setup has completed. Services like Bitcoin, LND, and other applications have not started. |
30 | | /usr/local/bin/mynode_hook_post_bitcoin_synced.sh | This script is executed after Bitcoin has started and it has synced to the tip.
This script can execute multiple times if Bitcoin happens to get significantly out of sync and then catches back up. |
31 |
32 |
--------------------------------------------------------------------------------
/docs/device/changing-password.md:
--------------------------------------------------------------------------------
1 | # Changing your Password
2 |
3 | After setting up your MyNode, it is important to change the password. When performing various actions on your device, you will be prompted to enter you password before accessing sensitive data. Setting your own password will secure your device.
4 |
5 | First, go to the settings page. Next, fill out your current password. If it has never been set, the default password is "bolt".
6 |
7 |
8 |
9 |
10 |
11 |
12 |
13 | Finally, enter a new password, repeat it and click Save.
14 |
15 | Your password has now been updated!
16 |
--------------------------------------------------------------------------------
/docs/device/connect-wifi.md:
--------------------------------------------------------------------------------
1 | # Connect WiFi
2 |
3 | ## Purpose
4 |
5 | To disconnect from wired ethernet connection and use WiFi instead, which makes it easier to relocate the node.
6 |
7 | ## Remote login to MyNode
8 |
9 | Follow instructions to access the [linux terminal](/advanced/linux-terminal.html)
10 |
11 | ## Check device status
12 |
13 | - Type `nmcli dev status` and press Enter. You should find the ethernet to be connected and WiFi disconnected.
14 | ```bash
15 | DEVICE TYPE STATE CONNECTION
16 | eth0 ethernet connected Wired connection 1
17 | wlan0 wifi disconnected --
18 | lo loopback unmanaged --
19 | ```
20 |
21 | ## Connect to new network
22 |
23 | 1. `sudo nmtui`
24 | 2. Enter password
25 | 3. Use up/down and left/right keys to navigate.
26 | 4. Select "Activate Connection" and press Enter.
27 | 5. Select the WiFi name. Press Enter.
28 | 6. Enter the WiFi password. Press Enter.
29 | 7. An asterisk should appear next to the WiFi name.
30 | 8. Press Escape key twice to quit.
31 |
32 |
44 |
45 | ## Recheck device status
46 | - Type `nmcli dev status` and press Enter. You should see that WiFi is now connected.
47 | ```bash
48 | DEVICE TYPE STATE CONNECTION
49 | eth0 ethernet connected Wired connection 1
50 | wlan0 wifi connected
51 | lo loopback unmanaged --
52 |
53 | ```
54 |
55 | ## Disconnect Ethernet cable
56 |
57 | You can safely remove the ethernet cable.
58 |
59 | ## Find new IP
60 |
61 | 1. Type `ifconfig wlan0 | grep inet` to find the IP address on wireless network. Example
62 |
63 | ```bash
64 | $ ifconfig wlan0 | grep inet
65 | inet netmask 255.255.255.0 broadcast 10.0.0.255
66 | inet6 prefixlen 64 scopeid 0x20
67 | ```
68 |
69 | 2. Use the `LOCAL-IP` listed beside `inet` to access your node once it is disconnected from wired network
70 |
71 | ## Reconfigure LND for new IP
72 |
73 | If you are using apps like Zap to remotely access your lightning node, you might have to regenerate the TLS certificates. To do so, go to the LND page of your MyNode and click on "regenerate" button in the row of "TLS Certification".
74 |
75 |
80 |
81 | ## Reconfigure VPN port forwarding
82 |
83 | If you are using the VPN to remotely access your node, you need to change the IP address corresponding to the forwarded port in your router settings. Please refer your router manufacturer's website to find out how to forward ports.
84 |
--------------------------------------------------------------------------------
/docs/device/forgot-password.md:
--------------------------------------------------------------------------------
1 | # Forgot your Password
2 | After setting up your MyNode, it is important to change the password. However, if you forget this password you will not be able to log back in to access the services. Luckily, MyNode was designed to make this recovery process relatively simple and not lose critical data, like the Bitcoin blockchain or Lightning data.
3 |
4 | All you need to do is reflash the SD card - detailed instructions available here.
5 |
6 | - Shutdown device using the button on the settings page
7 | - Remove SD Card from Device
8 | - Re-flash the SD Card
9 | - Insert SD card back into the device
10 | - Power device back on (may need to remove and re-connect power cable)
11 | - Your password has now been reset to "bolt"!
12 |
13 |
14 | Note: This process may cause your device to get a new IP address.
--------------------------------------------------------------------------------
/docs/device/upgrading-device.md:
--------------------------------------------------------------------------------
1 | # Upgrading your MyNode
2 | There are two main options for upgrading your MyNode device.
3 |
4 | ## One Click Update
5 |
6 | Premium Feature
7 |
8 | The first and easiest option to upgrade your MyNode is to purchase MyNode Premium (included if you purchased a device). You can see all your options on the [Order Now](https://mynodebtc.com/order_now) page.
9 |
10 | Once running MyNode Premium follow these steps:
11 |
12 | 1. Go to the settings page
13 | 2. Click on the "Check for updates button" to make sure an update is available
14 | 3. Click "Upgrade" and your device will automatically update to the latest version!
15 |
16 |
17 | ## Manual Upgrade
18 |
19 | The second option is to upgrade manually via the Linux Terminal by running a few commands.
20 |
21 | Follow these steps to manually upgrade to the latest version:
22 |
23 | 1. Open 2 Terminal windows:
24 | * Terminal 1: Local PC or laptop
25 | * Terminal 2: Connect to your MyNode Device ([see options](https://mynodebtc.github.io/advanced/linux-terminal.html))
26 | * Command: `ssh admin@[MyNode ip address]`
27 | * Default credentials: admin/bolt
28 | 2. Clone the latest release from the git repo on your PC or laptop
29 | * Run `git clone https://github.com/mynodebtc/mynode.git`
30 | * Run `cd mynode`
31 | * Run `git checkout tags/latest_release`
32 | 3. Run `make rootfs`
33 | 4. Run `make start_file_server`
34 | * This will run a local HTTP server so your device can download files
35 | 5. On the other terminal which you used to ssh into your device, run `sudo mynode-local-upgrade [pc ip address]`
36 | * This will download your locally generated artifact and install it on your device
37 | * Your device will automatically reboot to ensure updates take effect
38 | 6. Optional: Run `make stop_file_server`
39 | * This will stop the local HTTP server
40 | 7. You are now running the latest version of MyNode software!
41 |
42 |
--------------------------------------------------------------------------------
/docs/electrum/electrum.md:
--------------------------------------------------------------------------------
1 | # Electrum Server
2 |
3 | ## Enabling Electrum Server
4 |
5 | Electrum is a very popular light wallet that lets you use Bitcoin on your PC or mobile device without needing a full copy of the blockchain. By running Electrum Server on your MyNode, you can run light wallets on other devices in a trusted manner by offloading the heavy lifting to MyNode.
6 |
7 | First, from the MyNode home page click "Enable" to start running Electrum Server. Depending on the speed of your device, it may take several days to fully sync Electrum. Your device may run slowly during this initial sync period.
8 |
9 |
10 |
11 |
12 |
13 |
14 |
15 | Once the server has synced, you should see an Electrum Server status page similar to this.
16 |
17 |
18 |
19 |
20 |
21 |
22 |
23 | ## Connecting an Electrum Wallet to MyNode via the GUI
24 |
25 | At this point you can connect your Electrum light wallets to your MyNode. On the PC version, click on the colored icon in the bottom right to open up server settings. Enter the IP address of your MyNode with port 50002.
26 |
27 |
28 |
29 |
30 |
31 |
32 |
33 | If everything went correctly, you will get a green status icon and your MyNode device will be acting as your Electrum Server!
34 |
35 |
36 |
37 |
38 |
39 |
40 |
41 | *Notice!* At this point, your Electrum light wallet client may still use other servers for various things. To limit use to ONLY your node, you will need to make one more change.
42 |
43 | Re-open the Electrum network settings by clicking on the colored icon in the bottom right. The server you entered should now appear in the list. Right click on it and select "Use as Server" and click Close.
44 |
45 |
46 |
47 |
48 |
49 |
50 |
51 | Restart Electrum and you will be using MyNode for trusted Electrum access!
52 |
53 | ## Connecting an Electrum Wallet to MyNode via the CLI
54 |
55 | You can launch Electrum via a command line interface and connect it to you MyNode. Enter the following command and replace the IP with your own.
56 |
57 | If everything went correctly, you will get a green status icon and your MyNode device will be acting as your Electrum Server!
58 |
59 |
60 |
61 |
62 |
63 |
64 |
65 | ## Connecting an Electrum Wallet to MyNode via Mobile
66 |
67 | You can also run Electrum via the mobile app and connect it to you MyNode. First, go into settings and set the server like the following. Replace the IP with your own IP.
68 |
69 |
70 |
71 |
72 |
73 |
74 |
75 | Also make sure Auto-connect is ON and One-server mode is ON.
76 |
77 |
78 |
79 |
80 |
81 |
82 |
83 | If everything went correctly, you will get a screen like this and your MyNode device will be acting as your Electrum Server!
84 |
85 |
86 |
87 |
88 |
89 |
90 |
--------------------------------------------------------------------------------
/docs/intro/getting-started.md:
--------------------------------------------------------------------------------
1 | ---
2 | sidebarDepth: 0
3 | ---
4 |
5 | # Getting Started with MyNode
6 |
7 | ## Download and Install
8 |
9 | **Note:** You can skip flashing the SD card if you purchased a MyNode device!
10 |
11 | Setting up a new MyNode device can be done in a few simple steps!
12 |
13 | First, you need to download the MyNode image for your device type and [flash it to an SD card](/advanced/flash-sd-card) according to the instructions on the download page.
14 |
15 | ## Power On Device
16 |
17 | Follow the section the section that corresponds to your device.
18 |
19 | **Model One**
20 |
21 | - Insert the SSD into the USB Enclosure
22 | - Verify connections are secure
23 | - Attach SSD enclosure to device in USB 3 port (blue)
24 | - Connect Ethernet cable to your device and your router or switch
25 | - Plug power cable in outlet and connect to device
26 |
27 | **Model Two**
28 |
29 | - Insert the provided micro SD card or USB flash drive into the device
30 | - Connect Ethernet cable to your device and your router or switch
31 | - Plug power cable in outlet and connect to device
32 | - Push power button to turn on device
33 |
34 | **Building your Own**
35 |
36 | Many devices, like the Model One and Raspberry Pi 4, use an external drive attached via USB for data storage. If your device uses external storage, follow these steps.
37 |
38 | - Insert SSD into USB Enclosure
39 | - Verify connections are secure
40 | - Attach SSD enclosure to device in USB 3 port (blue)
41 |
42 | If your device supports internal storage drives, those should be preferred and offer better performance. Attach an SSD or NVMe drive of at least 1TB.
43 |
44 | - Connect Ethernet cable to your device and your router or switch
45 | - Plug power cable in outlet and connect to device
46 |
47 | ## Connecting to MyNode
48 |
49 | Your MyNode device runs its own web server that you can access with any browser on the same WiFi or local network. Visit [http://mynode.local/](http://mynode.local/) or [the IP address](/advanced/find-device-ip) in a web browser on your PC, laptop, tablet, or phone.
50 |
51 | **Note:** The device may reboot during initial setup. The web interface may not be available for 5-10 minutes.
52 |
53 | You will be prompted to enter your product key. If you are using the Community Edition, you can choose that option. Otherwise, enter the product key that has either been emailed to you, or is found on the bottom of your device.
54 |
55 |
56 |
57 |
58 |
59 |
60 |
61 | Next, the device will begin syncing the Bitcoin Blockchain! This process can take 6+ days, depending on your device and your network bandwidth. The MyNode web interface will show you the current status of synchronization. Once the initial sync is completed, the device will automatically stay synchronized with the Bitcoin network and display the main application page.
62 |
63 |
64 |
65 |
66 |
67 |
68 |
69 | Your MyNode device is now ready and you will see the main MyNode home page.
70 |
71 |
72 |
73 |
74 |
75 |
76 |
77 | You can optionally connect to your MyNode device via SSH if you are familiar with Linux. You can connect using the device IP or hostname.
78 |
79 | ### Default Credentials
80 |
81 | Username: `admin`
82 |
83 | Password: `bolt`
84 |
85 | **Note:** It is recommended to [change your password](/device/changing-password).
86 |
87 | From here, you can start using all the features MyNode has to offer!
88 |
89 |
90 | ## Next Steps
91 |
92 | [Change your Password](/device/changing-password)
93 |
94 | [Setup Lightning Wallet](/lightning/create)
95 |
--------------------------------------------------------------------------------
/docs/intro/introduction.md:
--------------------------------------------------------------------------------
1 |
2 |
3 |
4 |
5 |
6 |
7 |
8 | The easiest way to run Bitcoin and Lightning!
9 |
10 | MyNode aims to simplify running a dedicated Bitcoin node and Lightning wallet. The system combines the best open source software with our browser-based interface for accessing all your favorite apps, so you can safely and securely use Bitcoin and Lightning.
11 |
12 | Read more to see all MyNode has to offer!
13 |
14 |
15 |
16 |
17 |
18 |
19 |
20 |
21 | Website: [mynodebtc.com](https://mynodebtc.com)
22 |
--------------------------------------------------------------------------------
/docs/lightning/alby.md:
--------------------------------------------------------------------------------
1 | # Alby
2 |
3 | Alby is your companion for bitcoin transactions on the web. Connect your MyNode wallet to the Alby Browser Extension and use Bitcoin & Nostr apps conveniently in a non-custodial way.
4 |
5 |
6 | ## Introduction
7 |
8 | Alby is a browser extension to send and receive bitcoin payments with your normal browser on the Bitcoin Lightning Network with ease.
9 | - set a budget for each website to conveniently spend, but not overspend
10 | - connect an existing bitcoin lightning wallet or create a new one
11 | - manage multiple lightning accounts in Alby
12 | - log into bitcoin apps without passwords
13 | - securely store you Nostr private key, log into Nostr apps and interact with other users
14 | - fully open-source under the MIT license
15 | - client side only; all data stays within your browser
16 |
17 | Alby is an app from the community for the community. You can always view and contribute to the source code on: https://github.com/getAlby/lightning-browser-extension
18 |
19 | **Try it out!**
20 |
21 | ## Using Alby with myNode
22 | 1) Install Alby by visiting getalby.com
23 |
24 |
25 |
26 |
27 |
28 |
29 | 2) Set a passcode to protect accesss to the app
30 |
31 |
32 |
33 |
34 |
35 |
36 | 3) Click on "Connect" other wallet
37 |
38 |
39 |
40 |
41 |
42 |
43 | 4) Choose MyNode connector
44 |
45 |
46 |
47 |
48 |
49 |
50 | 5) Select the node/option to connect
51 |
52 |
53 |
54 |
55 |
56 |
57 | 6) Follow the instruction displayed in the window.
58 |
59 | Thanks for using Alby. If you cannot connect your MyNode have a look at Alby's [guides](https://guides.getalby.com/overall-guide/alby-browser-extension/debugging).
60 |
--------------------------------------------------------------------------------
/docs/lightning/bluewallet.md:
--------------------------------------------------------------------------------
1 | # Blue Wallet (LND Hub)
2 |
3 | The first step to using Blue Wallet with your MyNode is enalbling LND Hub. The can be done by clicking the "Enable" button underneath the LND Hub icon on the main page.
4 |
5 |
6 |
7 |
8 |
9 |
10 |
11 | Next, you can click on the "LND Hub" button and view the LND Hub web interface. This is not required.
12 |
13 |
14 |
15 |
16 |
17 |
18 |
19 | Now that LND Hub is running, install Blue Wallet on your mobile device and connect it to your MyNode!
20 |
21 | From the mobile wallet, click on the settings icon and then click on Lightning Settings. On this screen, enter the URL to your MyNode device on port 3000 and click Save. Alternatively, you can scan a QR code according to the [pairing instructions](/lightning/pairing-wallets).
22 |
23 |
24 |
25 |
26 |
27 |
28 |
29 | Any new wallets added to Blue Wallet will be tied to your MyNode device!
30 |
--------------------------------------------------------------------------------
/docs/lightning/create.md:
--------------------------------------------------------------------------------
1 | # Create Lightning Wallet
2 |
3 | To create a Lightning wallet on your MyNode, first, click on the "Lightning Wallet" button on the main MyNode page. Next click "Create Wallet" and you will be given a seed phrase.
4 |
5 | **This phrase is critical and anyone with this phrase has access to your wallet. Write this phrase down for a backup and do not share it with anyone!**
6 |
7 | Click "Continue" after you have written down your seed phrase.
8 |
9 | On the next page, re-enter your seed phrase to verify your backup has been created properly. Click "Create" to create your wallet!
10 |
11 | 
12 |
13 | If your phrase was correct, you will be sent back to the main Lightning page and your Lightning wallet will begin syncing and setting itself up. After a few minutes, the Lightning wallet should be ready and you should see a page like this.
14 |
15 | 
16 |
17 | Your Lightning wallet is now setup and ready to use!
18 |
19 | You can use your wallet via numerous interfaces. Check out the guides on look into RTL, Thunderhub, Blue Wallet and more!
20 |
21 | ### Next Steps
22 |
23 | [Open Ride the Lightning](/lightning/rtl)
24 |
25 | [Open Thunderhub](/lightning/thunderhub)
--------------------------------------------------------------------------------
/docs/lightning/lightning-terminal.md:
--------------------------------------------------------------------------------
1 | # Lightning Terminal
2 |
3 | Lightning Terminal is a tool made by Lightning Labs to control Loop and Pool via a convenient web interface.
4 |
5 | ## Opening Lightning Terminal
6 |
7 | Lightning Terminal can be opened via the Lightning icon under the Lightning tile on the homepage or via the Lightning Terminal "open" button on the Lightning page.
8 |
9 | 
10 |
11 | After opening the app, you will be prompted for a password.
12 |
13 | 
14 |
15 | This is NOT your MyNode password. To increase security, MyNode has generated a random password that can be found on the Lightning page. To see the password, click "show password" next to the Lightning Terminal label. You can easily copy it via the copy icon next to the password.
16 |
17 | 
18 |
19 | After logging in, you will see a screen similar to this. It allows easy control over Lightning Loop and Pool.
20 |
21 | 
--------------------------------------------------------------------------------
/docs/lightning/lnbits.md:
--------------------------------------------------------------------------------
1 | # LNbits
2 |
--------------------------------------------------------------------------------
/docs/lightning/lnd-alias.md:
--------------------------------------------------------------------------------
1 | # Setting your LND Alias
2 |
3 | Every Lightning node has a name that can be configured. By default, each MyNode device uses the name "mynodebtc.com [MyNode]". To change this name first go to the LND page in the GUI and click the gear icon in the Alias box.
4 |
5 | 
6 |
7 | After clicking on the gear icon, you will be presented with a popup that allows you to change your node's alias. Enter the new alias and click Save. This will reboot your device and it will come with the new alias!
8 |
9 | 
10 |
--------------------------------------------------------------------------------
/docs/lightning/pairing-wallets.md:
--------------------------------------------------------------------------------
1 | # Pairing Wallets
2 |
3 | Various Lightning mobile apps can be paired with your node's Lightning instance. This allows the app to use the same channels and funds available on your MyNode. Wallet apps can be paired with QR Codes and URLs that make connecting apps to a Lightning node very easy.
4 |
5 | First, make sure you have created a Lightning wallet and from the main MyNode home page, click on the QR icon under Lighting. A link is also available on the Lightning page.
6 |
7 |
8 |
9 |
10 |
11 |
12 |
13 | You will be prompted to enter your password. This prompt ensures you are securely accessing your device since anyone with your pairing codes can access your lighting wallet. Keep it secret!
14 |
15 |
16 |
17 |
18 |
19 |
20 |
21 | Once on the Pair Wallet page, you will see a drop down menu to choose a pairing option. After choosing an option, a QR code and a URL will appear. These can be used to easily connect your MyNode device to 3rd party Lightning wallets.
22 |
23 |
24 |
25 |
26 |
27 |
28 |
29 | Have fun pairing your favorite lightning wallets!
30 |
31 |
--------------------------------------------------------------------------------
/docs/lightning/restore.md:
--------------------------------------------------------------------------------
1 | # Restore Lightning Wallet
2 |
3 | If you already have a Lighting Wallet and want to restore it, you can do so via the MyNode interface.
4 |
5 | **Note:** You will only see the options to create or restore a wallet if no wallet exists. If a wallet has been created, you will first need to delete the Lightning wallet via the settings page before it can be restored.
6 |
7 | ## Restoring a Lightning Wallet
8 |
9 | First, click on Create Wallet under the Lightning app on the MyNode home page.
10 |
11 | Then, click on "Restore Wallet from Seed" on the Lightning page.
12 |
13 | **You will need your seed phrase and Static Channel Backup file!**
14 |
15 |
16 |
17 |
18 |
19 |
20 |
21 | On the next page, enter your seed phrase and upload your Static Channel Backup (SCB) file. Click Create.
22 |
23 | 
24 |
25 | This will restore you on-chain balance, close all channels that had been opened, and restore those funds in you on chain wallet. Seeing the channel funds appear may take a while.
26 |
27 | Your Lightning wallet is now setup and ready to use!
28 |
29 | ## Manual Recovery
30 |
31 | If all funds do not re-appear, you may need to use the lightning CLI to recover or check on the status of channels that are being closed.
32 |
33 | Below are more resources for recovering wallets.
34 |
35 | Recovering Funds
36 |
37 | Node Recovery
--------------------------------------------------------------------------------
/docs/lightning/rtl.md:
--------------------------------------------------------------------------------
1 | # Ride the Lightning (RTL)
2 |
3 | A GUI to manage Lightning channels
4 |
5 | ### Logging into RTL
6 |
7 | Ride the Lightning is a Lightning wallet and node management tool accessible via a web interface, and is built into MyNode.
8 | RTL is a creation of Suheb/saubyk, and complete information can be found at [Github](https://github.com/ride-the-lightning/RTL).
9 | The developer can be contacted via Twitter at: [@Suheb__](https://twitter.com/Suheb__) [@RTL_App](https://twitter.com/RTL_app).
10 |
11 | You can use RTL from any browser that is able to access your MyNode installation.
12 |
13 | Once a Lightning wallet [has been created](/lightning/create) on your device, the RTL app will be available via a button on the home page.
14 |
15 |
16 |
17 |
18 |
19 |
20 |
21 | After clicking the button, you will be presented with a login page. Use your MyNode password to login. Once logged in, the main RTL page will be displayed.
22 |
23 | 
24 |
25 | ### Funding your BTC Wallet
26 |
27 | In order to participate in the Lightning Network, you first need to fund your on-chain Bitcoin wallet. To do this, click on "On-chain" on the Navigation Panel on the left. Then click on the "Generate Address" button.
28 |
29 | This will generate a new address and corresponding QR code for you to use to fund your on-chain wallet.
30 |
31 | ### Opening a Channel
32 |
33 | To spend bitcoins on the Lightning network, one must first find peers on the network and open a channel with them. Peers can be trusted friends or complete strangers. [1ML.com](https://1ml.com/node?order=channelcount&active=true) or the MyNode Telegram channel are good places to find peers.
34 |
35 | When you have selected another Lightning node to connect to, click on "Lightning" in the RTL navigation panel, then click on "Peers/Channels". Under the "Connections" heading, find and click on "Peers" as shown:
36 |
37 | 
38 |
39 | Click on the "Add Peer" button, then:
40 |
41 | - Fill in the required information for your selected peer and close that window.
42 | - Click on the "Channels" button that is right under the "Connections" heading.
43 | - Click on the "Open Channel" button.
44 | - Select your chosen peer, fill in the amount of Bitcoin that you wish to open the channel with, and then click on "Open Channel"
45 | in the lower right corner of that window.
46 |
47 | You can verify the status of the channel via the Channels page. The channel will be pending until the transaction used to open the channel is confirmed.
48 |
49 |
50 | ### Sending Bitcoin using RTL & Lightning
51 |
52 | When your funding transaction is confirmed on the blockchain you are now ready to send Bitcoin using Lightning.
53 | You will need a payment invoice from the person you want to pay. Typically, either the payee will send you an invoice or you will copy it from a webpage.
54 |
55 | Go to the RTL navigation pane and click on "Lightning" and then "Transactions".
56 |
57 | 
58 |
59 | Click on "Send Payment" and paste your copy of the invoice in the window that opens.
60 | All of the details of the payment should automatically be filled in.
61 | Now, just click the "Send Payment" button and the payment should be completed within seconds!
62 |
63 | ### Receiving Bitcoin using RTL and Lightning
64 |
65 | To receive Bitcoin in any Lightning wallet, you must first establish what is called "inbound capacity".
66 |
67 | **Tip**: When creating Lightning channels with peers, it is generally a good practice for each party to open a separate channel from two ends to have some inbound and outbound capacity for each of them.
68 |
69 | There are many other ways to establish inbound capacity, but they are beyond the scope of this guide.
70 | A good overview of how to establish inbound capacity can be found [here](https://gist.github.com/bretton/53bc511b6fdafef31951199dd25bbf88).
71 |
72 | ### References
73 |
74 | - Github: [github.com/ride-the-lighting/RTL](https://github.com/Ride-The-Lightning/RTL)
75 |
--------------------------------------------------------------------------------
/docs/lightning/thunderhub.md:
--------------------------------------------------------------------------------
1 |
2 | # Thunderhub
3 |
4 | A GUI to manage Lightning channels
5 |
6 | ## Introduction
7 |
8 | Created by Anthony Potdevin, ThunderHub is an open-source LND node manager to monitor your node and manage channels via a web-interface. It allows you to take control of the Lightning network with a simple and intuitive UX.
9 |
10 | ThunderHub is part of the *Beta Apps* on MyNode available only for *premium* users.
11 |
12 | 
13 |
14 | ## Features
15 |
16 | Find the full list of features on [GitHub](https://github.com/apotdevin/thunderhub) or [website](https://thunderhub.io). Key features are listed below.
17 |
18 | ### Monitoring
19 | - Overview of current and pending balance for the Lightning and Bitcoin wallets.
20 | - Liquidity report with total remote and local Lightning balance.
21 | - Complete network info.
22 | - View open/pending/closed channels and how balanced they are.
23 | - View all transactions.
24 | - View all forwarded payments.
25 | - View all chain transactions.
26 | - View all unspent UTXOS.
27 |
28 | ### Management
29 |
30 | - Send and Receive Lightning payments.
31 | - Send and Receive Bitcoin payments.
32 | - Open and close channels.
33 | - Balance your channels through circular payments. (Check out the Tutorial)
34 | - Backup, verify and recover all your channels.
35 | - Sign and verify messages.
36 |
37 | ## ThunderHub on MyNode
38 |
39 | ThunderHub is already configured with default environment variables and connected to the Lightning wallet, but it is disabled by default. To enable it, open the MyNode homepage and find the tile with the ThunderHub logo under Beta Apps (like the left image below).
40 |
41 |
42 |
43 |
44 |
45 |
46 | Click on the **Enable** button, and wait for the page to refresh.
47 |
48 | You should now see a **ThunderHub** button (like shown on the right image above) and a green dot. On clicking this button, a new tab should open on your browser, containing ThunderHub.
49 |
50 | On the ThunderHub tab, click the **Login** button, enter your MyNode password and then click on **Connect**.
51 |
52 | 
53 |
54 | You should end up at the ThunderHub dashboard (as shown in the first image at the top).
55 |
56 | ## Specs
57 |
58 | - Website: [thunderhub.io](https://thunderhub.io)
59 | - Github: [apotdevin/thunderhub](https://github.com/apotdevin/thunderhub)
60 | - Installed location: `/opt/mynode/thunderhub` (NodeJS package)
61 | - Ports: [http://mynode.local:3030/](http://mynode.local:3030/) or [https://mynode.local:3031](https://mynode.local:3031/)
62 |
--------------------------------------------------------------------------------
/docs/lightning/zap.md:
--------------------------------------------------------------------------------
1 |
2 | # Zap
3 |
4 | ## Using Zap with MyNode (Desktop)
5 |
6 | First, install Zap on your PC.
7 |
8 | Next, open the Zap desktop app, click on "Create New Wallet".
9 |
10 |
11 |
12 |
13 |
14 |
15 |
16 | Select "Connect" and click Next. Now, open the MyNode GUI and go to the LND Connect page. Copy the LND Connect URL from the "gRPC Local IP" tab. Paste the URL into the Connection String box in Zap.
17 |
18 |
19 |
20 |
21 |
22 |
23 |
24 | Click Next and click Next on the Confirm screen. Zap will connect and use your MyNode device's wallet!
25 |
26 |
27 |
28 |
29 |
30 |
31 |
32 | ## Using Zap with MyNode (Android)
33 |
34 | First, install Zap on your mobile device.
35 |
36 | Next, open the Zap mobile app and tap on "Connect to Remote Node".
37 |
38 |
39 |
40 |
41 |
42 |
43 |
44 | In your the MyNode GUI, open the LND Connect page and enter your MyNode password. In the Zap app, scan the QR code in the "gRPC Local IP" tab.
45 |
46 |
47 |
48 |
49 |
50 |
51 |
52 | After Zap successfully scans the QR code, Zap will be using your MyNode device's wallet!
53 |
54 |
55 |
56 |
57 |
58 |
59 |
--------------------------------------------------------------------------------
/docs/lightning/zeus.md:
--------------------------------------------------------------------------------
1 |
2 | # Zeus
3 |
4 | ## Using Zeus with MyNode
5 |
6 | First, install Zeus on your mobile device.
7 |
8 | Next open the app, go to settings and tap "Add a new node".
9 |
10 |
11 |
12 |
13 |
14 |
15 |
16 | Tap on "Scan lndconnect config".
17 |
18 |
19 |
20 |
21 |
22 |
23 |
24 | Open the QR Pairing page on MyNode and scan the QR Code from the "REST Local IP" tab.
25 |
26 |
27 |
28 |
29 |
30 |
31 |
32 | Once the QR code is scanned, click "Save Node Config" and go back to the main app screen. Zeus is now using your MyNode device!
33 |
34 |
35 |
36 |
37 |
38 |
--------------------------------------------------------------------------------
/docs/multisig/caravan.md:
--------------------------------------------------------------------------------
1 | # Caravan
2 |
--------------------------------------------------------------------------------
/docs/multisig/specter.md:
--------------------------------------------------------------------------------
1 | # Specter
2 |
3 | Developed by [Crypto Advance GmbH](https://specter.solutions/about/), Specter is a desktop GUI for Bitcoin Core optimized to work with hardware wallets. Funds in hardware wallets are far more secure than using a hot wallet like Bitcoin Core or Electrum. Specter is built on top of Bitcoin Core as opposed to the conventional layer of an Electrum server between a wallet and Bitcoin Core. This removes a dependency and frees memory that would be used for storing the indexed database created by Electrum server.
4 |
5 | Along with supporting single signature wallets, Specter also supports multi-signature wallets.
6 |
7 | Specter is part of the *Beta Apps* on MyNode available only for *premium* users.
8 |
9 | 
10 |
11 | ## Features
12 |
13 | Find the full list of features on [GitHub](https://github.com/cryptoadvance/specter-desktop). Key features are:
14 |
15 | - hardware wallet support
16 | - [multisig](https://en.bitcoin.it/wiki/Multisignature)
17 | - [Partially Signed Bitcoin Transactions](https://bitcoinops.org/en/topics/psbt/)
18 | - Check total bitcoin supply (Run the numbers!)
19 |
20 | ## Using Specter
21 |
22 | ### On MyNode
23 |
24 | Specter is already configured with default environment variables and connected to Bitcoin Core, but it is disabled by default. To enable it, open the MyNode homepage and find the tile with the Specter logo under Beta Apps (like the left image below).
25 |
26 |
27 |
28 |
29 |
30 |
31 |
32 | Click on the **Enable** button, and wait for the page to refresh.
33 |
34 | You should now see a **Specter** button (like shown on the right image above) and a green dot. On clicking this button, a new tab should open on your browser, containing Specter GUI.
35 |
36 | Adding `blockfilterindex=1` to your [Bitcoin Config](/advanced/customize-config.md) file will occupy few more GB of storage but would improve the rescanning speed.
37 |
38 | ### Remote Use
39 |
40 | Your MyNode installation of Specter includes the additional "HWI Bridge" code to allow you to access your Specter wallet remotely.
41 | If you are using the MyNode VPN, make sure that the VPN is running and then you can start MyNode in your browser by entering `https://mynode.local:25441`. If you are using Tor for remote access, find your [Tor Hidden Service Address](/tor/web-gui.md) for Specter.
42 | Start a Tor browser and enter `your-tor-hidden-service-address:25441`.
43 |
44 | Specific instructions on how to use Specter can be found [here](https://github.com/cryptoadvance/specter-desktop/blob/master/docs/faq.md#how-do-i-run-the-app).
45 |
46 | If you face any issues, read their [FAQ](https://github.com/cryptoadvance/specter-desktop/blob/master/docs/faq.md).
47 |
48 | ## Specs
49 |
50 | - Github: [cryptoadvance/specter-desktop](https://github.com/cryptoadvance/specter-desktop)
51 | - Community: [Specter Telegram](https://t.me/spectersupport)
52 | - Installed location: A Python3 module with environment settings at `/opt/mynode/specter`
53 | - Ports: [https://mynode.local:25441](https://mynode.local:25441/)
54 |
--------------------------------------------------------------------------------
/docs/networking/tor.md:
--------------------------------------------------------------------------------
1 | # Using Tor for Bitcoin and LND
2 |
3 | ## Overview
4 |
5 | Tor is a technology that allows devices to communicate securely and privately via the Internet. This technology can be incredibly useful to Bitcoin and Lightning by securing connections between the devices you use everyday and your MyNode.
6 |
7 | By default, tor is enabled for Bitcoin and Lightning connections to the network for both Community and Premium users. This helps simplify network configuration and provide security. Some advaned users may want to disable this, and that option is available on the settings page.
8 |
9 | For more information on Tor, visit their [website](https://www.torproject.org/).
10 |
11 | ## Enabling or Disabling Tor for Bitcoin and LND
12 |
13 | To view or modify your current Tor setting for use by Bitcoin and LND, look for the Networking section on the settings page. Move the slider to enable or disable Tor for LND and/or Lightning and click Save. Your device will reboot and Bitcoin and LND will be using the new Tor setting.
14 |
15 |
16 |
17 |
18 |
19 |
20 |
--------------------------------------------------------------------------------
/docs/premium_plus/connect.md:
--------------------------------------------------------------------------------
1 | # Connect Device
2 |
3 | Several of the best Premium+ features, require pairing your node with your account at myndoebtc.com, including the following.
4 |
5 | - Remote SCB Backup
6 | - Lightning Watchtwer
7 | - Monitor Node Info
8 |
9 | Pairing a node is simple. It only requires the following steps, some of which may be done already.
10 |
11 | - Login or Register at mynodebtc.com
12 | - Add your product to your account
13 | - Open "My Devices" to get Access Token
14 | - Paste it into your node's Premium+ Page
15 |
16 | ## Login or Register
17 |
18 | The first step to setting up Premium+ is to make sure you have an account on mynodebtc.com. There, you can login or register if you have not previously setup an account.
19 |
20 |
21 |
22 |
23 |
24 |
25 |
26 | **Note:** Placing an order does not automatically create an account.
27 |
28 | ## Add Product Key
29 |
30 | Once you've registered and logged in, the next step is to visit the Product Key page. Here, you can add your product key, which is tied to your Premium+ subscription.
31 |
32 | To add your product key type your key into the text field and click the "Add Key" button. If successful, it should appear in a list of product keys.
33 |
34 |
35 |
36 |
37 |
38 |
39 |
40 | **Note:** Your product key may be automatically imported into your account if your registered email address matches the email addres used when placing your order.
41 |
42 | ## Open My Devices to get Access Token
43 |
44 | After your Product Key has been added, click the "My Devices" link in the navigation bar at the top of the screen. This will take you to a page with a list of devices, which includes an Access Token for each product key linked to your account.
45 |
46 | **Note:** If you see an error or warning on this page about an expired subscription, you can get more information on the Subscriptions page. A link it available in the nav bar at the top of the screen.
47 |
48 | The page with one product key associated with your account will look similar to this.
49 |
50 |
51 |
52 |
53 |
54 |
55 |
56 | This is showing "N/A" for the Last Update because the token has not been used on a device yet. After configuring the Access Token on your device, the field will update to indicate your device is connected with Premium+.
57 |
58 | ## Paste Access Token in Device
59 |
60 | Now, copy your Access Token and navigate to the main Premium+ page on your node. The link is available in the Networking section on the home page.
61 |
62 |
63 |
64 |
65 |
66 |
67 |
68 | After opening the page, click the Set Token button, paste your Access Token into the field and click Save.
69 |
70 | Now, your device will connect to mynodebtc.com to enable the Premium+ features, like remote SCB backup!
71 |
72 | To better control what you want to be accessible via mynodebtc.com, you can individually toggle each feature and once they token was saved, each feature toggle because enabled.
73 |
74 |
75 |
76 |
77 |
78 |
79 |
80 | To enable a feature, click the toggle next to the feature you want to enable and click Save. An info icon is also available next to each feature to better explain it. More info is also available here, on the Guides website.
81 |
82 | Finally, now that you are connected and have enabled any features you are interested in, go back to mynodebtc.com. On the "My Devices" page, click the Manage in the row with the access token you used.
83 |
84 |
85 |
86 |
87 |
88 |
89 |
90 | You will now see info about your device! Depending on what was enabled, you may have info about your node status, channel status, peer info, application status info, and a link to download your SCB file! Over time, the features and functionality available in Premium+ will continue to grow!
--------------------------------------------------------------------------------
/docs/premium_plus/premium_plus.md:
--------------------------------------------------------------------------------
1 | # Premium+
2 |
3 | ## What is Premium+?
4 | Premium+ is a service that is included with all MyNode orders and includes support along with a ton of additional features. Many of these features can be unlocked by connecting your device to your account on mynodebtc.com via an Access Token.
5 |
6 | ## Features
7 | Premium+ Includes and number of wonderful features and services.
8 |
9 | - Extended Support
10 | - Remote SCB Backup
11 | - Lightning Watchtower
12 | - Monitor you Node
13 |
14 | ## Extended Support
15 | MyNode Premium support, that has been included with all purchases, can be very helpful to get bugs fixed or to help diagnose issues, but ends after a year. Extending Premium+ includes additional Premium Support and access to our new support ticketing system.
16 |
17 | ## Remote SCB Backup
18 | When using Lightning, an important aspect of the backup procedure is to ensure you have access to your seed phrase as well as a copy of your Static Channel Backup file. This file is updated each time you open or close a Lightning channel and is important for helping close channels and recover funds if a recovery is necessary. In the event of loss or physical damage to your node, an additional copy may be vital. Remote SCB backup uploads an encrypted copy of the SCB file to MyNode for use when you need it.
19 |
20 | ## Lightning Watchtower
21 | When using Lightning, especially with peers you do not know or trust, there is a chance your peer may attempt to close your channel based on an innaccurate accounting of funds if you are offline at the time. This creates a potential for your peer to cheat and close the channel indicating they will receive more funds than they should. Having a watchtower monitor your node's channels mitigates this risk.
22 |
23 | ## Monitor you Node
24 | If you are interested, you can enable remote node monitoring which allows you to view your node's status via mynodebtc.com. This can be helpful when away from your node and allows viewing node information like Bitcoin status, Lightning status, app statuses, and device info.
25 |
--------------------------------------------------------------------------------
/docs/tor/electrum.md:
--------------------------------------------------------------------------------
1 | # Electrum Server via Tor
2 |
3 | ## Enabling Electrum Server
4 |
5 | Electrum is a very popular light wallet that lets you use Bitcoin on your PC or mobile device without needing a full copy of the blockchain. By running Electrum Server on your MyNode, you can run light wallets on other devices in a trusted manner by offloading the heavy lifting to MyNode.
6 |
7 | First, from the MyNode home page click "Enable" to start running Electrum Server. Depending on the speed of your device, it may take several days to fully sync Electrum. Your device may run slowly during this initial sync period.
8 |
9 |
10 |
11 |
12 |
13 |
14 |
15 | Once the server has synced, you should see an Electrum Server status page similar to this.
16 |
17 |
18 |
19 |
20 |
21 |
22 |
23 | ## Electrum via Tor
24 |
25 | #### Premium Feature
26 |
27 | Electrum is an easy-to-use light wallet, but requires that you delegate some trust to other servers to give you correct information about your Bitcoin. MyNode removes this risk by running a full Bitcoin node and Electrum Server on the device, removing the need to trust a random server to provide you accurate information about your Bitcoin funds.
28 |
29 | However, for your mobile wallets to work properly wherever you are, you need to have public connection to your MyNode. The most secure way to do this is via Tor. It allows remote, encrypted connections back to your MyNode device.
30 |
31 | More information and tips are available in this community guide as well - All The Reasons You’ve Failed To Connect Electrum to Your Node Via Tor by Arman the Parman.
32 |
33 | ## Android Electrum Wallet Use via Tor
34 |
35 | On your Android device, download Orbot and enable it by Clicking the Start button. This will create a Tor connection from your phone.
36 |
37 |
38 |
39 |
40 |
41 |
42 |
43 | Next, open the Electrum Server information page on your MyNode device and find the Onion URL. This link will need to be used later in the Electrum App.
44 |
45 |
46 |
47 |
48 |
49 |
50 |
51 | Next, download the Electrum app for Android and create or import a wallet. Once your wallet has been added, click on the settings icon and choose Network. On the Network page, set Auto-connect to OFF and One-server mode to ON. Set the proxy settings to:
52 | Proxy mode: `socks5`
53 | Host: `localhost`
54 | Port: `9050`
55 |
56 | And set the Server settings to:
57 | Host: `[your Onion Electrum URL]`
58 | Port `50002`
59 |
60 |
61 |
62 |
63 |
64 |
65 |
66 | If everything went correctly, your wallet will sync and your MyNode device will be acting as your Electrum Server!
67 |
68 |
69 |
70 |
71 |
72 |
73 |
74 | ## Linux Electrum Wallet Use via Tor
75 |
76 | On your Linux PC, make sure you have Tor and Electrum installed. Tor can be installed as a proxy or Tor Browser, which includes the proxy functionality.
77 |
78 | Open Electrum and update your settings
79 |
80 | Proxy mode: `socks5`
81 | Host: `localhost`
82 | Port: `9050` or `9150` (if using Tor Browser's proxy)
83 |
84 | And set the Server settings to:
85 | Host: `[your Onion Electrum URL]`
86 | Port `50002` or `50001`
87 |
88 | Your Electrum wallet should connect successfully and look like the following!
89 |
90 |
91 |
92 |
93 |
94 |
95 |
--------------------------------------------------------------------------------
/docs/tor/setup.md:
--------------------------------------------------------------------------------
1 | # Tor Setup
2 |
3 | ## Using Tor with your MyNode
4 |
5 | #### Premium Feature
6 |
7 | Tor is a technology that allows devices to communicate securely and privately via the Internet. This technology can be incredibly useful to Bitcoin and Lightning by securing connections between the devices you use everyday and your MyNode.
8 |
9 | By enabling Tor, you can use apps, like Electrum, on your phone or laptop no matter where you are and still rely on the trust your MyNode provides.
10 |
11 | For more information on Tor, visit their [website](https://www.torproject.org/).
12 |
13 | ## Tor Browser Setup
14 |
15 | On any operating system, if you want to access the MyNode Web User Interface via Tor, go to [torproject.org](https://www.torproject.org/) and download and install the Tor Browser application.
16 |
17 | Once installed, you can access the MyNode UI via the link shown on the Tor page.
18 |
19 | ## Tor Setup on Android
20 |
21 | On your Android device, download Orbot and enable it by Clicking the Start button. This will create a Tor connection from your phone.
22 |
23 |
24 |
25 |
26 |
27 |
28 |
29 | Some apps require "VPN Mode" to access Tor. Tap the settings button next to "Full Device VPN" and select the apps - each app's guide will describe if VPN Mode is required.
30 |
31 | ## Tor Setup using Tor Browser (Windows, Linux, Mac)
32 |
33 | On your PC or laptop, install Tor Browser.
34 |
35 | Once installed, you can use it to browse to the onion URLs found via the Tor page on your MyNode device. Many services are available via a web interface, like RTL, Thunderhub, BTC Pay Server, etc...
36 |
37 | However, other services require the Tor network, but not the Tor browser. For example, wallets connecting to Electrum Server use the network, but cannot be interacted with via the browser. In these cases, you can use the proxy being run behind the tor browser by setting the app's proxy to port 9150.
38 |
39 | ## Tor Setup on Linux
40 |
41 | On your Linux PC, install Tor so you have a proxy running.
42 |
43 | ```
44 | sudo apt-get install tor
45 | ```
46 |
47 | Your Linux PC is now running a Tor proxy and ready to connect to Tor services provided by MyNode!
48 |
49 |
50 | ## Find Onion URL for Service
51 |
52 | To find the proper Onion URL for a service, open the Tor information page on your MyNode device.
53 |
54 |
55 |
56 |
57 |
58 |
59 |
60 | If you click "Show Onion URLs" you will see URLs for each service. Your device is now ready to use with various applications via Tor!
61 |
--------------------------------------------------------------------------------
/docs/tor/web-gui.md:
--------------------------------------------------------------------------------
1 | # Web Interface via Tor
2 |
3 | ## Accessing the Web User Interface
4 |
5 | #### Premium Feature
6 |
7 | You can access your MyNode Web Interface from anywhere using Tor if you are a Premium user. The device will open a secure Tor service for the user interface via Tor automatically.
8 |
9 | First, make sure you have Tor Browser installed via the instructions on the [Tor Setup](/tor/setup) page.
10 |
11 | Next, click on the Tor Services link under the Tor app on the main user interface screen.
12 |
13 |
14 |
15 |
16 |
17 |
18 |
19 | Then, click on the "Show Onion URLs" button and find the Onion URL for the MyNode Web service.
20 |
21 | Finally, open your Tor Browser app, copy the MyNode Web URL, and paste it into the Tor Browser URL bar.
22 |
23 |
24 |
25 |
26 |
27 |
28 |
29 | Your MyNode User Interface should appear!
30 |
31 | For more information on Tor, visit [torproject.org](https://torproject.org).
32 |
--------------------------------------------------------------------------------
/docs/tor/zeus.md:
--------------------------------------------------------------------------------
1 | # Using MyNode with Zeus Wallet via Tor
2 |
3 | ## Enable Tor on your Mobile Device
4 |
5 | #### Premium Feature
6 |
7 | First, enable Tor on your mobile device. Follow the [Setup Tor Guide](/tor/setup).
8 |
9 | ## Using Zeus Mobile with MyNode via Tor
10 |
11 | First, download the Zeus app to your mobile device.
12 |
13 | Next open the app, go to settings and tap "Add a new node".
14 |
15 |
16 |
17 |
18 |
19 |
20 |
21 | Tap on "Scan lndconnect config".
22 |
23 |
24 |
25 |
26 |
27 |
28 |
29 | Open the LND Connect page in the MyNode GUI and scan the QR Code from the "REST Tor" tab.
30 |
31 |
32 |
33 |
34 |
35 |
36 |
37 | Once the QR code is scanned, click "Save Node Config" and go back to the main app screen. Zeus is now using your MyNode device!
38 |
39 |
40 |
41 |
42 |
43 |
44 |
--------------------------------------------------------------------------------
/docs/troubleshooting/bitcoin-error.md:
--------------------------------------------------------------------------------
1 | # My Device has a Bitcoin Error
2 |
3 | If your device gets into a state indicating "Bitcoin has experienced an error. Please check the logs." it means Bitcoin is not able to start and so the device limits other services from starting until the Bitcoin error is resolved.
4 |
5 | ## Check the Bitcoin Log
6 |
7 | The first step is to track down the Bitcoin log on the status page and check it for errors. Click on the "status" link at the bottom of the page. Then click "Show Log" under the Bitcoin Status heading. This will open and display the recent lines of the Bitcoin log with the latest information at the top.
8 |
9 | Typical errors are corruption in the blockchain data. If you see errors similar to "failure to open database" or mentioning "corrupt" data, the blockchain data is likely bad. This can happen due to several reasons - the drive could be going bad or it could be from a power outage.
10 |
11 | ## Step 1
12 |
13 | First, just try rebooting the device and see if the error comes back. The error could be minor and the device might work fine after rebooting and remounting the drive and data.
14 |
15 | ## Step 2
16 |
17 | Investigate the issue further - if the error is related to network settings, UPnP settings, tor failure, etc... the suggestions below may not help and it would need to be investigated further.
18 |
19 | ## Step 3 - Data Corruption
20 |
21 | If the error does appear to be related to corruption (most Bitcoin errors are), the next step is to "Reset Blockchain" which will delete the blockchain data and re-sync it. This may take several days. Any of the corrupt data will be replaced with freshly downloaded data.
22 |
23 | ## Step 4 - Data Corruption
24 |
25 | Finally, the last option is to try a new drive or other hardware. If you have a hard drive, you may want to upgrade to an SSD to reduce load and sync faster. If you had been getting Undervoltage or Throttling errors, a new power supply or new device may also help.
--------------------------------------------------------------------------------
/docs/troubleshooting/bitcoin-sync-slow.md:
--------------------------------------------------------------------------------
1 | # Bitcoin is Syncing Slowly
2 |
3 | There are numerous reasons your device may appear to be syncing the Bitcoin blockchain slowly. If your device is syncing slowly, here are several suggestions to try and speed things up.
4 |
5 | Even with slow internet speed, slow external drives, or slow Internet, the early blocks in a device's IBD (Initial Blockchain Download) may still appear to sync quickly. However, once the device has progressed to block ~450k, sync times will slow down significantly.
6 |
7 | ## Using a Hard Drive
8 |
9 | Earlier on in Bitcoin, hard drives could be used for Bitcoin nodes since the chain was much smaller. Now that the chain is over 720,000 and the size is over 400GB, hard drives are not fast enough to keep up.
10 |
11 | It is recommended to upgrade to a Solid State Drive (SSD) for much better performance.
12 |
13 | Try using the recommended hardware on [mynodebtc.com/download](https://mynodebtc.com/download).
14 |
15 | ## Using the wrong USB Port
16 |
17 | On Raspberry Pi 4 devices, there are USB ports for USB 2 (black) and USB 3 (blue). USB 3 provides much better performance. Ensure you are using a USB 3 port.
18 |
19 | ## Slow Tor Connection
20 |
21 | Another reason for slow syncing is a bad tor connection. MyNode uses tor by default and if your connection or Bitcoin peers are slow, you may also experience slow sync times.
22 |
23 | First, just try rebooting. You should get a new tor connection and may find new Bitcoin peers.
24 |
25 | Second, if that doesn't seem to help. You can also disable Tor for Bitcoin and Lightning on the settings page. That will use clearnet for syncing the Bitcoin Blockchain, which can be much more performant. We have a guide on toggling tor/clearnet available [here](/networking/tor).
26 |
27 | ## Unsupported USB -> SATA Adapter for SSD
28 |
29 | Some enclosures or adapters for Solid State drives (SSDs) are not well supported by the Raspberry Pi OS. This can lead to slow sync times or possible data corruption. The recommended adapter listed on [mynodebtc.com/download](https://mynodebtc.com/download) has been known to work well.
--------------------------------------------------------------------------------
/docs/troubleshooting/device-not-booting.md:
--------------------------------------------------------------------------------
1 | # My Device is not Booting
2 |
3 | If your device does not appear to be booting, there can be several causes. Following these steps should help resolve the issue.
4 |
5 | ## Step 1 - Reboot
6 |
7 | In rare cases, software bugs may prevent the user interface from loading, making it appear like the the device has not started or shut off. First, verify the lights of the device are on. If not, the power adapter may be bad or may have come loose or the device may have died. Either way, disconnect the power cable and reconnect it to the device. If the lights do not appear on the device or Ethernet cable within 60 seconds, there is likely a hardware failure with the power cable or device.
8 |
9 | For more information on diagnosing Raspberry Pi 4 LEDs, visit this link.
10 |
11 | [LED Codes](https://elinux.org/R-Pi_Troubleshooting#Normal_LED_status)
12 |
13 | ## Step 2 - Find the IP Address
14 |
15 | If the device lights come on, try connecting to the device via the web UI again via mynode.local as well as the IP address. How to find the [device IP address](/advanced/find-device-ip.html).
16 |
17 | If those tools cannot find an IP address, then the device may not be booting properly or not connecting to the network.
18 |
19 | ## Step 3 - Connect Keyboard and Monitor (optional)
20 |
21 | Another option to help diagnose some issues, is to connect a keyboard and monitor to the device. After connecting the additional hardware, reboot the device and watch the monitor. It may show error messages that indicate the operating system cannot start, which can mean SD card failure, corruption, or operating system upgrade failures. If error messages appear, go to step 4 and try re-flashing the SD card.
22 |
23 | If a login prompt appears, try logging in with the username admin and your MyNode password. After logging in, you should see an IP address in the banner to use to connect to the user interface. If no IP address appears or the interface still cannot connect, you likely have a network issue preventing access. Going to step 4 may help resolve the issue, but it is more likely a different issue related to networking or failed hardware.
24 |
25 | ## Step 4 - Reflash SD Card
26 |
27 | If the device has lights, proving it has power, the next thing to try is to re-flash the SD card. Some failed operating system updates, power outages, or SD card corruption can prevent the device from booting and be resolved by loading a fresh copy of the software. The MyNode software was designed to limit the impact of this as much as possible. Nearly all ciritical data is stored on the external drive, so re-flashing the SD card will have limited side effects.
28 |
29 | Download link and basic instructions for re-flashing are available on the MyNode [download page](https://mynodebtc.com/download). A full guide on how to re-flash an SD card is also available [here](/advanced/flash-sd-card).
30 |
31 | ## Step 5 - Replace hardware
32 |
33 | If all other steps have failed or the device does not light up, hardware failure may be to blame. Replacing the following parts may help.
34 |
35 | - Power Supply (if not powering up)
36 | - SD Card (if not booting properly, but powering up)
37 | - Raspberry Pi / Other Device (if not booting properly or not powering up)
--------------------------------------------------------------------------------
/docs/troubleshooting/drive-not-found.md:
--------------------------------------------------------------------------------
1 | # My Device cannot Find the Drive
2 |
3 | Some users may encouter an issue where the drive cannot be found even though it is attached. This is likely due to power or driver issues related to the external disk drive.
4 |
5 | ## Hard Disk Drive
6 |
7 | If you are using a hard drive, you may need to provide more power to the drive. During disk startup it requires a large amount of power and this can cause the device to hang or fail. It can also lead to data corruption, which can cause other issues down the line.
8 |
9 | If you experience this issue and have a hard drive, try using a USB Y cable or powered USB hub to power the drive.
10 |
11 | A powered USB hub will let the drive pull power from two USB ports and a powered USB hub will provide an additional power supply for powering the drive. Here are two recommeded options.
12 |
13 | + [USB Y Cable](https://amzn.to/2SMixF7)
14 | + [Powered USB Hub](https://amzn.to/3idx5bn)
15 |
16 | Once updating your drive connection and power, it is recommended to reset the blockchain to restart QuickSync to avoid any issues with previously corrupted data.
17 |
18 | Alternatively, you can try using a USB 2 port or different port on your device.
19 |
20 | ## Solid State Drive
21 |
22 | If you are using a solid state drive, power is probably NOT the issue. The issue is more likely to be poor driver support for the specific USB -> SATA adapter you are using.
23 |
24 | To resolve this, you have two options. First, you can try plugging your drive into a USB 2 port (black) on the device. This will typically revert the driver back to the older, but more consistent, version and help avoid issues. If that doesn't work, or you want to continue using USB 3, try using a recommeded USB->SATA adapter that has worked well for users in the past.
25 |
26 | **Recommeded Adapters**
27 |
28 | + [UGREEN External Drive Enclosure](https://amzn.to/3b2gowf)
29 |
30 | Once updating your drive connection, it is recommended to reset the blockchain to restart IBD to avoid any issues with previously corrupted data.
31 |
32 |
--------------------------------------------------------------------------------
/docs/troubleshooting/drive-readonly-error.md:
--------------------------------------------------------------------------------
1 | # My Device has a Drive Error
2 |
3 | If your device gets into a state indicating "Drive Error" it means an error has been detected on the external drive and the device cannot properly read and write data.
4 |
5 | The error will popup and appear like this.
6 |
7 |
8 |
9 |
10 |
11 |
12 |
13 | ## Step 1
14 |
15 | First, try rebooting the device and monitor to see if the error comes back. If so, there may be corruption on the external drive preventing it from working properly.
16 |
17 | ## Step 2 - Remount the External Drive
18 |
19 | The next thing to try is to remount the external drive via the settings page. Under the Advanced section, there is a button to remount the drive, which may make it read/write again and ready for use.
20 |
21 |
22 |
23 |
24 |
25 |
26 |
27 | ## Step 3 - Investigate the USB adapter
28 |
29 | If that still does not work, your drive may be suffering from a USB -> SATA adapter that is not well supported. Try replacing it with one that has been well tested.
30 |
31 | **Recommeded Adapters**
32 |
33 | + [UGREEN External Drive Enclosure](https://amzn.to/3b2gowf)
34 |
35 | ## Step 4 - Format the Drive
36 |
37 | In some cases, the data on the external drive has been corrupted causing the drive to be unusable. This may have been caused by power outages or certain hardware, like from step 3. In this case, you can format the drive to get back up and running.
38 |
39 | **NOTE:** Ensure you have backed up all wallet information, seed phrases, and static channel backup files prior to formatting your drive. This action CANNOT be undone!
40 |
41 |
42 |
43 |
44 |
45 |
46 |
47 | After rebooting, the drive will format and your device will begin syncing the blockchain again. If you had a Lighting wallet, you can re-import the wallet by following the [Restore Lightning Wallet](/lightning/restore) guide.
--------------------------------------------------------------------------------
/docs/troubleshooting/electrum-connection-error.md:
--------------------------------------------------------------------------------
1 | # My Electrum Wallet is not Connecting
2 |
3 | If you run into issues connecting your Electrum wallet to the Electrum server running on MyNode, there are several steps you can perform to resolve common issues.
4 |
5 | ## Verify Configuration
6 |
7 | First, verify that your IP address matches exactly in your Electrum wallet settings. The port specified in the interface should be 50002.
8 |
9 | ## Verify Electrum Server is Running
10 |
11 | Verify Electrum status icon on the MyNode home screen is green and the status is Running. On the status page, verify that there are no obvious errors in the Electrum Server log.
12 |
13 | ## Clear Electrum Wallet Certificates
14 |
15 | If your device has changed IP addresses or your Electrum data was cleared, you client may have cached an old certificate and is preventing the connection. On your PC or laptop running the electrum wallet, find the electrum data folder.
16 |
17 | To find your Electrum files, try [these instructions](https://electrum.readthedocs.io/en/latest/faq.html#where-is-my-wallet-file-located).
18 |
19 | Under the data folder, there should be a folder for certificates. Delete all the certificates and try connecting again.
20 |
21 | ## Try an Insecure Connection
22 |
23 | To connect directly to the Electrum server, try using port 50001. This will avoid the proxy that verifies the certificates.
24 |
25 | First, find your Electrum config file for your application and change some settings.
26 |
27 | To find your Electrum files, try [these instructions](https://electrum.readthedocs.io/en/latest/faq.html#where-is-my-wallet-file-located).
28 |
29 | Open the config file and make change the connection URL to: `[MyNode IP]:50001:t`
30 |
31 | Restart Electrum and you will be using MyNode for trusted Electrum access!
--------------------------------------------------------------------------------
/docs/troubleshooting/fsck-error.md:
--------------------------------------------------------------------------------
1 | # My Device has a Filesystem Error
2 |
3 | If your device displays a message indicating a filesystem or "fsck" error, it means the device has automatically detected an error on the external drive. In many cases, it will automatically resolve the issue and you will need to click "OK" to dismiss the message.
4 |
5 | The error will popup and appear like this on the main MyNode page.
6 |
7 |
8 |
9 |
10 |
11 |
12 |
13 | ## Concern
14 |
15 | While data corrption is not a good thing, if this issue has only happened once, it may be nothing to worry about. If the message has appeared several times, it may warrant more investigation.
16 |
17 | If the issue has appeared multiple times and you do not believe the hardware to be bad, you may need to reformat the external drive to get back to working condition. Some data corruption cannot be automatically recovered. This option is available via the settings page.
18 |
19 | ## Causes
20 |
21 | ### Power Outages
22 |
23 | First, this issue can be caused by power outages when the drive was in the middle of writing a file and power was lost. If that is the case or your area experiences frequent power outages, you may want to look into putting your device on a battery backup to prevent data corruption.
24 |
25 | ### Unsupported USB -> SATA Adapter
26 |
27 | Your drive may be suffering from a USB -> SATA adapter that is not well supported. Try replacing it with one that has been well tested.
28 |
29 | **Recommeded Adapters**
30 |
31 | + [UGREEN External Drive Enclosure](https://amzn.to/3b2gowf)
32 |
33 | ### Failing Drive
34 |
35 | This issue can also be caused by a failing drive. This can be a hardware failure or by corruption that cannot be automatically recovered.
36 |
37 | ### Hardware Failure
38 |
39 | Finally, this can be caused by other hardware going bad. It can be related to power supply problems, a bad device, or the drive itself going bad. To verify other hardware is working, you can detach the drive and let the device run for 24-48 hours while monitoring the uptime on the settings page. Verify the uptime does not get reset back to 0, indicating the device rebooted on its own.
--------------------------------------------------------------------------------
/docs/troubleshooting/https-error.md:
--------------------------------------------------------------------------------
1 | # My Web Browser shows an Error
2 |
3 | When you first connect to your node, it may use HTTP which is less secure than HTTPS. Most users will want to start using HTTPS by clicking the lock icon in the top right of the home page, once it loads.
4 |
5 | ## You see a "Your connection is not Private" Error
6 |
7 | Some users browsers will show an error and it may appear like MyNode interface cannot load. In most cases, the browser is warning you that the certificate is unknown to the browser because the certifcate being used is self-signed by the device. Since the MyNode interface is not a public website, the browser can't verify the validity of the certificate, like it does for public websites.
8 |
9 | You may see an error similar to this.
10 |
11 |
12 |
13 |
14 |
15 |
16 |
17 | First, click on the Advanced button to open more options.
18 |
19 |
20 |
21 |
22 |
23 |
24 |
25 | Then, click the proceed link. Even though it may say unsafe, the HTTPS certificate is still providing security between your browser and the device.
26 |
27 | ## You see an "Not Secure" Warning
28 |
29 | Even after accepting the certificate in the section above, you may still see a warning in your browser about the site not being secure, like below.
30 |
31 |
32 |
33 |
34 |
35 |
36 |
37 | This is caused by the same reason as above. The certificate is providing security between your browser and the device, but the web browser cannot verify the certificate came from a trusted source, like it does with public websites.
--------------------------------------------------------------------------------
/docs/troubleshooting/sd-card-full-error.md:
--------------------------------------------------------------------------------
1 | # My Device has SD Card Full Warning
2 | If your device is displaying a warning indicating the SD card is getting full, there are some several options to save space or upgrade to a larger SD card.
3 |
4 |
5 |
6 |
7 |
8 |
9 |
10 |
11 | ## Step 1 - Check the Usage
12 |
13 | First, check the app usage by visiting the Settings page. In the Status section, click on the "Show Details" button next to "OS Disk Usage".
14 |
15 |
16 |
17 |
18 |
19 |
20 |
21 | You should see details about the usage of a variety of folders, like this. Note any especially large folders.
22 |
23 |
24 |
25 |
26 |
27 |
28 |
29 | ## Step 2 - Uninstall Apps
30 |
31 | If you have any apps that you are not using, you can uninstall them and save a lot of space. Some that require the most space are RTL, Thunderhub, Caravan, and JoinMarket.
32 |
33 | To uninstall an app, click on the Applications button on the Home page. Then, click on the Uninstall button next to the app you would like to remove.
34 |
35 |
36 |
37 |
38 |
39 |
40 |
41 | ## Step 3 - Upgrade the SD card
42 |
43 | The simplest solution is to upgrade the SD card to a larger one. You can follow the instructions at mynodebtc.com/downoad and flash the software onto a new, larger SD card. A 64 GB SD card will be plenty large and only costs around $10 on Amazon.
44 |
45 | Steps
46 | - Flash software onto new SD card
47 | - Shut down device
48 | - Remove existing SD card and insert new one
49 | - Power device back on
50 | - Note: Password will be reset to bolt and some apps may need to be re-installed
51 |
--------------------------------------------------------------------------------
/docs/troubleshooting/sd-card-readonly-error.md:
--------------------------------------------------------------------------------
1 | # My Device has an SD Card Error
2 |
3 | If your device gets into a state indicating "SD Card Error" it means an error has been detected on the SD card and the device cannot properly read and write data.
4 |
5 | The error will popup and appear like one of these screenshots.
6 |
7 | **Screenshot 1**
8 |
9 |
10 |
11 |
12 |
13 |
14 | **Screenshot 2**
15 |
16 |
17 |
18 |
19 |
20 |
21 | ## Step 1
22 |
23 | First, try rebooting the device and monitor to see if the error comes back. If so, there may be corruption on the SD card preventing it from working properly.
24 |
25 | ## Step 2 - Re-flash the SD card
26 |
27 | The next thing to try is re-flashing the SD card. This will clear any corrupt data and write a fresh MyNode operating system to the SD card. All critical data is saved on the external drive, so you will not lose your Bitcoin or Lightning data.
28 |
29 | Detailed instructions available on the download page.
30 |
31 | - Shutdown device using the button on the settings page
32 | - Remove SD Card from Device
33 | - Re-flash the SD Card
34 | - Insert SD card back into the device
35 | - Power device back on (may need to remove and re-connect power cable)
36 | - Your password will also be reset to "bolt"!
37 |
38 | Note: This process may cause your device to get a new IP address.
39 |
40 | ## Step 3 - Replace the SD card
41 |
42 | If that still does not work, your SD card may have gone bad. You can easily get back up and running by replacing the SD card and repeating step 2.
--------------------------------------------------------------------------------
/docs/troubleshooting/stuck-copying-files.md:
--------------------------------------------------------------------------------
1 | # My Device is stuck at Copying Files
2 |
3 | Some users may encouter an issue where the "copying files" step of QuickSync stalls and gets stuck or will get to a point and then restart from 0%. This is likely due to power or driver issues related to the external disk drive.
4 |
5 | ### Hard Disk Drive
6 |
7 | If you are using a hard drive, you likely need to provide more power to the drive. Disk IO is very intense when extracting a 270+ GB file during the final stages of QuickSync and some drives draw more power than can be provided by a small device via USB. This can cause the device to hang or fail. It can also lead to data corruption, which can cause other issues down the line.
8 |
9 | If you experience this issue and have a hard drive, try using a USB Y cable or powered USB hub to power the drive.
10 |
11 | A powered USB hub will let the drive pull power from two USB ports and a powered USB hub will provide an additional power supply for powering the drive. Here are two recommeded options.
12 |
13 | + [USB Y Cable](https://amzn.to/2SMixF7)
14 | + [Powered USB Hub](https://amzn.to/3idx5bn)
15 |
16 | Once updating your drive connection and power, it is recommended to reset the blockchain to restart QuickSync to avoid any issues with previously corrupted data.
17 |
18 | ### Solid State Drive
19 |
20 | If you are using a solid state drive, power is probably NOT the issue. The issue is more likely to be poor driver support for the specific USB -> SATA adapter you are using.
21 |
22 | To resolve this, you have two options. First, you can try plugging your drive into a USB 2 port (black) on the device. This will typically revert the driver back to the older, but more consistent, version and help avoid issues. If that doesn't work, or you want to continue using USB 3, try using a recommeded USB->SATA adapter that has worked well for users in the past.
23 |
24 | **Recommeded Adapters**
25 |
26 | + [UGREEN External Drive Enclosure](https://amzn.to/3b2gowf)
27 |
28 | After updating your drive connection, it is recommended to reset the blockchain to restart IBD to avoid any issues with previously corrupted data.
29 |
--------------------------------------------------------------------------------
/docs/troubleshooting/stuck-formatting.md:
--------------------------------------------------------------------------------
1 | # My Device is stuck at Formatting Drive
2 |
3 | Some users may encouter an issue where the first step of setting up the external drive for use by MyNode stalls and becomes stuck. This is likely due to wither a loose cable connection or a USB to SATA adapter that is not well supported by the Raspberry Pi operating system.
4 |
5 | ### Loose Connections
6 |
7 | Verify the connection between USB and the drive is secure as well as the connection between the SSD and the adapter. The SATA connection between the adapter and drive is a common place that can be a bit loose and cause the drive to not work properly. Try disconnecting and securely re-connecting the drive and adapter.
8 |
9 | ### Solid State Drive
10 |
11 | If you are using a solid state drive, the issue is more likely to be poor driver support for the specific USB -> SATA adapter you are using.
12 |
13 | To resolve this, you have two options. First, you can try plugging your drive into a USB 2 port (black) on the device. This will typically revert the driver back to the older, but more consistent, version and help avoid issues. If that doesn't work, or you want to continue using USB 3, try using a recommeded USB->SATA adapter that has worked well for users in the past.
14 |
15 | **Recommeded Adapters**
16 |
17 | + [UGREEN External Drive Enclosure](https://amzn.to/3b2gowf)
18 |
19 | After updating your drive connection, you may need to use the Format Drive option on the settings page to trigger it to re-format the external drive.
20 |
--------------------------------------------------------------------------------
/docs/troubleshooting/voltage-error.md:
--------------------------------------------------------------------------------
1 | # My Device has a Voltage Error
2 |
3 | If your device gets into a state indicating "Device Undervoltage" it means a power issue has been detected by the hardware.
4 |
5 | The error will popup and appear like this.
6 |
7 |
8 |
9 |
10 |
11 |
12 |
13 | ## Step 1
14 |
15 | First, just try rebooting the device and monitor to see if the error comes back. An intermittent power problem may have been detected and there may be no long term issues.
16 |
17 | ## Step 2
18 |
19 | Another symptom to monitor for is the uptime of the device. If there are power issues, the device may be randomly rebooting as well, which increases the chances for data corruption.
20 |
21 | Check the uptime on the status or settings page every day for a few days and see if the amount of time decreases. If so, there may be a hardware issue. Check steps three and four.
22 |
23 | ## Step 3 - Bad Power Cable
24 |
25 | The power supply of the device may be bad and not providing less power. This is not very common, but is typically relatively inexpensive to replace or to try a backup power cable.
26 |
27 | A 5V 3.5A power supply is recommended. See the [download page](https://mynodebtc.com/download) for hardware recommendations.
28 |
29 | ## Step 4 - Bad Board
30 |
31 | Finally, the last option is to try replacing the board if you continue to see issues. This will be the priciest option, but is basically guaranteed to resolve the issue.
32 |
33 | See the [download page](https://mynodebtc.com/download) for hardware recommendations.
--------------------------------------------------------------------------------
/docs/videos/guides.md:
--------------------------------------------------------------------------------
1 | # Video Guides
2 | A number of video guides have been created by the amazing MyNode community detailing everything from how to get started to the details and setup of various features.
3 |
4 | ## Series
5 | Ministry of Nodes - MyNode Series
6 |
7 | ## Setup and Basics
8 | Parts and Assembly - BTC Sessions | Ministry of Nodes
9 |
10 | Connecting to your MyNode - BTC Sessions | Ministry of Nodes
11 |
12 | UI Basics - Ministry of Nodes
13 |
14 | Upgrading - Ministry of Nodes
15 |
16 | ## Features
17 | Electrum Server - Ministry of Nodes
18 |
19 | BTC RPC Explorer - Ministry of Nodes
20 |
21 | Lightning - Ministry of Nodes Part 1 - Part 2
22 |
23 | ## Using Hardware Wallets
24 | Coldcard - Ministry of Nodes
25 |
26 | ## Other
27 | Running MyNode as a Virtual Machine - Ministry of Nodes
--------------------------------------------------------------------------------
/docs/vpn/setup.md:
--------------------------------------------------------------------------------
1 | # Remote Access via VPN
2 |
3 | ## Enabling VPN on your MyNode
4 |
5 | #### Premium Feature
6 |
7 | VPN is a technology that allows devices to communicate securely over the Internet. This technology can be incredibly useful to Bitcoin and Lightning by securing connections between the devices you use everyday and your MyNode.
8 |
9 | By enabling VPN, you can use all your mobile Bitcoin apps on your phone or laptop, no matter where you are, and still rely on the trust your MyNode provides.
10 |
11 | In fact, when VPN is enabled on your mobile device, all traffic from your device will be securely sent to your MyNode. This can also help prevent snooping and monitoring of your traffic when on open WiFi connections.
12 |
13 | For more information on VPN, visit the VPN page on wikipedia.
14 |
15 | ## Open Port for VPN
16 |
17 | For VPN to work properly, you need to forward port 51194 on your router to port 51194 on your MyNode.
18 |
19 | First, you will need the IP address of your MyNode. Go to the settings page and find its local IP address.
20 |
21 |
22 |
23 |
24 |
25 |
26 |
27 | Then, go to your router and forward UDP port 51194 to port 51194 on the IP of your MyNode. It will look something like this, but every router is different.
28 |
29 |
30 |
31 |
32 |
33 |
34 |
35 | You can verify the port is being forwarded by checking port 51194 on a website like CanYouSeeMe.
36 |
37 | ## Connecting with VPN on your Android Device
38 |
39 | #### Premium Feature
40 |
41 | On your Android device, download and install OpenVPN.
42 |
43 | Next, on your mobile device, visit the MyNode web GUI while you are connected to your home WiFi. Go to the VPN page by clicking on "Info" under the VPN heading.
44 |
45 |
46 |
47 |
48 |
49 |
50 |
51 | Once on the VPN Info page, click on the button to download the OVPN File. Enter your password when the prompt appears. This will download the OpenVPN profile.
52 |
53 |
54 |
55 |
56 |
57 |
58 |
59 | Open the OpenVPN app and:
60 |
61 | 1. Tap on "OVPN Profile"
62 | 2. Tap on the "+" button and choose the recently downloaded file
63 | 3. Tap Import
64 | 4. Tap Add
65 |
66 | Once the profile was imported successfully, you can tap the toggle icon and connect to your MyNode securely via the Internet.
67 |
68 |
69 |
70 |
71 |
72 |
73 |
74 | Now, whenever you connect to your MyNode using OpenVPN, you will be able to access all the MyNode services as if you were on your home WiFi network!
75 |
--------------------------------------------------------------------------------
/package.json:
--------------------------------------------------------------------------------
1 | {
2 | "name": "MyNode-docs",
3 | "version": "1.0.0",
4 | "devDependencies": {
5 | "@vuepress/plugin-back-to-top": "^1.5.3",
6 | "@vuepress/plugin-google-analytics": "^1.8.2",
7 | "@vuepress/plugin-medium-zoom": "^1.5.3",
8 | "vuepress": "^1.5.3",
9 | "vuepress-plugin-minimal-analytics": "^0.1.4"
10 | },
11 | "scripts": {
12 | "docs:dev": "vuepress dev docs",
13 | "docs:build": "vuepress build docs"
14 | },
15 | "dependencies": {
16 | "vuepress-plugin-seo": "^0.1.4"
17 | }
18 | }
19 |
--------------------------------------------------------------------------------
12 | 
20 | 
28 | 
38 | 
46 | 
54 | 
12 | 
20 | 
28 | 
36 | 
44 | 
52 | 
60 | 
12 | 
20 | 
29 | 
44 | 
52 | 
60 | 
34 | 
52 | 
60 | 
68 | 
76 | 
84 | 
95 | 
25 | 
27 | 
39 | 
65 | 
10 | 
18 | 
22 | 
34 | 
10 | 
11 | 
10 | 
42 | 
12 | 
20 | 
30 | 
38 | 
48 | 
62 | 
72 | 
80 | 
88 | 
58 | 
66 | 
74 | 
4 | 
17 | 
26 | 
33 | 
40 | 
47 | 
54 | 
8 | 
16 | 
26 | 
10 | 
18 | 
26 | 
18 | 
18 | 
43 | 
44 | 
13 | 
21 | 
29 | 
41 | 
49 | 
57 | 
13 | 
21 | 
29 | 
37 | 
28 | 
29 | 
18 | 
23 | 
37 | 
53 | 
65 | 
77 | 
87 | 
40 | 
63 | 
71 | 
93 | 
26 | 
57 | 
16 | 
26 | 
18 | 
26 | 
34 | 
42 | 
10 | 
24 | 
44 | 
10 | 
14 | 
22 | 
34 | 
7 | 
18 | 
26 | 
38 | 
11 | 
18 | 
10 | 
24 | 
32 | 
48 | 
56 | 
71 |