LogoLogo
Open a Support Ticket!GridPlus.ioDiscordLattice Manager
  • Welcome!
  • Setup
    • Lattice1 Device Setup
  • Lattice1
    • Lattice1 Introduction
    • Lattice1 Security Features
      • Lattice1 Random Number Generation
    • How the Lattice1 Makes Transactions Readable with ABI Decoding
      • Advanced ABI Decoding
    • How to Manage Your Seed Phrase
    • Lattice1 Power Supply
    • Supported Digital Assets
    • Lattice1 WiFi Troubleshooting
    • Lattice1 Firmware Reference
    • Lattice1 Guides 🛠️
      • Update the Firmware
      • Verify That Your Lattice1 Is Authentic
      • View the Seed Phrase on Your Lattice and SafeCard
      • Claim Your "Verified Lattice1 Owner" POAP and Discord Role
      • Establish a Connection With Your Lattice1 via SSH
      • Connect to WiFi Using SSH
      • Disable Wifi When Connected via Ethernet Using SSH
      • Managing ETH Validator Keys
  • SafeCards
    • Introduction to SafeCards
    • Setting up a New SafeCard
    • SafeCard Operations
    • Lattice1 Doesn't Recognize the Inserted SafeCard
    • SafeCard CLI
  • Apps & Integrations
    • Lattice Manager
      • Managing Your Bitcoin Wallet
      • Creating Custom Address Tags
      • Using the Wallet Explorer
      • Connecting Your Lattice to Your Own Private Endpoint
      • Lattice Manager Troubleshooting
      • How to View the XPUB of Your Bitcoin Wallet
    • MetaMask
      • Installing MetaMask
      • Connecting to MetaMask
      • Advanced MetaMask Setup
      • MetaMask Troubleshooting
    • NuFi
      • Connecting to NuFi
    • Frame
      • Installing Frame
      • Connecting to Frame
      • Advanced Frame Setup
    • Rabby
      • Connecting to Rabby
      • Rabby Troubleshooting
    • MyCrypto
      • Connecting to MyCrypto
      • MyCrypto Troubleshooting
    • Ambire Wallet
      • Connecting to Ambire
    • Eidoo App (Mobile)
  • Additional Resources
    • Payment, Shipping, Delivery
    • GridPlus Affiliate Program
    • Developer Resources
    • GridPlus Brand Assets
    • Bug Bounty & Responsible Disclosure Policy
  • Blockchain Basics
    • Introduction
    • Wallets
    • A Brief Introduction to Private Keys
    • Blocks & Consensus Mechanism
    • UTXO vs. Account Model
    • Bitcoin
    • Ethereum
      • Smart Contracts
      • ERC-20 tokens
      • NFTs
      • Layer 2s
Powered by GitBook
On this page
  • Latest Firmware
  • The Process
  • Update Security
  1. Lattice1
  2. Lattice1 Guides 🛠️

Update the Firmware

PreviousLattice1 Guides 🛠️NextVerify That Your Lattice1 Is Authentic

Last updated 1 year ago

Latest Firmware

If you're looking for what's new, you can find the latest firmware revision on our GitHub, along with the full revision history.

The Process

The Lattice1 will check for updates to the HSM firmware automatically every 6 hours. Once an update is available, the device will prompt you to confirm the installation of the new update manually.

Then all you need to do is kick back and watch the progress bar for a minute or two. Your device will reboot and you’ll be back in action with an upgraded Lattice1.

The HSM update will never be installed without your approval. However, we strongly recommend you upgrade to every single new update available.

You can also check if an update is available manually without waiting for the regular 6-hour scan if you go to System Preferences → Software Update on your Lattice1.

Also, if you want to make sure what firmware revision you have in your device, you can check this if you go to System Preferences → Device info.

Check out the current version of our firmware with explanation for each function here:

Update Security

The device is made up of two elements (the HSM/SCE and the GCE) - the GCE that runs a simple Linux system updates automatically (far less often than the SCE), but every single part of the device is constructed with the idea that the GCE is vulnerable at all times - this means that no part of the system that handles secure data is ever exposed to the update.

In other words, funds are safu.

The Linux GCE is also updated - the updates are very infrequent and automatic - you're not prompted to approve them. These happen completely outside of the secure chip running the firmware and do not touch any secure data or private keys.

How can we safely update your secure hardware over the air like this? Every release must be signed by multiple GridPlus private keys which are separated geographically so your device can verify the provenance of the release. The secure bootloader will reject any updates that do not meet these strict criteria before installing anything. You can also use the to make sure your Lattice1 is authentic - no other device can receive our update.

verification tool
LogoLattice1 Firmware ReferenceGridPlus
LogoGitHub - GridPlus/lattice-firmware-history: History of Lattice firmware updates and corresponding changesGitHub