Package: lumensigner
Build an offline, airgapped Stellar signing device for less than $50!The project is currently in development and is not yet ready for use with real funds.The first developer preview has been released.Project SummaryShopping ListSoftware InstallationVerifying the SoftwareEnclosure DesignsSeedQR Printable TemplatesManual Installation InstructionsProject SummaryThe goal of LumenSigner is to enhance the security of users' Stellar accounts. To accomplish this goal, LumenSigner offers anyone the opportunity to build a verifiable air-gapped, stateless Stellar signing device using inexpensive, publicly available hardware components (usually < $50).LumenSigner is built on top of SeedSigner, and we are grateful for the contributions made by SeedSigner contributors.If you have specific questions about the project, ourDiscord serveris a great place to ask them.Feature Highlights:Calculate word 12/24 of a BIP-39 seed phraseCreate a 24-word BIP-39 seed phrase with 99 dice rollsCreate a 24-word BIP-39 seed phrase by taking a digital photoTemporarily store up to 3 seed phrases while device is poweredGuided interface to manually create a SeedQR for instant input(demo video here)BIP-39 passphrase / word 25 supportScan and parse transaction data from animated QR codesReview transaction information and sign it.Live preview during photo-to-seed and QR scanning UXOptimized seed word entry interfaceResponsive, event-driven user interfaceShopping ListTo build a LumenSigner, you will need:Raspberry Pi Zero (preferably version 1.3 with no WiFi/Bluetooth capability, but any Raspberry Pi 2/3/4 or Zero model will work, Raspberry Pi 1 devices will require a hardware modification to the Waveshare LCD Hat, as per theinstructions here)Waveshare 1.3" 240x240 pxl LCD (correct pixel count is important, more info athttps://www.waveshare.com/wiki/1.3inch_LCD_HAT)Pi Zero-compatible camera (tested to work with the Aokin / AuviPal 5MP 1080p with OV5647 Sensor)Notes:You will need to solder the 40 GPIO pins (20 pins per row) to the Raspberry Pi Zero board. If you don't want to solder, purchase "GPIO Hammer Headers" for a solderless experience.Other cameras with the above sensor module should work, but may not fit in the Orange Pill enclosureChoose the Waveshare screen carefully; make sure to purchase the model that has a resolution of 240x240 pixelsLumenSigner owes its existence to the hard work of SeedSigner contributors, you can support them by purchasing hardwarehere.Software InstallationA Special Note On Minimizing TrustAs is the nature of pre-packaged software downloads, downloading and using the prepared LumenSigner release images means implicitly placing trust in the individual preparing those images; in our project the release images are prepared and signed by the eponymous creator of the project,@overcat"the person". That individual is additionally the only person in possession of the PGP keys that are used to sign the release images.However, one of the many advantages of the open source software model is that the need for this kind of trust can be negated by our users' ability to (1) review the project's source code and (2) assemble the operating image necessary to use the software themselves. From our project's inception, instructions to build a LumenSigner operating image (using precisely the same process that is used to create the prepared release images) have been made availabile. We have put a lot of thought and work into making these instructions easy to understand and follow, even for less technical users. These instructions can be foundhere.Downloading the SoftwareDownload the current Version (0.1.0.dev0) software image that is compatible with your  Raspberry Pi Hardware. The Pi Zero 1.3 is the most common and recommended board.BoardDownload Image Link/NameRaspberry Pi Zero 1.3lumensigner_os.0.1.0.dev0.pi0.imgRaspberry Pi Zero Wlumensigner_os.0.1.0.dev0.pi0.imgRaspberry Pi Zero 2 Wlumensigner_os.0.1.0.dev0.pi02w.imgRaspberry Pi 2 Model Blumensigner_os.0.1.0.dev0.pi2.imgRaspberry Pi 3 Model Blumensigner_os.0.1.0.dev0.pi02w.imgRaspberry Pi 4 Model Blumensigner_os.0.1.0.dev0.pi4.imgRaspberry Pi 400lumensigner_os.0.1.0.dev0.pi4.imgNote: If you have physically removed the WiFi component from your board, you will still use the image file of the original(un-modified) hardware. (Our files are compiled/based on theprocessorarchitecture). Although it is better to spend a few minutes upfront to determine which specific Pi hardware/model you have, if you are still unsure which hardware you have, you can try using the pi0.img file. Making an incorrect choice here will not ruin your board, because this is software, not firmware.also downloadthese 2 signature verification files to the same folderThe Plaintext manifest fileThe Signature of the manifest fileOnce the files have all finished downloading, follow the steps below to verify the download before continuing on to write the software onto a MicroSD card. Next, insert the MicroSD into your assembled hardware and connect the USB power. Allow about 45 seconds for our logo to appear, and then you can begin using your LumenSigner!Our previous software versions are available here. Choose a specific version and then expand theAssetssub-heading to display the .img file binary and also the 2 associated signature files.Note:The prior version files will have lower numbers than the scripts and examples provided in this document, but the naming format will be the same, so you can edit them as required for signature verification etc.Verifying that the downloaded files are authentic (optional but highly recommended!)You can quickly verify that the software you just downloaded is both authentic and unaltered, by following these instructions.
We assume you are running the commands from a computer where bothGPGandshasumare already installed, and that you also knowhow to navigate on a terminal.Step 1. Verify that the signature (.sig) file is genuine:Run GPG'sfetch-keyscommand to import the LumenSigner projects public key from the popular online keyserver calledKeybase.io, into your computer'skeychain.gpg --fetch-keys https://keybase.io/overcat/pgp_keys.asc?fingerprint=a78bca78b9c468db2b6f8a1493323c9ec6769086The result should confirm that 1 key waseitherimported or updated.Ignoreany key ID's or email addresses shown.Next, you will run theverifycommand on the signature (.sig) file. (Verifymust be run from inside the same folder that you downloaded the files into earlier. The*'s in this command will auto-fill the version from your current folder, so it should be copied and pasted as-is.)gpg --verify lumensigner_os.0.1.0.dev0.sha256.sigWhen the verify command completes successfully, it should display output like this:The result must display "Good signature".  Ignore any email addresses -onlymatching Key fingerprints count here. Stop immediately if it displays "Bad signature"!On thelastoutput line, look at yourrightmost16 characters (the 4 blocks of 4).Crucially, we must now check WHO that Primary key fingerprint /ID belongs to.We will start by looking at Keybase.io to see if it is theLumenSigner project's public key or not.About the warning message:Since you are about to match the outputted fingerprint/ID against the proofs at keybase.io/overcat, and thereby confirm who the pubkey really belongs to-, you can safely ignore this warning message:> WARNING: This key is not certified with a trusted signature!  
> There is no indication that the signature belongs to the owner.More about how the verify command works:The verify command will attempt to decrypt the signature file (sha256.sig) by trying each public key already imported into your computer. If the public key we just imported (via fetch-keys), manages to: (a) successfully decrypt the .sig file , and (b), that result matches exactly to the clear-text equivalent (.sha256) of the .sig file, then its "a good signature"!Crucially, we must still manually check whoexactlyowns the Key ID which gave us that "Good signature". Thats what the warning message means- Who does the matching key really belong to? We will start by looking at keybase.io to see if it is "The LumenSigner project"'s public Key or not.
Note that it is the file hashes of .sig and .sha256 thatverifycompares, not their raw contents.Now to determinewhothe Public key ID belongs to: Gotokeybase.io/overcatYou must nowmanuallycompare: The 16 character fingerprint ID (as circled in red above) to, thoserightmost16 characters from yourverifycommand.If they match exactly, then you have successfully confirmed that your .sig file is authentically from the LumenSigner Project!Learn more about how keybase.io helps you check that someone (online) is who they say they are:Keybase.io allows you to independently verify that the public key saved on Keybase.io, is both authentic and that it belongs to the organization it claims to represent.  
 Keybase has already checked the three pubkey file locations  cryptographically when they were saved there. You can further verify the key publications if you would like:via Keybase: By clicking on any of the three blue badges to see that the "proof" was published at that location. (The blue badge marked as tweet, is in the most human-readable form and it is also a bi-directional link on Twitter)Once you have used the above method, you will know if the Public Key stored on Keybase, is genuinely from the LumenSinger Project or not.If the two ID's donotmatch, then you must stop here immediately. Do not continue. Contact us for assistance in the Discord server above.Step 2. Verifying that thesoftware images/binariesare genuineNow that you have confirmed that you do have the real LumenSigner Project's Public Key (ie the 16 characters match) - you can return to your terminal window. Running  theshasumcommand, is the final verification step and will confirm (via file hashing) that the software code/image files, were also not altered since publication, or even during your download process.On Linux or OSX:Run this commandshasum -a 256 --ignore-missing --check lumensigner.0.1.*.sha256On Windows (inside Powershell):Run this commandCertUtil -hashfile gpg --verify lumensigner_os.0.1.0.dev0.Insert_Your_Pi_Models_binary_here_For_Example_pi02w.img SHA256On Windows, you must then manually compare the resulting file hash value to the corresponding hash value shown inside the .SHA256 cleartext file.Wait up to 30 seconds for the command to complete, and it should display:lumensigner_os.0.1.0.dev0.[Your_Pi_Model_For_Example:pi02w].img: OKIf you receive the "OK" messagefor yourlumensigner.0.1.x.[Your_Pi_Model_For_Example:pi02w].img file, as shown above, then your verification is fully complete!All of your downloaded files have now been confirmed as both authentic and unaltered!You can proceed to create/write your MicroSD card😄😄 !!If your file result shows "FAILED", then you must stop here immediately. Do not continue. Contact us for assistance at  the Discord server above.Please recognize that this process can only validate the software to the extent that the entity that first published the key is an honest actor, and their private key is not compromised or somehow being used by a malicious actor.Writing the software onto your MicroSD cardTo write the LumenSigner software onto your MicroSD card, there are a few options available:ApplicationDescriptionPlatform and official SourceBalena EtcherThe application is called Etcher, and the company that wrote it is called Balena.  HenceEtcher by BalenaorBalena EtcherAvailable for Windows, Mac and LinuxRaspberry Pi ImagerProduced by the Raspberry Pi organization.Available for Windows, Mac and LinuxDD Command Line UtilityBuilt-in to Linux and MacOS, the DD (Data Duplicator) is a tool for advanced users.  If not used carefully it can accidentally format the incorrect disk!Built-in to Linux and MacOSBe sure to download the software from the genuine publisher.Either of the Etcher or Pi Imager software is recommended.  Some users have reported a better experience with one or the other. So, if the one application doesn't work well for your particular machine, then please try the other one.General Considerations:The writing and verify steps are very quick from version 0.1.0 upwards, so please pay close attention to your screen.
Make sure to set any write-protection physical slider on the MicroSD Card Adapter to UN-locked.You also don't need to pre-format the MicroSD beforehand.  Youdontneed to unzip any .zip file beforehand.
Current Etcher and Pi Imager software will perform a verify action (by default) to make sure the card was written successfully! Watching for that verify step to complete successfully, can save you a lot of headaches if you later need to troubleshoot issues where your LumenSigner device doesn't boot up at power on.Writing the MicroSd card is also known as flashing.It will overwrite everything on the MicroSD card.If the one application fails for you, then please try again using our other recommended application.Advanced users may want to try the Linux/MacOSDDcommand instead of using Etcher or Pi Imager, however, a reminder is given that DD can overwrite the wrong disk if you are not careful !Specific considerations for Windows users:Use the Pi imager software as your first choice on Windows. Windows can sometimes flag the writing of a MicroSD as risky behaviour and hence it may prevent this activity. If this happens, your writing/flashing will fail, hang or won't even begin, in which case you should to try to run the Etcher/Pi-Imager app "As administrator", (right-click and choose that option). It can also be blocked by windows security in some cases, so If you have the (non-default)Controlled Folder Accessoption set to active, try turning thatofftemporarily.Enclosure DesignsOpen PillThe Open Pill enclosure design is all about quick, simple and inexpensive deployment of a LumenSigner device. The design does not require any additional hardware and can be printed using a standard FDM 3D printer in about 2 hours, no supports necessary. A video demonstrating the assembly process can be foundhere. To access the design file and printable model, clickhere.Orange PillThe Orange Pill enclosure design offers a more finished look that includes button covers and a joystick topper. You'll also need the following additional hardware to assemble it:4 x F-F M2.5 spacers, 10mm length4 x M2.5 pan head screws, 6mm length4 x M2.5 pan head screws, 12mm lengthThe upper and lower portions of the enclosure can be printed using a standard FDM 3D printer, no supports necessary. The buttons and joystick nub should ideally be produced with a SLA/resin printer. An overview of the entire assembly process can be foundhere. To access the design files and printable models, clickhere.Community DesignsLil Pillby @_CyberNomadOrangeSurf Caseby @OrangeSurfBTCPS4 SeedSignerby @SilexperienceOpenPill Faceplateby @RevetuzoWaveshare CoverPlateby @Adathome1SeedQR Printable TemplatesYou can use LumenSigner to export your seed to a hand-transcribed SeedQR format that enables you to instantly load your seed back into LumenSigner.More information about SeedQRsStandard SeedQR templates:12-word SeedQR template dots (25x25)24-word SeedQR template dots (29x29)12-word SeedQR template grid (25x25)24-word SeedQR template grid (29x29)Baseball card template: 24-word SeedQR (29x29)CompactSeedQR templates:12-word CompactSeedQR template dots (21x21)24-word CompactSeedQR template dots (25x25)12-word CompactSeedQR template grid (21x21)24-word CompactSeedQR template grid (25x25)Baseball card template: 12-word Compact SeedQR (21x21)Baseball card template: 24-word Compact SeedQR (25x25)2-sided SeedQR templates - 8 per sheet
Printing settings - (2-sided)("flip on long edge")("Actual Size")
If printing on cardstock, adjust your printer settings via its control panelA4 templates(210mm * 297mm):21x21 - stores 12-word seeds ONLY in CompactSeedQR format ONLY25x25 - stores 12-word or 24 word seeds depending on SeedQR format29x29 - stores 24-word seeds ONLY as plaintext SeedQR format ONLYLetter templates(8.5in * 11in):21x21 - stores 12-word seeds ONLY in CompactSeedQR format ONLY25x25 - stores 12-word or 24 word seeds depending on format29x29 - stores 24-word seeds ONLY as plaintext SeedQR format ONLYManual Installation Instructionssee the docs:Manual Installation Instructions