GridPlus primary-source snapshot
Fetched: 2026-05-01 UTC
1) Lattice1 introduction
Source: https://docs.gridplus.io/lattice1/lattice1-introduction
Selected excerpts from the official docs:
The GridPlus Lattice1 is a next-generation hardware wallet designed by crypto users for crypto users - created to be a digital asset management hub
One Lattice1 device + unlimited SafeCards = unlimited wallets.
Additional signals from the source:
- This page is the clearest top-level source for understanding GridPlus’s positioning around active digital-asset use, not just deep cold storage
- The SafeCard model is central: one device can manage many wallet identities and backups instead of assuming one permanent seed / one hardware unit
- The same page also lists direct integrations with MetaMask, Rabby, NuFi, Frame, MyCrypto, Ambire, and Lattice Manager, which makes the device look like a hub layered into existing wallet UX rather than a closed ecosystem
2) Lattice1 security features
Source: https://docs.gridplus.io/lattice1/security-features
Selected excerpts from the official docs:
The Lattice1 has a smaller attack surface than legacy hardware wallets because it’s got two totally separate hardware environments inside the box.
The GCE software runs on Linux and can connect to the internet … our security model operates under the assumption that it’s always compromised.
your private keys are completely inaccessible from the internet.
Additional signals from the source:
- This is the single most important page for classification because it details the General Compute Environment vs Secure Compute Environment split, the anti-tamper mesh, and the mailbox / multiplexer / doorbell communication design
- The docs also emphasize that the secure display is drawn by the SCE and that user input reaches the secure environment directly, which matters because GridPlus ties transaction readability to the security model itself
- The architecture is much richer than a generic “secure element + small screen” hardware-wallet story
3) First-time setup guide
Source: https://docs.gridplus.io/setup/lattice1
Selected excerpts/signals from the official docs:
The first step of the device setup is connecting your Lattice1 to the internet
We highly recommend arming the security mesh!
Additional signals from the source:
- The setup guide is valuable because it shows how GridPlus operationalizes the product: a network-connected device, PIN controls, mesh arming, wallet generation / restoration, and handoff into Lattice Manager or partner apps
- The docs also distinguish security tradeoffs for importing a hot-wallet seed versus generating a new wallet on hardware, which helps recover the intended user model
4) Lattice Manager docs
Source: https://docs.gridplus.io/apps-and-integrations/lattice-manager
Selected excerpts from the official docs:
The Lattice Manager is a GridPlus web tool which provides an interface for managing your Lattice.
Additional signals from the source:
- The Lattice Manager page exposes address tagging, wallet exploration, BTC send / receive flows, third-party connection management, and custom message-routing configuration
- This is a high-signal page for classification because it shows GridPlus operating a broader wallet-control-plane layer, not just shipping a device
5) GridPlus GitHub organization and SDK
Sources:
Selected excerpts/signals from the official repo/org:
SDK for communicating with the GridPlus Lattice1 hardware wallet
This SDK is designed to facilitate communication with a user’s Lattice1 hardware wallet.
Additional signals from the source:
- The SDK repo describes encrypted requests for address retrieval and transaction signing, confirming that GridPlus exposes a real developer surface around the device
- The organization page also exposes lattice-simulator, lattice-manager, lattice-cli, and release repos, which reinforces that the company ships software infrastructure around the device
6) Lattice Connect V2
Source: https://github.com/GridPlus/lattice-connect-v2
Selected excerpts from the official repo:
This open-source project provides Lattice1 owners a HTTP server which they manage themselves
If you would like to remove all connections to the GridPlus cloud, you will also need to erase some system settings and configure a custom device ID.
Additional signals from the source:
- This repo is especially important because it makes the vendor-routing model explicit: cloud routing exists by default, but users can replace it with their own local endpoint
- That self-hosted relay option is a strong sovereignty / privacy signal and one of the more unusual pieces of the public project surface
Notes
- GridPlus appears best cataloged as hardware-wallet infrastructure / signing and wallet-routing control plane / SafeCard-based self-custody architecture / self-hostable device connectivity.
- No canonical standalone whitepaper or litepaper surfaced in this pass.
- The most useful primary sources are the Lattice1 introduction + security docs, the Lattice Manager docs, and the SDK / routing repositories.