Release notes

• Remove legacy "export to SD" 5b8ca01
• Show warning that tx is fully signed if we find final witness or scriptsig 9deaebb
• Add fingerprint to processed files so the same SD card can be used with multiple devices at the same time 2e197b0
• Support scanning or loading from SD files seeds in binary, digital and text form using standard "Scan QR code" and "Open SD file" buttons d838664
• Switch QR scanner to command mode, so we don't overwrite the buffer when QR code rate is too high (hello Sparrow) d838664
• Fix a bug in embit that caused invalid psbt serialization in rare cases fbe4f57
• Fix a bug when wallets are not reloaded if another seed is loaded e5bc8b7
• Fix a bug when selecting Liquid Tested was throwing errors 4f6ed13

Upgrade process

Copy specter_upgrade_v1.8.3.bin to the SD card and insert it into the device. The bootloader will check the signatures of the upgrade file and update the firmware.

Flashing on empty board

If your discovery board is empty or you have a very old firmware (below 1.4.0) - connect your board over miniUSB with power jumper set to STLK and copy-paste initial_firmware_v1.8.3.bin file to the mounted drive.

If you have problems flashing initial firmware consider using stlink-tools. A command to flash firmware:

st-flash write path/to/initial_firmware.bin 0x8000000

If you want to use self-signed bootloader and firmware check out the instructions in the bootloader repo

sha256.signed.txt file contains sha256 hashes of the firmware binary files and signed with @stepansnigirev's GPG key.
You can get the public key here: https://stepansnigirev.com/ss-specter-release.asc.
It is also available on keys.openpgp.org.
Fingerprint of the key is 6F16 E354 F833 93D6 E52E C25F 36ED 357A B24B 915F, short id: 36ed357ab24b915f

Tags and commits are signed using another key: stepan-github.asc

Reproducible build

You can build binaries identical to the ones in this release yourself. Follow this instruction, when the build is almost complete the script will output a message for signing and ask you for the signatures.

Verify that upgrade message is:

1.8.3-1kejkzr43ufvje3eku3ztx9jmgm6m59xn42yx2zepzplgwu3jy05spj8cax

Add first signature:

IOjijYdeUr+GkXwa0c/lOAmoqBrk0rktoZTF1yF70rI0EfqkJG75qA1miaekw1fvfHpk6nc22qqSrGUoOmfSA48=

Add second signature:

H0Sr+fjLl6UG3wWc5/mYRKg79TJdnKOKVlOWpcXYGeCLFD+L2Uo5c8xWY76plTr+Wg/waXcgIPvLErsmSlt9SQk=

Then hit enter and check that sha256.txt has the same hashes as in sha256.signed.txt file.