| System | -Steps | -
| Windows | -
-
|
-
| Debian-based | -
-
|
-
| RedHat-based | -
-
|
-
| Any Linux distribution | -
-
|
-
-
-### Usage
-
-#### Main Menu
-When executing the Krux Installer, you will be presented with a menu of two items:
-
-
-
-
-#### Select Device
-First, select the device we want to flash. After that the menu will shown three items:
-
-
-
-
-
-#### Select Version
-This option allows you to select the latest official version or the latest beta version on our github. If the connection works, you will see the following screen:
-
-
-
-| **Version** | **Name** |**Advantages** | **Disadvantages** |
-|-------------|------------------------------------|-----------------------------------------------------------------------------------------------------------------------------------|-----------------------------------------------------------------|
-| Official | `selfcustody/krux/releases/tag/* ` |- Stable version;
- All features were reviewd and tested;
- It's integrity and authenticity can be verified. |
- Updates may take some time to be released.
- Latest features available;
- Constant UX reviews by our community.
- Its integrity or authenticity cannot be verified.
-
-----8<----
-flash-krux-logo.en.txt
-----8<----
-
-#### Wipe device
-
-This option **erases ALL data from the device's flash memory**. On Linux, it will prompt for your password before. Once the process starts, the screen will appear frozen. When it's done, you can scroll down and see all the events that occurred.
-
-> ⚠️ TIP: It's useful when your device is not working or for security reasons. To use Krux again, you'll need to re-flash the firmware.
-
-
-
-> ⚠️ TIP: Do not unplug or poweroff your device or computer. Wait until the process finishes.
-
-----8<----
-tips-after-install.en.txt
-----8<----
diff --git a/docs/getting-started/installing/from-gui/debian-like.en.md b/docs/getting-started/installing/from-gui/debian-like.en.md
new file mode 100644
index 000000000..ba91d337a
--- /dev/null
+++ b/docs/getting-started/installing/from-gui/debian-like.en.md
@@ -0,0 +1,56 @@
+# :material-debian: Download assets
+
+* [`{{latest_installer_deb}}`](https://github.com/selfcustody/krux-installer/releases/download/{{latest_installer}}/{{latest_installer_deb}})
+* [`{{latest_installer_deb}}.sha256.txt`](https://github.com/selfcustody/krux-installer/releases/download/{{latest_installer}}/{{latest_installer_deb}}.sha256.txt)
+* [`{{latest_installer_deb}}.sig`](https://github.com/selfcustody/krux-installer/releases/download/{{latest_installer}}/{{latest_installer_deb}}.sig)
+
+## Verify the integrity
+
+----8<----
+verify-the-integrity-explain.en.txt
+----8<----
+
+```bash
+sha256sum --check ./{{latest_installer_deb}}.sha256.txt
+```
+
+## Verify the authenticity
+
+----8<----
+verify-the-signature-explain.en.txt
+----8<----
+
+```bash
+gpg --verify ./{{latest_installer_deb}}.sig
+```
+
+----8<----
+verify-the-signature-tip.en.txt
+----8<----
+
+## Install
+
+**krux-installer** isn't available on Debian or Ubuntu repositories.
+Therefore, only the `apt-get install` command will not work.
+To install, it'll be necessary two steps:
+
+- Install the .deb package itself:
+
+```bash
+sudo dpkg -i {{latest_installer_deb}}
+```
+
+- Update the installed package:
+
+```bash
+sudo apt-get install -f {{latest_installer_deb}}
+```
+
+It will warn you that your system user was added to `dialout` group and maybe you need to reboot
+to activate the `sudoless` flash procedure.
+
+## After install
+
+----8<----
+after-install-installer.en.md
+----8<----
diff --git a/docs/getting-started/installing/from-gui/fedora-like.en.md b/docs/getting-started/installing/from-gui/fedora-like.en.md
new file mode 100644
index 000000000..a46201e4c
--- /dev/null
+++ b/docs/getting-started/installing/from-gui/fedora-like.en.md
@@ -0,0 +1,54 @@
+# :material-fedora: Download assets
+
+* [`{{latest_installer_rpm}}`](https://github.com/selfcustody/krux-installer/releases/download/{{latest_installer}}/{{latest_installer_rpm}})
+* [`{{latest_installer_rpm}}.sha256.txt`](https://github.com/selfcustody/krux-installer/releases/download/{{latest_installer}}/{{latest_installer_rpm}}.sha256.txt)
+* [`{{latest_installer_rpm}}.sig`](https://github.com/selfcustody/krux-installer/releases/download/{{latest_installer}}/{{latest_installer_rpm}}.sig)
+
+## Verify the integrity
+
+----8<----
+verify-the-integrity-explain.en.txt
+----8<----
+
+```bash
+sha256sum --check ./{{latest_installer_rpm}}.sha256.txt
+```
+
+## Verify the authenticity
+
+----8<----
+verify-the-signature-explain.en.txt
+----8<----
+
+```bash
+gpg --verify ./{{latest_installer_rpm}}.sig
+```
+
+----8<----
+verify-the-signature-tip.en.txt
+----8<----
+
+## Install
+
+**krux-installer** isn't available on Fedora or RedHat repositories. You'll need to add it manually:
+
+### Fedora
+
+```bash
+sudo dnf install {{latest_installer_rpm}}
+```
+
+### Other RedHat based distros:
+
+```bash
+sudo yum localinstall {{latest_installer_rpm}}
+```
+
+It will warn you that your system user was added to `dialout` group and maybe you need to reboot
+to activate the `sudoless` flash procedure.
+
+## After install
+
+----8<----
+after-install-installer.en.md
+----8<----
diff --git a/docs/getting-started/installing/from-gui/index.en.md b/docs/getting-started/installing/from-gui/index.en.md
new file mode 100644
index 000000000..3ffa1474b
--- /dev/null
+++ b/docs/getting-started/installing/from-gui/index.en.md
@@ -0,0 +1,15 @@
+You can install Krux (both official or beta releases) onto your K210-based device using our
+official desktop application, [KruxInstaller](https://github.com/selfcustody/krux-installer),
+available for:
+
+> ⚠️ WARNING: Krux-Installer latest version is in it's alpha version. Maybe you can experience
+> bugs or don't like something. If it is the case, please submit a
+[issue](https://github.com/selfcustody/krux-installer/issues).
+
+- [:material-microsoft-windows: Windows](./windows.en.md)
+- [:material-apple: MacOS Intel](./macos-intel.en.md)
+- [:material-apple: MacOS M1/M2/M3](./macos-arm64.en.md)
+- [:material-debian: Debian and like](./debian-like.en.md)
+- [:material-fedora: Fedora and like](./fedora-like.en.md)
+- [:material-linux: Other linux distros](./other-linux-distro.en.md)
+
diff --git a/docs/getting-started/installing/from-gui/macos-arm64.en.md b/docs/getting-started/installing/from-gui/macos-arm64.en.md
new file mode 100644
index 000000000..1a5cf625d
--- /dev/null
+++ b/docs/getting-started/installing/from-gui/macos-arm64.en.md
@@ -0,0 +1,41 @@
+# :material-apple: Download assets
+
+* [`{{latest_installer_mac_arm}}`](https://github.com/selfcustody/krux-installer/releases/download/{{latest_installer}}/{{latest_installer_mac_arm}})
+* [`{{latest_installer_mac_arm}}.sha256.txt`](https://github.com/selfcustody/krux-installer/releases/download/{{latest_installer}}/{{latest_installer_mac_arm}}.sha256.txt)
+* [`{{latest_installer_mac_arm}}.sig`](https://github.com/selfcustody/krux-installer/releases/download/{{latest_installer}}/{{latest_installer_mac_arm}}.sig)
+
+## Verify the integrity
+
+----8<----
+verify-the-integrity-explain.en.txt
+----8<----
+
+```bash
+sha256sum --check ./{{latest_installer_mac_arm}}.sha256.txt
+```
+
+## Verify the authenticity
+
+----8<----
+verify-the-signature-explain.en.txt
+----8<----
+
+```bash
+gpg --verify ./{{latest_installer_mac_arm}}.sig
+```
+
+----8<----
+verify-the-signature-tip.en.txt
+----8<----
+
+## Install
+
+----8<----
+install-installer-macos.en.txt
+----8<----
+
+## After install
+
+----8<----
+after-install-installer.en.md
+----8<----
diff --git a/docs/getting-started/installing/from-gui/macos-intel.en.md b/docs/getting-started/installing/from-gui/macos-intel.en.md
new file mode 100644
index 000000000..44a17d984
--- /dev/null
+++ b/docs/getting-started/installing/from-gui/macos-intel.en.md
@@ -0,0 +1,41 @@
+# :material-apple: Download assets
+
+* [`{{latest_installer_mac_intel}}`](https://github.com/selfcustody/krux-installer/releases/download/{{latest_installer}}/{{latest_installer_mac_intel}})
+* [`{{latest_installer_mac_intel}}.sha256.txt`](https://github.com/selfcustody/krux-installer/releases/download/{{latest_installer}}/{{latest_installer_mac_intel}}.sha256.txt)
+* [`{{latest_installer_mac_intel}}.sig`](https://github.com/selfcustody/krux-installer/releases/download/{{latest_installer}}/{{latest_installer_mac_intel}}.sig)
+
+## Verify the integrity
+
+----8<----
+verify-the-integrity-explain.en.txt
+----8<----
+
+```bash
+sha256sum --check ./{{latest_installer_mac_intel}}.sha256.txt
+```
+
+## Verify the authenticity
+
+----8<----
+verify-the-signature-explain.en.txt
+----8<----
+
+```bash
+gpg --verify ./{{latest_installer_mac_intel}}.sig
+```
+
+----8<----
+verify-the-signature-tip.en.txt
+----8<----
+
+## Install
+
+----8<----
+install-installer-macos.en.txt
+----8<----
+
+## After install
+
+----8<----
+after-install-installer.en.md
+----8<----
diff --git a/docs/getting-started/installing/from-gui/other-linux-distro.en.md b/docs/getting-started/installing/from-gui/other-linux-distro.en.md
new file mode 100644
index 000000000..4634e2a10
--- /dev/null
+++ b/docs/getting-started/installing/from-gui/other-linux-distro.en.md
@@ -0,0 +1,58 @@
+# :material-linux: Download assets
+
+For this installation, we'll use the `.deb` sources:
+
+* [`{{latest_installer_deb}}`](https://github.com/selfcustody/krux-installer/releases/download/{{latest_installer}}/{{latest_installer_deb}})
+* [`{{latest_installer_deb}}.sha256.txt`](https://github.com/selfcustody/krux-installer/releases/download/{{latest_installer}}/{{latest_installer_deb}}.sha256.txt)
+* [`{{latest_installer_deb}}.sig`](https://github.com/selfcustody/krux-installer/releases/download/{{latest_installer}}/{{latest_installer_deb}}.sig)
+
+## Verify the integrity
+
+----8<----
+verify-the-integrity-explain.en.txt
+----8<----
+
+```bash
+sha256sum --check ./{{latest_installer_deb}}.sha256.txt
+```
+
+## Verify the authenticity
+
+----8<----
+verify-the-signature-explain.en.txt
+----8<----
+
+```bash
+gpg --verify ./{{latest_installer_deb}}.sig
+```
+
+----8<----
+verify-the-signature-tip.en.txt
+----8<----
+
+## Install
+
+This step it's not really an installation.
+At least it will make the program's binary available somewhere on your computer;
+it can be useful if you want to develop a package for your distro.
+
+To do this you'll need two tools:
+
+* [`ar`](https://linux.die.net/man/1/ar);
+* [`bsdtar`](https://man.archlinux.org/man/bsdtar.1).
+
+### Extract contents
+
+- Extract the `.deb` contents:
+
+```bash
+ar xv {{latest_installer_deb}}
+```
+
+- Extract the `data.tar.zst` contents:
+
+```bash
+bsdtar -xvf data.tar.zst
+```
+
+The binary will be located at `./usr/local/bin/krux-installer`.
diff --git a/docs/getting-started/installing/from-gui/usage.en.md b/docs/getting-started/installing/from-gui/usage.en.md
new file mode 100644
index 000000000..94ca1a418
--- /dev/null
+++ b/docs/getting-started/installing/from-gui/usage.en.md
@@ -0,0 +1,219 @@
+This guide will walk through the basic use of the installer. At startup, it can differ in some
+operational systems. In the rest, the procedures will be similar.
+
+### Main Menu
+When executing the Krux Installer, you will be presented with a menu of 4 enabled buttons and
+two disabled buttons:
+
+
+
+* Enabled buttons:
+ * `Version`: select a firmware version;
+
+ * `Device`: select a supported device for the selected version;
+
+ * `Settings`: change some application settings;
+
+ * `About`: just show some information about the application.
+
+* Disabled buttons:
+
+ * `Flash firmware`: This button will start the flash firmware procedure;
+
+ * It will be enabled when user select **both** version and device;
+
+ * `Wipe device`: This button will start the wipe device procedure.
+
+ * It will be enabled when user select the device.
+
+### Select version
+
+At startup, the application will setup it to the latest one, `{{latest_krux}}`. But you can select
+even a beta release or older versions:
+
+
+
+* Click in the button that show the text `Version: {{latest_krux}}`;
+
+* To select a beta release, click on button that show the text `odudex/krux_binaries`;
+
+* To select an older version, click on button that show the text `Old versions`;
+
+#### Beta release
+
+After choose `odudex/krux_binaries`, you'll be warned with a message:
+
+
+
+#### Older versions
+
+* We put this option in case you have any interest in the history of firmware development;
+
+
+
+* Each version supports one device or the other;
+
+* For example: the version `v22.03.0` has support only for `m5stickv`.
+
+
+### Settings
+
+**krux-Installer** will give to you some freedom of choices for:
+
+* Krux-Installer settings;
+
+* General settings;
+
+#### krux-installer specific settings
+
+Here you can configure some of the specifics of krux firmare, like:
+
+
+
+* Where you'll save downloaded assets;
+
+* The flash baudrate
+
+* The natural language that will be used in the application ([system locale](https://en.wikipedia.org/wiki/Locale_(computer_software))).
+
+##### Flash baudrate
+The flash baudrate is how quickly the firmware will be written to the device.
+
+
+
+But not any value can be used. The valid ones are: 9600, 19200, 28800, 38400, 57600, 76800, 115200,
+230400, 460800, 576000, 921600, 1500000.
+
+##### System locale
+
+At startup, **krux-installer** recognize the locale used in your system. If your language isn't supported, it will defaults to `en_US`.
+
+
+
+
+### Select Device
+
+Everytime you select a new version, you'll see that the device button will be
+reseted to `Device: select a new one` state. Once a version is selected you can choose a device
+on which the firmware will be written.
+
+First, select the device we want to flash. After that the menu will shown three items:
+
+
+
+Note that some devices may be disabled if they are not supported by the chosen version
+
+### Flash device
+
+Once you choose the device and version, it enables the "flash device" button. It will start an
+**automatic** process of:
+
+* For official firmware's releases:
+
+ * Warning;
+
+ * Download;
+
+ * Verification:
+
+ * Unzip the correct firmware;
+
+ * The flash itself;
+
+* For beta releases:
+
+ * Download asset;
+
+ * The flash itself;
+
+#### Warning
+
+If you already downloaded assets, you'll be warned about this and will be offered the possibility
+to download again or continue without downloading:
+
+
+
+#### Download
+
+Krux-installer download can download four assets for official releases or one for beta releases.
+
+##### Official releases
+
+* A `zip` file containing all firmwares for each device;
+
+* Download a `zip.sha256.txt` file containing a `zip`'s digital fingerprint;
+
+* Download a `zip.sig` file containing a `zip`'s digital signature;
+
+* Download the `selfcustody.pem` file containing a public key certificate, signed by `odudex`;
+
+
+
+##### Beta releases
+
+* A `kfpkg` file containing the specific firmware for choosen device;
+
+
+
+#### Verification
+
+* Integrity verification compares the computed hash of `zip` against thei provided `zip.sha256.txt`;
+
+* Authenticity verification check if the `zip` file was really signed by `odudex`, using
+the `zip.sig` and `selfcustody.pem`.
+
+
+
+
+#### Unzip
+
+Now you will be able to select if you do a flash process or need to do an airgap process (soon):
+
+
+
+#### Flash
+
+When flash starts, it will warn you to **not disconnect the device until the process is complete**.
+You'll be able to see the flash progress:
+
+
+> ⚠️ TIP: You must connect and turn on your device **before click extract and flashing starts!**.
+
+As well a done icon:
+
+
+
+> ⚠️ TIP:
+----8<----
+flash-krux-logo.en.txt
+----8<----
+
+### Wipe device
+
+This is two step process:
+
+* Warning
+
+* Wipe
+
+#### Warning
+
+Before the wipe starts, it will show to you a message:
+
+
+> ⚠️ TIP: It's useful when your device is not working or for security reasons.
+To use Krux again, you'll need to re-flash the firmware.
+
+#### Wipe
+
+Once the process starts, the screen will appear frozen and a spinner will keep moving.
+When it's done, you can scroll down you will see a `check` icon.
+
+
+> ⚠️ TIP: Do not unplug or poweroff your device or computer. Wait until the process finishes.
+
+## Tips after install
+
+----8<----
+tips-after-install.en.txt
+----8<----
diff --git a/docs/getting-started/installing/from-gui/windows.en.md b/docs/getting-started/installing/from-gui/windows.en.md
new file mode 100644
index 000000000..e38faf26f
--- /dev/null
+++ b/docs/getting-started/installing/from-gui/windows.en.md
@@ -0,0 +1,53 @@
+# :material-microsoft-windows: Download assets
+
+* [`{{latest_installer_win}}`](https://github.com/selfcustody/krux-installer/releases/download/{{latest_installer}}/{{latest_installer_win}})
+* [`{{latest_installer_win}}.sha256.txt`](https://github.com/selfcustody/krux-installer/releases/download/{{latest_installer}}/{{latest_installer_win}}.sha256.txt)
+* [`{{latest_installer_win}}.sig`](https://github.com/selfcustody/krux-installer/releases/download/{{latest_installer}}/{{latest_installer_win}}.sig)
+
+## Verify the integrity
+
+----8<----
+verify-the-integrity-explain.en.txt
+----8<----
+
+```pwsh
+(Get-FileHash '.\{{latest_installer_win}}').Hash -eq (Get-Content '.\{{latest_installer_win}}')
+```
+
+## Verify the authenticity
+
+* You'll need have [GPG](https://gnupg.org/) installed;
+* We recommend installing [GPG4Win](https://www.gpg4win.org/).
+
+----8<----
+verify-the-signature-explain.en.txt
+----8<----
+
+```pwsh
+gpg --verify ./{{latest_installer_win}}.sig
+```
+
+----8<----
+verify-the-signature-tip.en.txt
+----8<----
+
+## Install
+
+Execute the `{{latest_installer_win}}`. You'll be faced with a blue window saying
+"Windows protected your PC". This occurs because we don't have a
+[code signing certificate](https://signmycode.com/resources/how-to-sign-an-exe-or-windows-application):
+
+
+
+----8<----
+verify-the-signature-trust-tip.en.txt
+----8<----
+
+Follow the installer's instructions to complete the installation. At the end, click on
+"Create desktop icon":
+
+## After install
+
+----8<----
+after-install-installer.en.md
+----8<----
diff --git a/docs/getting-started/installing/from-pre-built-release.en.md b/docs/getting-started/installing/from-pre-built-release.en.md
index eafa59601..9fa180adb 100644
--- a/docs/getting-started/installing/from-pre-built-release.en.md
+++ b/docs/getting-started/installing/from-pre-built-release.en.md
@@ -6,13 +6,13 @@ Head over to the [releases](https://github.com/selfcustody/krux/releases) page a
### Verify the files
Before installing the release, it's a good idea to check that:
-1. The *SHA256 hash* of `krux-vX.Y.Z.zip` matches the hash in `krux-vX.Y.Z.zip.sha256.txt`
-2. The *signature file* `krux-vX.Y.Z.zip.sig` can be verified with the [`selfcustody.pem` public key](https://github.com/selfcustody/krux/blob/main/selfcustody.pem) found in the root of the krux repository.
+1. The *SHA256 hash* of `{{latest_krux}}.zip` matches the hash in `{{latest_krux}}.zip.sha256.txt`
+2. The *signature file* `{{latest_krux}}.zip.sig` can be verified with the [`selfcustody.pem` public key](https://github.com/selfcustody/krux/blob/main/selfcustody.pem) found in the root of the krux repository.
You can either do this manually or with the `krux` shell script, which contains helper commands for this:
```bash
-./krux sha256 krux-vX.Y.Z.zip
-./krux verify krux-vX.Y.Z.zip selfcustody.pem
+./krux sha256 {{latest_krux}}.zip
+./krux verify {{latest_krux}}.zip selfcustody.pem
```
On Mac you may need to install `coreutils` to be able to use `sha256sum`
@@ -25,7 +25,7 @@ Fun fact: Each Krux release is signed with Krux!
### Flash the firmware onto the device
Extract the latest version of Krux you downloaded and enter the folder:
```bash
-unzip krux-vX.Y.Z.zip && cd krux-vX.Y.Z
+unzip {{latest_krux}}.zip && cd {{latest_krux}}
```
Connect the device to your computer via USB (for Maix Amigo, make sure you’re using bottom port), power it on, and run the following, replacing `DEVICE` with either `m5stickv`, `amigo`, `bit`, `cube`, `dock` or `yahboom` (to yahboom you may need to manually specify the port, for example `/dev/ttyUSB0` on Linux or `COM6` on Windows):
diff --git a/docs/getting-started/installing/from-source.en.md b/docs/getting-started/installing/from-source.en.md
index 6ab049bb9..6ea5269a3 100644
--- a/docs/getting-started/installing/from-source.en.md
+++ b/docs/getting-started/installing/from-source.en.md
@@ -29,7 +29,7 @@ The first command will create `privkey.pem` and `pubkey.pem` files you can use w
Once you've updated the `SIGNER_PUBKEY` with this value, you can proceed with the regular build process.
### Build the firmware (Linux or WSL)
-The [krux](https://github.com/selfcustody/krux/blob/main/krux) bash script contains commands for common development tasks. It assumes a Linux host, you will need to have [Docker Desktop or Docker Engine](https://docs.docker.com/desktop/), `openssl`, and `wget` installed at a minimum for the commands to work as expected. It works on Windows using WSL. The channel Crypto Guide from Youtube made a step-by-step video - [Krux DIY Bitcoin Signer: Build From Source & Verify (With Windows + WSL2 + Docker)](https://www.youtube.com/watch?v=Vmr_TFy2TfQ)
+The [krux bash script](https://github.com/selfcustody/krux/blob/main/krux) contains commands for common development tasks. It assumes a Linux host, you will need to have [Docker Desktop or Docker Engine](https://docs.docker.com/desktop/), `openssl`, and `wget` installed at a minimum for the commands to work as expected. It works on Windows using WSL. The channel Crypto Guide from Youtube made a step-by-step video - [Krux DIY Bitcoin Signer: Build From Source & Verify (With Windows + WSL2 + Docker)](https://www.youtube.com/watch?v=Vmr_TFy2TfQ)
To build and flash the firmware:
```bash
diff --git a/docs/getting-started/installing/from-test-release.en.md b/docs/getting-started/installing/from-test-release.en.md
index 542b54863..4a4f19e92 100644
--- a/docs/getting-started/installing/from-test-release.en.md
+++ b/docs/getting-started/installing/from-test-release.en.md
@@ -7,7 +7,7 @@ Keep in mind that these are unsigned binaries.
Download experimental compiled firmware or the Android app `apk` from our [test (beta) repository](https://github.com/odudex/krux_binaries).
#### Android
-The Krux Android app is designed for learning about Krux and Bitcoin air-gapped transactions. Due to the numerous potential vulnerabilities inherent in smartphones, such as the lack of control over the operating system, libraries, and hardware peripherals, the Krux app should NOT be used to manage wallets containing savings or important keys and mnemonics. For secure management of your keys, a dedicated device is recommended. [More](../../faq.md#what-is-krux-android-app)
+The [Krux Android app](../../faq.md#what-is-krux-android-app) is designed for learning about Krux and Bitcoin air-gapped transactions. Due to the numerous potential vulnerabilities inherent in smartphones, such as the lack of control over the operating system, libraries, and hardware peripherals, the Krux app should NOT be used to manage wallets containing savings or important keys and mnemonics. For secure management of your keys, a dedicated device is recommended.
#### Compiled firmware for Kendryte K210 devices
#### M5StickV
@@ -110,17 +110,17 @@ To Flash Yahboom k210 module you'll have to manually specify the port.
##### Linux
See the correct port using `ls /dev/ttyUSB*`, in the example below we use `/dev/ttyUSB0`:
```bash
-./ktool-linux -B goE -b 1500000 -p /dev/ttyUSB0 yahboom/kboot.kfpkg
+./ktool-linux -B goE -b 1500000 -p /dev/ttyUSB0 maixpy_yahboom/kboot.kfpkg
```
##### Mac
See the correct port using the command line: `ls /dev/cu.usbserial*`, in the example below we use `/dev/cu.usbserial-10`:
```bash
-./ktool-mac -B goE -b 1500000 -p /dev/cu.usbserial-10 yahboom/kboot.kfpkg
+./ktool-mac -B goE -b 1500000 -p /dev/cu.usbserial-10 maixpy_yahboom/kboot.kfpkg
```
##### Windows
See the correct port at Device Manager > Ports (COM & LPT), in the example below we use `COM6`:
```pwsh
-.\ktool-win.exe -B goE -b 1500000 -p COM6 yahboom\kboot.kfpkg
+.\ktool-win.exe -B goE -b 1500000 -p COM6 maixpy_yahboom\kboot.kfpkg
```
diff --git a/docs/getting-started/installing/index.en.md b/docs/getting-started/installing/index.en.md
index 849e33a65..d4bc0738c 100644
--- a/docs/getting-started/installing/index.en.md
+++ b/docs/getting-started/installing/index.en.md
@@ -1,6 +1,6 @@
You can install Krux in four different ways:
-- [:material-package-variant: From GUI application](../installing/from-gui.md)
+- [:material-package-variant: From GUI application](../installing/from-gui/index.en.md)
- [:material-console: From pre-built official release](../installing/from-pre-built-release.md)
- [:material-console: From pre-built test (beta) release](../installing/from-test-release.md)
- [:material-console: From source](../installing/from-source.md)
@@ -8,4 +8,4 @@ You can install Krux in four different ways:
### Requirements
Please, check the [parts list](../../parts.md) for the compatible devices and requirements.
-After the first firmware install, you can use a microSD card if you wish to perform further [airgapped updates](../features/sd-card-update.md).
\ No newline at end of file
+After the first firmware install, you can use a microSD card if you wish to perform further [airgapped updates](../features/sd-card-update.md).
diff --git a/docs/getting-started/usage/generating-a-mnemonic.en.md b/docs/getting-started/usage/generating-a-mnemonic.en.md
index ef7851d0e..8bacfb7d6 100644
--- a/docs/getting-started/usage/generating-a-mnemonic.en.md
+++ b/docs/getting-started/usage/generating-a-mnemonic.en.md
@@ -6,18 +6,14 @@ At the start screen, after selecting New Mnemonic, you will be taken to a second
## Camera
+(Experimental!) Choose between 12, 24 words or double mnemonic, then take a random picture and Krux will generate a mnemonic from the hash of the image bytes.
-(Experimental!) Choose between 12 or 24 words, then take a random picture and Krux will generate a mnemonic from the hash of the image bytes.
-
-
-
-
-
-
-
+
+
+
+
#### Image Entropy Quality Estimation
-
@@ -25,78 +21,75 @@ During image capture, entropy quality estimation is displayed to assist you in o
-## Words
+#### Double mnemonic
+It is the combination of two 12-word mnemonics that also forms a valid 24-word BIP-39 mnemonic. This is achieved by using the first 16 bytes (128 bits) of the image's entropy to generate the first 12-word, then using the next 16 bytes to generate the second 12-word and checking if these two 12-word together forms a valid 24-word, if not, we iterate over the second 12-word incrementing its entropy bytes until the two 12-word forms a valid 24-word.
+
+Some might say that the name double mnemonic is incorrect because we end up with two 12-word plus a 24-word mnemonic (12 + 12 + 24), so it's a triple mnemonic! But we only use entropy for the two 12-word ones, hence the name double mnemonic. Also, this name has already been used in this [double mnemonic generator](https://stepansnigirev.github.io/seed-tools/double_mnemonic.html) since July 2023.
+Some may wonder what is the use of this, it may be useful to some [plausible deniability](https://en.bitcoin.it/wiki/Privacy) or even a way to improve your [OPSEC](https://en.wikipedia.org/wiki/Operations_security).
+
+## Words
Print the BIP39 word list in 3D or on paper, then cut out the words and place them in a bucket. Manually draw 11 or 23 words from the bucket.
For the final word, Krux will assist you in picking a valid 12th or 24th word by adjusting its smart keypad to only allow typing words with a valid checksum. Alternatively, you can leave it empty, and Krux will select a final, valid checksum word for you.
## Dice Rolls
-
### Via D6
+Choose between 12 or 24 words. The entropy in a single roll of a D6 is 2.585 bits ( log2(6) ); therefore a minimum of a 50 rolls will be required for 128 bits of entropy, enough to generate a 12-word mnemonic. For 24-word, or an entropy of 256 bits, a minimum of 99 rolls will be required.
-Choose between 12 or 24 words.
-
-The entropy in a single roll of a D6 is 2.585 bits ( log2(6) ); therefore a minimum of a 50 rolls will be required for 128 bits of entropy, enough to generate a 12-word mnemonic. For 24 words, or an entropy of 256 bits, a minimum of 99 rolls will be required.
-
-
-
-
-
-
-
+
+
+
+
### Via D20
-
Since a D20 has more possible outcomes, the entropy is increased per roll to 4.322 bits ( log2(20) ). This means that only 30 rolls are necessary to create a 12-word mnemonic and 60 rolls for a 24-word mnemonic.
-
-
-
-
-
-
+
+
+
+
### Dice Rolls Entropy Quality Estimation
-
When you input your dice rolls, you'll see two progress bars filling up. The top progress bar shows how many rolls you've entered compared to the minimum number needed. The bottom progress bar shows the real-time calculated Shannon's entropy compared to the required minimum (128 bits for 12 words and 256 bits for 24 words). When the Shannon's entropy estimation reaches the recommended level, the progress bar will be full, and its frame will change color. If you've met the minimum number of rolls but the entropy estimation is still below the recommended level, a warning will appear, suggesting you add more rolls to increase entropy.
Note: Similar to image entropy quality estimation, dice rolls Shannon's entropy serves as an indicator and should not be considered an absolute measure of cryptographic entropy.
-Learn more about [Krux Entropy Quality Estimation](../features/entropy.md)
+Learn more about [Krux Entropy Quality Estimation](../features/entropy.md).
+
+
### Stats for Nerds
+A low Shannon's entropy value could suggest that your dice are biased or that there's a problem with how you're gathering entropy. To investigate further, examine the "Stats for Nerds" section to check the distribution of your rolls and look for any abnormalities.
-A low Shannon's entropy value might suggest that your dice are biased or that there's a problem with how you're gathering entropy. To investigate further, examine the "Stats for Nerds" section to check the distribution of your rolls and look for any abnormalities.
+
+
+
+
-
-
-
-
-
+## Editing a New Mnemonic - Optional
+After entering dice rolls, random words, or captured entropy through the camera, you can manually add custom entropy by editing some of the words. Edited words will be highlighted, and the final word will automatically update to ensure a valid checksum. However, proceed with caution, modifying words can negatively impact the natural entropy previously captured.
-## How it works
+
+
+## How Entropy Capture Works
For dice rolls, Krux keeps track of every roll you enter and displays the cumulative string of outcomes after each roll.
-When you have entered your final roll, Krux will hash this string using SHA256 and output the resulting hash to the screen so that you can verify it for yourself.
+When you have entered your final roll, Krux will hash this string using [SHA256](https://en.bitcoin.it/wiki/SHA-256) and output the resulting hash to the screen so that you can verify it for yourself.
-In the case a camera snapshot is used as source, image bytes, which contain pixels data in RGB565 format, will be hashed just like it is done with the dice rolls string.
+In case a camera snapshot is used as a source, the image bytes, which contain pixels data in RGB565 format, will be hashed in the same way as the dice rolls.
-
-
-
-
+
+
+
+
Krux then takes this hash, runs [`unhexlify`](https://docs.python.org/3/library/binascii.html#binascii.unhexlify) on it to encode it as bytes, and deterministically converts it into a mnemonic according to the [BIP-39 Reference Implementation](https://github.com/trezor/python-mnemonic/blob/6b7ebdb3624bbcae1a7b3c5485427a5587795120/src/mnemonic/mnemonic.py#L189-L207).
Note: For 12-word mnemonics, only the first half of the SHA256 hash is used (128 bits), while 24-word mnemonics use the full hash (256 bits).
-
-
-
-### How to verify
-
+### How to Verify
Don't trust, verify. We encourage you not to trust any claim you cannot verify yourself. Therefore, there are wallets that use compatible algorithms to calculate the entropy derived from dice rolls. You can use the [SeedSigner](https://seedsigner.com/) or [Coldcard](https://coldcard.com/) hardware wallets, or even the [Bitcoiner Guide website](https://bitcoiner.guide/seed/), they share the same logic that Krux uses and will give the same mnemonic for the dice roll method.
diff --git a/docs/getting-started/usage/loading-a-mnemonic.en.md b/docs/getting-started/usage/loading-a-mnemonic.en.md
index f147b5594..cb3c0f026 100644
--- a/docs/getting-started/usage/loading-a-mnemonic.en.md
+++ b/docs/getting-started/usage/loading-a-mnemonic.en.md
@@ -1,4 +1,4 @@
-Once you have either a 12- or 24-word BIP-39 mnemonic, choose `Load Mnemonic` on Krux's start menu, and you will be presented with several input methods:
+Once you have either a 12 or 24-word BIP-39 mnemonic, choose `Load Mnemonic` on Krux's start menu (aka login menu), and you will be presented with several input methods:
@@ -8,8 +8,7 @@ Once you have either a 12- or 24-word BIP-39 mnemonic, choose `Load Mnemonic` on
### Via Camera
-
-You can choose to use the camera to scan a `QR code` or `Tiny Seed` metal plate backup.
+You can choose to use the camera to scan a `QR code`, `Tiny Seed`, `OneKey KeyTag` or a `Binary Grid`.
----8<----
camera-scan-tips.en.txt
@@ -26,19 +25,19 @@ It's unpleasant having to manually enter 12 or 24 words every time you want to u
- [Compact SeedQR](https://github.com/SeedSigner/seedsigner/blob/dev/docs/seed_qr/README.md/#compactseedqr-specification): Basically, it is the mnemonic words bits concatenated as bytes.
- [Encrypted Mnemonic](../features/encrypted-mnemonics.md): A specification created by Krux that encrypts the mnemonic words bits and adds some information about the encryption used.
-After opening your wallet via one of the manual methods you can use Krux to create QR codes of all types above, transcript them to paper or metal using the transcription helpers or attach a thermal printer to your Krux and print out the mnemonic. Check out the [Printing section](../features/printing.md) for more information.
+After opening a wallet via one of the methods available you can use Krux to [backup the mnemonic](navigating-the-main-menu.md#backup-mnemonic) as QR code, transcribe them to paper or metal using the transcription helpers or attach a thermal printer to your Krux and print out the mnemonic as QR. Check out the [printing section](../features/printing.md) for more information.
You can also use [an offline QR code generator for this](https://iancoleman.io/bip39/) (ideally on an airgapped device).
-#### Tiny Seed
+#### Tiny Seed, OneKey KeyTag or Binary Grid
+[Tiny Seed](https://tinyseed.io/), [Onekey KeyTag](https://onekey.so/products/onekey-keytag/) and others directly encode a seed as binary, allowing for a very compact mnemonic storage. Krux devices have machine vision capabilities that allow users to scan these metal plates and instantly load mnemonics engraved on them (this feature is not available in Krux Android app).
-[Tiny Seed](https://tinyseed.io/) is a compact metal plate mnemonic backup method.
-Krux devices have machine vision capabilities that allow users to scan these metal plates and instantly load mnemonics engraved on them. To properly scan them place the Tiny Seed over a black background and paint the punched bits black to increase contrast. You can also scan the thermally printed version, or a filled template. Find templates to scan or print [here](https://github.com/odudex/krux_binaries/tree/main/templates).
+To properly scan, place the backup plate over a black background and paint the punched bits black to increase contrast. You can also scan the thermally printed version, or a filled template. You can find some [examples of mnemonics encoded here](../features/tinyseed.md). Alternatively, you can find [templates to scan or print here](https://github.com/odudex/krux_binaries/tree/main/templates).
### Via Manual Input
-Manually type `Words`, `Word Numbers`, `Tiny Seed` (toggle the bits or punches) or [`Stackbit`](https://stackbit.me) (model 1248 metal plate backup).
+Manually type `Words`, `Word Numbers`, `Tiny Seed` (toggle the bits or punches) or [`Stackbit 1248`](https://stackbit.me/produto/stackbit-1248/).
@@ -74,7 +73,7 @@ Enter the BIP-39 mnemonic word's numbers (1-2048) in binary format, toggling nec
-Enter the BIP-39 mnemonic word's numbers (1-2048) using the Stackbit 1248 metal plate backup method, where each of the four digits of the word's number is a sum of the numbers marked (punched) 1, 2, 4, or 8. For example, to enter the word "pear", number 1297, you must punch (1)(2)(1+8=9)(1+2+4=7).
+Enter the BIP-39 mnemonic word's numbers (1-2048) using the Stackbit 1248 metal plate backup method, where each of the four digits of the word's number is a sum of the numbers marked (punched) 1, 2, 4, or 8. For example, to enter the word "oyster", number 1268, you must punch (1)(2)(2,4)(8).
@@ -87,105 +86,86 @@ You can retrieve mnemonics previously stored on device's internal flash or exter
## Wallet Loading
-
### Confirm Mnemonic Words
-Once you have entered your mnemonic, you will be presented with the full list of words to confirm.
-
-
-
-### Confirm Wallet Attributes
-
-You will be presented with a screen containing wallet attributes, if they are as expected just press `Load Wallet` and you'll be ready to use your loaded key.
-
-
-
-
-#### Attributes
-
-**Fingerprint**
-
- 73c5da0a
-
- Mainnet
-
- Single-sig
-
- m/84'/0'/0'
-
+
+If you see an asterisk (`*`) in the header, it means this is a [double mnemonic](generating-a-mnemonic.md/#double-mnemonic).
- `44'` for Legacy
+
- `49'` for Nested Segwit
+### Edit Mnemonic - Optional
- `86'` for Taproot
+
+
- `48'` for Multisig
+If you make a mistake while loading a mnemonic, you can easily edit it. Simply touch or navigate to the word you want to change and replace it. Edited words will be highlighted in a different color. If the final word contains an invalid checksum, it will appear in red. If your checksum word is red, please review your mnemonic carefully, as there may be an error.
+
-2. Network: The second number defines the network:
+### Confirm Wallet Attributes
+
+
- `0'` for Mainnet
+You will be presented with a screen containing wallet attributes, if they are as expected just press `Load Wallet` and you'll be ready to use your loaded key.
- `1'` for Testnet
+
+#### Fingerprint
+* :material-fingerprint: ` 73c5da0a `:
+The BIP-32 master wallet's fingerprint, if you have it noted down, will help you make sure you entered the correct mnemonic and passphrase (optional) and will load the expected wallet.
-3. Account Index: The third number is the account index, with `0'` being the default.
+#### Network
+* ` Mainnet `:
+Check if you are loading a `Testnet` or `Mainnet` wallet.
-For multisig wallets, a fourth node with the value `2'` is added to the derivation path.
+#### Single / Multisig
+* ` Single-sig `:
+Check if you are loading a `Single-sig` or `Multisig` wallet.
-**Passphrase**
-
- No Passphrase
-
-You can type or scan a BIP-39 passphrase. When typing, swipe left :material-gesture-swipe-left: or right :material-gesture-swipe-right: to change keypads if your device has a touchscreen. For scanning, you can also create a QR code from your offline passphrase in [Tools](../features/tools.md/#create-qr-code).
+You can type or scan a BIP-39 passphrase. When typing, swipe left :material-gesture-swipe-left: or right :material-gesture-swipe-right: to change keypads if your device has a touchscreen. You can also hold the button `PAGE` or `PAGE_PREV` when navigating among letters while typing text to fast forward or backward. For scanning, you can also create a QR code from your offline passphrase using the [create QR code tool](../features/tools.md/#create-qr-code).
#### Customize
-
Press `Customize` to open a menu where you can change the `Network`, `Single/Multisig`, `Script Type` and `Account`.
-
Now, onto the main menu...
-
-
diff --git a/docs/getting-started/usage/navigating-the-main-menu.en.md b/docs/getting-started/usage/navigating-the-main-menu.en.md
index 23998c7d7..9e36a5721 100644
--- a/docs/getting-started/usage/navigating-the-main-menu.en.md
+++ b/docs/getting-started/usage/navigating-the-main-menu.en.md
@@ -3,8 +3,6 @@ After entering your mnemonic, and loading a wallet, you will find yourself on Kr
-
-
### Backup Mnemonic
@@ -16,7 +14,6 @@ If you set a [printer](../settings.md/#printer), it will also give the option to
#### QR Code
-
- **Plaintext QR**
@@ -48,8 +45,6 @@ Words are converted to their BIP-39 numeric indexes, those numbers are then conc
This option converts the encrypted mnemonic into a QR code. Enter an encryption key and, optionally, a custom ID. When you scan this QR code through "Load Mnemonic" -> "Via Camera" -> "QR Code," you will be prompted to enter the decryption key to load the mnemonic stored in it. Like any QR code, it can be printed if a thermal printer driver is set up.
-
-
#### Encrypted
@@ -62,7 +57,6 @@ When using any of the encryption methods, you will be prompted to enter an encry
See this page to find out more about: [Krux Mnemonics Encryption](../../getting-started/features/encrypted-mnemonics.md).
-
- **Store on Flash**
This option stores the encrypted mnemonic in the device's flash memory. You can decrypt and load it later through the "Load Mnemonic" -> "From Storage" option.
@@ -74,9 +68,12 @@ If an SD card is available, this option stores the encrypted mnemonic on it. You
- **Encrypted QR Code**
It's another path for the same functionality present on QR Code backups, described above.
+
+
#### Other Formats
- **Words**
+
@@ -85,18 +82,16 @@ Display the BIP-39 mnemonic words as text so you can write them down.
- **Numbers**
+
Display the BIP-39 mnemonic word numbers (1-2048) in decimal, hex, or octal format.
-
-
-
-
- **Stackbit 1248**
+
@@ -105,6 +100,7 @@ This metal backup format represents the BIP-39 mnemonic word's numbers (1-2048).
- **Tiny Seed**
+
@@ -116,30 +112,24 @@ This metal backup format represents the BIP-39 mnemonic word's numbers (1-2048)
A menu will be presented with options to display your master extended public key (xpub) as text and as a QR code. Depending on the script type or whether a single-sig or multisig wallet was loaded, the options shown will be xpub, ypub, zpub, or Zpub. When displayed as text, the extended public key can be stored on an SD card if available. If you choose to export a QR code, you can not only scan it but also save it as an image on an SD card or print it if a thermal printer is attached.
-
-
-
-
-
-
+
+
+
+
+
+
All QR codes will contain [key origin information in key expressions](https://github.com/bitcoin/bips/blob/master/bip-0380.mediawiki#Key_Expressions). If your coordinator cannot parse this information, it will not be capable of importing the wallet's fingerprint. As a result, Krux will not perform important verifications when signing transactions created by it unless you manually add the fingerprint so that it can be used to create Krux-compatible PSBTs.
Always prefer to import extended public keys directly from Krux when setting up a coordinator instead of copying it (or parts of it) from other sources.
-
-
### Wallet
Here you can load view and save wallet descriptors, add or change passphrases, customize wallet's attributes, generate and load a BIP85 child mnemonic.
#### Wallet Descriptor
-
A Bitcoin Wallet Output Script Descriptor defines a set of addresses in a wallet. It includes the following information:
-
- Script Type: Specifies the type of script (e.g., P2PKH, P2SH, P2WPKH).
-
- Origin Info: Defines the master fingerprint and derivation path used to derive keys.
-
- Extended Public Keys: usually represented as an xpub, but could be ypub, zpub, etc.
Output descriptors standardize how wallets generate addresses, ensuring compatibility and security. They help wallets and other software understand how to derive and verify the addresses used in transactions.
@@ -148,10 +138,10 @@ For multisig wallets, it is essential to load a descriptor to check addresses an
When you select the "Wallet Descriptor" option for the first time, you will be prompted to load a wallet descriptor via QR code or SD card. After loading, a preview of the wallet attributes will be displayed for confirmation.
-
-
-
-
+
+
+
+
If you access the "Wallet Descriptor" option again after loading your wallet, you will see the wallet's name, fingerprints, and the abbreviated XPUBs of all cosigners, along with a QR code containing the exact data that was initially loaded. If an SD card is inserted, you can save the descriptor to it for later use without the assistance of a coordinator. Additionally, if you have a thermal printer attached, you can print this QR code.
@@ -162,7 +152,6 @@ Please note that if you customize the wallet parameters or restart the device, t
#### Passphrase
-
@@ -178,25 +167,22 @@ Don't forget to verify the resulting fingerprint in the status bar to ensure you
-Here you are presented to the exact same customization options you have while loading a key and wallet. You can change the Network, Single/Multisig, Script Type and Account. [More about wallet attributes](./loading-a-mnemonic.md/#attributes)
+Here you are presented to the exact same customization options you have while loading a key and wallet. You can change the Network, Single/Multisig, Script Type and Account. [More about wallet attributes](./loading-a-mnemonic.md/#confirm-wallet-attributes)
#### BIP85
-
Bitcoin BIP85, also known as the Deterministic Entropy From BIP32 Keychains, allows for the generation of deterministic entropy using a BIP32 master key. This entropy can then be used to create various cryptographic keys and mnemonics (e.g., BIP39 seed phrases). BIP85 ensures that all derived keys and mnemonics are deterministic and reproducible, meaning they can be recreated from the same master key. This feature is useful for securely managing multiple child keys from a single master key without the need to store each one separately.
-
-
-
-
+
+
+
+
Choose between a 12 or 24 words child then type the desired index to export a child mnemonic. After being presented to the new mnemonic, you can choose to load and use it right away.
Please note passphrases will be removed when loading a BIP85 child.
-
-
### Address
@@ -262,11 +248,9 @@ If a thermal printer is attached to your device, you can also print the PSBT QR
#### Message
-
Similar to PSBTs, Krux can load, sign, and export signatures for messages. This feature allows you to attest not only to the ownership of the messages themselves but also to the ownership of Bitcoin addresses and the authorship of documents and files.
##### Standard Messages and Files
-
@@ -281,8 +265,9 @@ This feature is used to sign Krux releases, airgapped, using a Krux device.
##### Messages at Address
-
Coordinators like Sparrow and Specter offer the possibility to sign messages at a Bitcoin receive address, allowing you to attest ownership of that address. Krux will detect if the message is of this type and present a similar workflow for signing. The main difference is that the address will be displayed along with the raw message, and since the message is signed with a derived address instead of the master public key, Krux won't offer the option to export the raw public key after the signature.
+
+
diff --git a/docs/img/krux-installer/app_settings.png b/docs/img/krux-installer/app_settings.png
new file mode 100644
index 000000000..629c7c631
Binary files /dev/null and b/docs/img/krux-installer/app_settings.png differ
diff --git a/docs/img/krux-installer/baudrate.png b/docs/img/krux-installer/baudrate.png
new file mode 100644
index 000000000..6a98c4bcb
Binary files /dev/null and b/docs/img/krux-installer/baudrate.png differ
diff --git a/docs/img/krux-installer/dmg_volume.png b/docs/img/krux-installer/dmg_volume.png
new file mode 100644
index 000000000..c90fb66a4
Binary files /dev/null and b/docs/img/krux-installer/dmg_volume.png differ
diff --git a/docs/img/krux-installer/download_assets.png b/docs/img/krux-installer/download_assets.png
new file mode 100644
index 000000000..01049ba01
Binary files /dev/null and b/docs/img/krux-installer/download_assets.png differ
diff --git a/docs/img/krux-installer/flash.png b/docs/img/krux-installer/flash.png
new file mode 100644
index 000000000..9d58c68d0
Binary files /dev/null and b/docs/img/krux-installer/flash.png differ
diff --git a/docs/img/krux-installer/flash_done.png b/docs/img/krux-installer/flash_done.png
new file mode 100644
index 000000000..6e7c999f1
Binary files /dev/null and b/docs/img/krux-installer/flash_done.png differ
diff --git a/docs/img/krux-installer/locale_menu.png b/docs/img/krux-installer/locale_menu.png
new file mode 100644
index 000000000..2b5d16710
Binary files /dev/null and b/docs/img/krux-installer/locale_menu.png differ
diff --git a/docs/img/krux-installer/main.png b/docs/img/krux-installer/main.png
index cbadd5ef0..e22fba1f8 100644
Binary files a/docs/img/krux-installer/main.png and b/docs/img/krux-installer/main.png differ
diff --git a/docs/img/krux-installer/main2.png b/docs/img/krux-installer/main2.png
deleted file mode 100644
index 319dc008c..000000000
Binary files a/docs/img/krux-installer/main2.png and /dev/null differ
diff --git a/docs/img/krux-installer/select_device.png b/docs/img/krux-installer/select_device.png
index 3ee9527a4..e1bed277a 100644
Binary files a/docs/img/krux-installer/select_device.png and b/docs/img/krux-installer/select_device.png differ
diff --git a/docs/img/krux-installer/select_flash.png b/docs/img/krux-installer/select_flash.png
deleted file mode 100644
index 4bc6e457c..000000000
Binary files a/docs/img/krux-installer/select_flash.png and /dev/null differ
diff --git a/docs/img/krux-installer/select_old_version_menu.png b/docs/img/krux-installer/select_old_version_menu.png
new file mode 100644
index 000000000..2b388b91c
Binary files /dev/null and b/docs/img/krux-installer/select_old_version_menu.png differ
diff --git a/docs/img/krux-installer/select_version_menu.png b/docs/img/krux-installer/select_version_menu.png
index 0e9a8acff..a61fd8e31 100644
Binary files a/docs/img/krux-installer/select_version_menu.png and b/docs/img/krux-installer/select_version_menu.png differ
diff --git a/docs/img/krux-installer/unzip.png b/docs/img/krux-installer/unzip.png
new file mode 100644
index 000000000..7f2195a6d
Binary files /dev/null and b/docs/img/krux-installer/unzip.png differ
diff --git a/docs/img/krux-installer/verification.png b/docs/img/krux-installer/verification.png
new file mode 100644
index 000000000..08e95ed54
Binary files /dev/null and b/docs/img/krux-installer/verification.png differ
diff --git a/docs/img/krux-installer/warn_already_downloaded.png b/docs/img/krux-installer/warn_already_downloaded.png
new file mode 100644
index 000000000..25ed9701f
Binary files /dev/null and b/docs/img/krux-installer/warn_already_downloaded.png differ
diff --git a/docs/img/krux-installer/warn_beta.png b/docs/img/krux-installer/warn_beta.png
new file mode 100644
index 000000000..d12f3aabc
Binary files /dev/null and b/docs/img/krux-installer/warn_beta.png differ
diff --git a/docs/img/krux-installer/wipe.png b/docs/img/krux-installer/wipe.png
new file mode 100644
index 000000000..737231386
Binary files /dev/null and b/docs/img/krux-installer/wipe.png differ
diff --git a/docs/img/krux-installer/wipe_warn.png b/docs/img/krux-installer/wipe_warn.png
index 83bf0ca41..62f1e5076 100644
Binary files a/docs/img/krux-installer/wipe_warn.png and b/docs/img/krux-installer/wipe_warn.png differ
diff --git a/docs/img/maixpy_amigo/load-mnemonic-camera-options-150.en.png b/docs/img/maixpy_amigo/load-mnemonic-camera-options-150.en.png
index dcd7fc95a..4aef1a273 100644
Binary files a/docs/img/maixpy_amigo/load-mnemonic-camera-options-150.en.png and b/docs/img/maixpy_amigo/load-mnemonic-camera-options-150.en.png differ
diff --git a/docs/img/maixpy_amigo/load-mnemonic-seq-double-mnemonic-150.en.png b/docs/img/maixpy_amigo/load-mnemonic-seq-double-mnemonic-150.en.png
new file mode 100644
index 000000000..7bfe52224
Binary files /dev/null and b/docs/img/maixpy_amigo/load-mnemonic-seq-double-mnemonic-150.en.png differ
diff --git a/docs/img/maixpy_amigo/load-mnemonic-seq-mnemonic-150.en.png b/docs/img/maixpy_amigo/load-mnemonic-seq-mnemonic-150.en.png
index 9da9fe950..98ca3641a 100644
Binary files a/docs/img/maixpy_amigo/load-mnemonic-seq-mnemonic-150.en.png and b/docs/img/maixpy_amigo/load-mnemonic-seq-mnemonic-150.en.png differ
diff --git a/docs/img/maixpy_amigo/load-mnemonic-seq-mnemonic-edited-wrong-150.en.png b/docs/img/maixpy_amigo/load-mnemonic-seq-mnemonic-edited-wrong-150.en.png
new file mode 100644
index 000000000..1da8fc837
Binary files /dev/null and b/docs/img/maixpy_amigo/load-mnemonic-seq-mnemonic-edited-wrong-150.en.png differ
diff --git a/docs/img/maixpy_amigo/new-mnemonic-edited-150.en.png b/docs/img/maixpy_amigo/new-mnemonic-edited-150.en.png
new file mode 100644
index 000000000..296877776
Binary files /dev/null and b/docs/img/maixpy_amigo/new-mnemonic-edited-150.en.png differ
diff --git a/docs/img/maixpy_amigo/new-mnemonic-options-150.en.png b/docs/img/maixpy_amigo/new-mnemonic-options-150.en.png
index 1a3bfc1a2..f65388a15 100644
Binary files a/docs/img/maixpy_amigo/new-mnemonic-options-150.en.png and b/docs/img/maixpy_amigo/new-mnemonic-options-150.en.png differ
diff --git a/docs/img/maixpy_amigo/new-mnemonic-via-snapshot-prompt-150.en.png b/docs/img/maixpy_amigo/new-mnemonic-via-snapshot-prompt-150.en.png
index 1dbd64c56..85ecc6226 100644
Binary files a/docs/img/maixpy_amigo/new-mnemonic-via-snapshot-prompt-150.en.png and b/docs/img/maixpy_amigo/new-mnemonic-via-snapshot-prompt-150.en.png differ
diff --git a/docs/img/maixpy_m5stickv/load-mnemonic-camera-options-125.en.png b/docs/img/maixpy_m5stickv/load-mnemonic-camera-options-125.en.png
index 6a4c81853..fd47cf038 100644
Binary files a/docs/img/maixpy_m5stickv/load-mnemonic-camera-options-125.en.png and b/docs/img/maixpy_m5stickv/load-mnemonic-camera-options-125.en.png differ
diff --git a/docs/img/maixpy_m5stickv/load-mnemonic-seq-double-mnemonic-125.en.png b/docs/img/maixpy_m5stickv/load-mnemonic-seq-double-mnemonic-125.en.png
new file mode 100644
index 000000000..acbd53f1b
Binary files /dev/null and b/docs/img/maixpy_m5stickv/load-mnemonic-seq-double-mnemonic-125.en.png differ
diff --git a/docs/img/maixpy_m5stickv/load-mnemonic-seq-mnemonic-125.en.png b/docs/img/maixpy_m5stickv/load-mnemonic-seq-mnemonic-125.en.png
index eaed3952e..6c09de296 100644
Binary files a/docs/img/maixpy_m5stickv/load-mnemonic-seq-mnemonic-125.en.png and b/docs/img/maixpy_m5stickv/load-mnemonic-seq-mnemonic-125.en.png differ
diff --git a/docs/img/maixpy_m5stickv/load-mnemonic-seq-mnemonic-edited-wrong-125.en.png b/docs/img/maixpy_m5stickv/load-mnemonic-seq-mnemonic-edited-wrong-125.en.png
new file mode 100644
index 000000000..8c808d5a0
Binary files /dev/null and b/docs/img/maixpy_m5stickv/load-mnemonic-seq-mnemonic-edited-wrong-125.en.png differ
diff --git a/docs/img/maixpy_m5stickv/new-mnemonic-edited-125.en.png b/docs/img/maixpy_m5stickv/new-mnemonic-edited-125.en.png
new file mode 100644
index 000000000..2c83d95d8
Binary files /dev/null and b/docs/img/maixpy_m5stickv/new-mnemonic-edited-125.en.png differ
diff --git a/docs/img/maixpy_m5stickv/new-mnemonic-options-125.en.png b/docs/img/maixpy_m5stickv/new-mnemonic-options-125.en.png
index 235c3b334..dcfb8773d 100644
Binary files a/docs/img/maixpy_m5stickv/new-mnemonic-options-125.en.png and b/docs/img/maixpy_m5stickv/new-mnemonic-options-125.en.png differ
diff --git a/docs/img/tinyseed_binarygrid/binarygrid.jpg b/docs/img/tinyseed_binarygrid/binarygrid.jpg
new file mode 100644
index 000000000..4b19884c4
Binary files /dev/null and b/docs/img/tinyseed_binarygrid/binarygrid.jpg differ
diff --git a/docs/img/tinyseed_binarygrid/onekey_keytag.jpg b/docs/img/tinyseed_binarygrid/onekey_keytag.jpg
new file mode 100644
index 000000000..d1405ee5e
Binary files /dev/null and b/docs/img/tinyseed_binarygrid/onekey_keytag.jpg differ
diff --git a/docs/img/tinyseed_binarygrid/size_reference.jpg b/docs/img/tinyseed_binarygrid/size_reference.jpg
new file mode 100644
index 000000000..60d520f13
Binary files /dev/null and b/docs/img/tinyseed_binarygrid/size_reference.jpg differ
diff --git a/docs/img/tinyseed_binarygrid/tinyseed.jpg b/docs/img/tinyseed_binarygrid/tinyseed.jpg
new file mode 100644
index 000000000..b1d297412
Binary files /dev/null and b/docs/img/tinyseed_binarygrid/tinyseed.jpg differ
diff --git a/docs/parts.en.md b/docs/parts.en.md
index 1890a5298..57717e384 100644
--- a/docs/parts.en.md
+++ b/docs/parts.en.md
@@ -17,7 +17,7 @@
:material-information:{id="camera-info"}:
-Only `OV7740` and `OV2640` have an anti-glare mode to better capture images from high brightness screens or with incident light.
+Only `OV7740`, `OV2640` and `GC2145` have an anti-glare mode to better capture images from high brightness screens or with incident light.
:material-numeric-1-circle:{id="m5stickv-info"}:
@@ -133,7 +133,7 @@ warning-printer.en.txt
Krux has the capability to print all QR codes it generates, including those for mnemonics, xpubs, wallet backups, and signed PSBTs, using a locally-connected thermal printer via its serial port.
-Many TTL serial thermal printers may be compatible, but currently, the [Goojprt QR203](https://www.aliexpress.com/w/wholesale-Goojprt-QR203.html) has the best support. The [Adafruit printer starter pack](https://www.adafruit.com/product/600) can also be a convenient option to get started, as it includes all the necessary components for printing (except the conversion cable). To ensure proper functionality, enable the printer driver in the [Krux settings](./getting-started/settings.md/#thermal), set the Tx pin and baud rate value to either 19200 or 9600 (depends on the printer), as explained in this [Adafruit printer tutorial](https://learn.adafruit.com/mini-thermal-receipt-printer/first-test). You will need to connect the device's Tx to the printer's Rx and device's ground to the printer's ground, do not connect any other pins because a wrong connection may damage your device. The printer requires a dedicated power supply, typically with an output of 5 to 9V and capable of supplying at least 2A. For more information, [see this discussion](https://github.com/selfcustody/krux/discussions/312).
+Many TTL serial thermal printers may be compatible, but currently, the [Goojprt QR203](https://www.aliexpress.com/w/wholesale-Goojprt-QR203.html) has the best support (except this printer only supports ASCII or Chinese characters, non-ASCII characters will be printed as Chinese). The [Adafruit printer starter pack](https://www.adafruit.com/product/600) can also be a convenient option to get started, as it includes all the necessary components for printing (except the conversion cable). To ensure proper functionality, enable the printer driver in the [Krux settings](./getting-started/settings.md/#thermal), set the Tx pin and baud rate value to either 19200 or 9600 (depends on the printer), as explained in this [Adafruit printer tutorial](https://learn.adafruit.com/mini-thermal-receipt-printer/first-test). You will need to connect the device's Tx to the printer's Rx and device's ground to the printer's ground, do not connect any other pins because a wrong connection may damage your device. The printer requires a dedicated power supply, typically with an output of 5 to 9V (or 12V) and capable of supplying at least 2A. For more information, [see this discussion](https://github.com/selfcustody/krux/discussions/312).
#### (Optional) Conversion Cable for Thermal Printer
To connect the printer to M5StickV, Amigo or Cube, you will need a [grove conversion cable](https://store-usa.arduino.cc/products/grove-4-pin-male-to-grove-4-pin-cable-5-pcs) with a 4-pin male Grove connector on one end (to connect to the device) and 4-pin male jumpers on the other end (to connect to the printer). Check your device and printer model connection first, Yahboom comes with PH2.0 4Pin female connector; Dock and Bit doesn't have a connector. For a more reliable connection, it is recommended to cut and solder the wires of your custom cables instead of using jumpers.
\ No newline at end of file
diff --git a/docs/snippets/after-install-installer.en.md b/docs/snippets/after-install-installer.en.md
new file mode 100644
index 000000000..fc81b67d7
--- /dev/null
+++ b/docs/snippets/after-install-installer.en.md
@@ -0,0 +1 @@
+Once installed, you can proceed to [firmware installation](/krux/getting-started/installing/from-gui/usage).
diff --git a/docs/snippets/camera-scan-tips.en.txt b/docs/snippets/camera-scan-tips.en.txt
index 0fa7b4ee3..bfbd8720c 100644
--- a/docs/snippets/camera-scan-tips.en.txt
+++ b/docs/snippets/camera-scan-tips.en.txt
@@ -1 +1 @@
-If you are in a dark environment, you can hold down the `ENTER` button of the M5StickV or Maix Amigo to turn on their LED light to potentially increase visibility. Some cameras (`OV7740` and `OV2640`) have an anti-glare mode to better capture images from high brightness screens or with incident light, they are present on M5StickV, Amigo, Cube and some Yahboom. To enable/disable the anti-glare mode on a supported device just press the `PAGE` button while scanning.
\ No newline at end of file
+If you are in a dark environment, you can hold down the `ENTER` button of the M5StickV or Maix Amigo to turn on their LED light to potentially increase visibility. Some cameras (`OV7740`, `OV2640` and `GC2145`) have an anti-glare mode to better capture images from high brightness screens or with incident light, they are present on M5StickV, Amigo, Cube and Yahboom. To enable/disable the anti-glare mode on a supported device just press the `PAGE` button while scanning.
\ No newline at end of file
diff --git a/docs/snippets/flash-krux-logo.en.txt b/docs/snippets/flash-krux-logo.en.txt
index bfeca470f..8d3056ccf 100644
--- a/docs/snippets/flash-krux-logo.en.txt
+++ b/docs/snippets/flash-krux-logo.en.txt
@@ -1,8 +1,8 @@
When the flashing process completes, you should see the Krux logo:
-
-
+
+
If it doesn't, try turning your device off and on by holding down the power button for six seconds.
-Congrats, you're now running Krux!
\ No newline at end of file
+Congrats, you're now running Krux!
diff --git a/docs/snippets/install-installer-macos.en.txt b/docs/snippets/install-installer-macos.en.txt
new file mode 100644
index 000000000..2e1d8c0ae
--- /dev/null
+++ b/docs/snippets/install-installer-macos.en.txt
@@ -0,0 +1,17 @@
+Open the `dmg` file and a new volume will be presented;
+drag'n'drop the **krux-installer** to the **Applications** folder:
+
+
+
+Before run, you'll need to remove the quarantine flag from application.
+This occurs because we don't added the [Apple's code signing and notarization](https://support.apple.com/guide/security/app-code-signing-process-sec3ad8e6e53/web).
+
+To fix this, open your terminal and execute the following command:
+
+```bash
+xattr -d com.apple.quarantine -r /Applications/krux-installer.app
+```
+
+----8<----
+verify-the-signature-trust-tip.en.txt
+----8<----
diff --git a/docs/snippets/tips-after-install.en.txt b/docs/snippets/tips-after-install.en.txt
index 8518deee0..5a2652c67 100644
--- a/docs/snippets/tips-after-install.en.txt
+++ b/docs/snippets/tips-after-install.en.txt
@@ -2,4 +2,4 @@
Prefer a different language? Krux has support for multiple languages. Once at the start screen, go to `Settings`, followed by `Locale`, and select the locale you wish to use.
### Upgrade via microSD card
-Once you've installed the initial firmware on your device via USB, you can either continue updating the device by flashing or you can perform upgrades [via microSD](../features/sd-card-update.md) card to keep the device airgapped.
\ No newline at end of file
+Once you've installed the initial firmware on your device via USB, you can either continue updating the device by flashing or you can perform upgrades [via microSD](/krux/getting-started/features/sd-card-update/) card to keep the device airgapped.
diff --git a/docs/snippets/verify-the-integrity-explain.en.txt b/docs/snippets/verify-the-integrity-explain.en.txt
new file mode 100644
index 000000000..a283a75d4
--- /dev/null
+++ b/docs/snippets/verify-the-integrity-explain.en.txt
@@ -0,0 +1 @@
+Open your terminal and type the command below:
diff --git a/docs/snippets/verify-the-signature-explain.en.txt b/docs/snippets/verify-the-signature-explain.en.txt
new file mode 100644
index 000000000..de4cebf3a
--- /dev/null
+++ b/docs/snippets/verify-the-signature-explain.en.txt
@@ -0,0 +1,7 @@
+The first step is import the developer's key:
+
+```bash
+gpg --keyserver hkps://keys.openpgp.org --recv-keys B4281DDDFBBD207BFA4113138974C90299326322
+```
+
+Then, to verify yourself, run this command on your terminal:
diff --git a/docs/snippets/verify-the-signature-tip.en.txt b/docs/snippets/verify-the-signature-tip.en.txt
new file mode 100644
index 000000000..6e1f4fbff
--- /dev/null
+++ b/docs/snippets/verify-the-signature-tip.en.txt
@@ -0,0 +1,2 @@
+> ⚠️ TIP: If the verification was successful,
+> you may get a message similar to: `Good signature from "qlrddev