A user connects a GridPlus Lattice1 hardware wallet to their browser and opens the Rabby wallet extension in Chrome, expecting a straightforward pairing. Instead, they see repeated “Verification Pending” messages, disconnections mid-confirmation, and screens that ask to re-authenticate the device multiple times before a single transaction can be signed. The Lattice1 is widely recognized as a secure hardware device, yet the pairing process with this particular Ethereum wallet feels broken. The problem is not necessarily that the wallet or device is faulty; it is that the connection protocol between GridPlus and Rabby has specific requirements that are rarely documented clearly, and skipping even one verification step can force the entire sequence to restart.
This article addresses the practical troubleshooting steps that GridPlus Lattice1 users need to follow when setting up or reconnecting a hardware wallet through a browser-based application. The issue affects not only Rabby but other EVM wallets that rely on standardized hardware wallet protocols. Understanding the root causes—device firmware synchronization, browser cache behavior, permission persistence, and network communication order—can transform a frustrating 45-minute loop into a reproducible, resolvable process. Users who follow the correct sequence will avoid the most common failure modes and maintain the security that a hardware wallet is designed to provide.

Why GridPlus Lattice1 disconnection loops happen in the first place
The GridPlus Lattice1 is an air-gapped hardware wallet that communicates with applications only through QR code scanning or a paired network connection. When you connect it to a Rabby wallet extension, the device and the wallet must establish a secure channel. This channel requires several handshakes: the device must broadcast its identity and supported derivation paths, the wallet must request permission to access specific accounts, and the device must confirm that the wallet application is authorized. If any of these steps are interrupted—a browser tab crashes, a USB connection is loose, the device enters sleep mode, or the browser cache becomes stale—the entire sequence breaks and may require a restart.
The Lattice1’s architecture compounds the issue because it separates signing from broadcasting. The device does not connect directly to blockchain nodes. Instead, it sits between your computer and the network, acting as a gatekeeper. The Rabby wallet extension must therefore manage both the hardware wallet protocol (communicating with the device) and the blockchain protocol (sending transactions to the Ethereum network or EVM chains). A timeout in one channel does not always cleanly propagate to the other, leaving the wallet in an ambiguous state where it believes the device is still connected but the device has moved on or gone to sleep.
Browser cache is a major culprit. The rabby wallet extension stores session data, device identifiers, and connection state in the browser’s local storage. If this cache becomes out of sync with the device’s current state, the extension may attempt to reuse a stale session token or account derivation path. The device rejects the request because it does not recognize the token, but the wallet does not clear the cache and retry with fresh credentials. Instead, it loops back to the verification screen, showing the same error repeatedly. A full cache clear often resolves this, but many users do not realize that is the first step.
Rabby setup and hardware wallet support: The pre-connection checklist
Before connecting the GridPlus Lattice1, confirm that several preconditions are met. First, the device firmware must be current. GridPlus releases firmware updates that improve protocol compatibility, fix race conditions, and add support for new wallet applications. Connecting an outdated Lattice1 to a wallet that expects a newer protocol version will produce verification failures that look like connection problems but are actually firmware incompatibility. Visit the GridPlus website, download the latest firmware to a USB drive, and update the device before proceeding.
Second, the browser itself must be fully updated. Chrome, Brave, Edge, Opera, and Arc each handle browser extensions differently, and older versions may not properly implement the persistent storage or background messaging protocols that Rabby relies on. An out-of-date browser can cause the extension to lose track of the device between page reloads or when the tab enters the background.
Third, ensure that the Lattice1 is in an awake, responsive state. The device enters a low-power mode after several minutes of inactivity, and waking it mid-connection can disrupt the handshake. Touch the device screen or press a button to confirm it is responsive before launching the wallet extension.
Fourth, if you are re-connecting a device that was previously paired with Rabby, clear the browser extension’s local storage entirely. Do not just refresh the page or log out. Open your browser’s developer tools, go to Application > Local Storage, find the Rabby entry, and delete it. Then close the extension completely and reopen it. This step is non-negotiable for second or subsequent connections, as stale credentials are the most common cause of repeated verification loops.
The three-step verification sequence that actually works
After clearing cache and updating firmware, follow this exact sequence. Do not skip or reorder steps.
Step One: Open Rabby and initiate hardware wallet detection. Open the extension, click “Add Account” or “Connect Hardware Wallet,” and select “GridPlus Lattice1” from the list of supported devices. The wallet will immediately begin scanning for available Lattice1 instances on your local network (if using network mode) or prompt you to authorize the connection via USB. Do not press any buttons on the Lattice1 yet. Wait 10 seconds for the extension to broadcast its availability announcement. This is a listening phase, and interrupting it can cause the device to miss the initial pairing request.
Step Two: Confirm the pairing on the device itself. The Lattice1 will display a confirmation screen asking whether you want to authorize the requesting application (Rabby). You will see the wallet name and a prompt to confirm or reject. Press “Confirm” on the device. This step is critical because it creates a cryptographic signature that proves the device authorized the connection. If you press “Confirm” but the browser is frozen or loading, the device will time out and return to its home screen after 30 seconds. If this happens, do not immediately retry on the browser side. Instead, repeat Step One from the browser.
Step Three: Allow the wallet to retrieve account information. After confirming on the device, the wallet will request a list of available accounts (the specific Ethereum addresses derived from your seed phrase using the device’s keypath). This request may take 5–10 seconds because the device is deriving addresses and preparing to show them on its screen. The browser will display “Verifying Accounts” or a similar message. Do not click anything. Wait for the process to complete. Once it finishes, the wallet will display a list of addresses that you can select from. Choose the account you want to use and click “Connect.”
If the wallet shows “Verification Pending” after Step Three and does not advance after 30 seconds, the connection has likely timed out. Close the Rabby extension completely (right-click the extension icon and select “Manage Extensions,” then disable and re-enable Rabby). Do not clear cache this time unless this is the second failure. Re-open Rabby and start from Step One again. One retry usually succeeds; a second retry often indicates a deeper issue such as outdated firmware or a browser permissions problem.
Permission persistence and why re-verification loops repeat
A subtle issue occurs when the browser extension’s permissions become stale or misaligned with the device’s internal state. The Lattice1 maintains an internal list of applications it has authorized. If Rabby is on that list but the extension’s local copy of the authentication token has expired, the device will recognize Rabby as a known application but reject its requests because the token does not match the device’s current security context. This is a security feature—it prevents malicious code from reusing old tokens—but it creates a user experience where each transaction or account access triggers a new verification step.
To resolve this, you must revoke and re-authorize the connection at the device level. On the Lattice1, navigate to Settings > Connected Apps or a similar menu (exact names vary by firmware version). Find “Rabby” or the wallet application in the list and select “Revoke” or “Remove.” This clears the token from the device. Then re-pair the wallet by starting again at Step One. The new connection will create a fresh token that matches the browser extension’s session data.
Another permission issue arises from browser-level restrictions. Some users enable “Strict” privacy modes or use browser extensions that block local network access. The Lattice1 communicates over your local network, and if the browser cannot reach it, the wallet will fail to detect the device even though it is physically connected and powered on. Check your browser settings and any privacy extensions you have installed. Temporarily disable script blockers, tracker blockers, or network-restriction extensions when pairing the hardware wallet.
Diagnosing whether the problem is the device, the wallet, or the browser
When troubleshooting, isolate the variable. If Rabby shows “Device Not Found” or “Connection Failed,” try connecting the same Lattice1 to a different wallet application (such as MetaMask or Frame). If the Lattice1 connects and works with another wallet but fails consistently with Rabby, the issue is likely in the Rabby extension or browser configuration, not the device. If the Lattice1 fails to connect with all wallets, the issue is on the device side: check firmware, restart the device, or test it on a different computer.
Browser-specific issues can be ruled out by testing on a different browser. If Rabby works with your Lattice1 in Firefox but not in Chrome, the problem is browser-specific. Clear Chrome’s cache entirely (Settings > Privacy and Security > Clear Browsing Data > All Time), then uninstall and reinstall the Rabby extension. If the issue persists, switch to a different browser for that wallet until you identify which browser has the underlying problem.
You can also inspect the extension’s error logs. Open your browser console (F12), navigate to the Rabby extension’s background page, and check for JavaScript errors or failed API calls. Look for messages mentioning “timeout,” “unauthorized,” or “device not responding.” Screenshots of these errors can be valuable if you need to report the issue to the Rabby development team through their GitHub repository or support channel.
Hardware wallet support across other devices and lessons for future pairing
Rabby supports multiple hardware wallets beyond GridPlus: Ledger, Trezor, Keystone, OneKey, and BitBox02 each have different connection protocols and firmware requirements. The same fundamental principles apply across all of them. Clear cache before re-pairing, update firmware, confirm the connection on the device, and wait for the wallet to retrieve account information without interruption. The specific menus and confirmation screens vary, but the timing and sequence are consistent.
Ledger and Trezor typically connect via USB and have simpler connection flows because they do not require local network setup. However, they also require that you unlock the device and sometimes confirm that you want to allow a new application to access it. BitBox02 and OneKey involve similar approval steps on the device itself. Keystone is entirely air-gapped and requires QR code scanning, which adds a different set of potential failure points (poor camera focus, incorrect QR alignment, stale QR data) but avoids the network timing issues that sometimes affect networked hardware wallets.
The common thread is that every hardware wallet connection is a multi-stage handshake, and interrupting any stage forces a restart. Users who understand this are less likely to abandon the process mid-way or try to force a retry before the device has finished responding. Patience—waiting 10–30 seconds at each stage without clicking—is often the solution to what appears to be a technical failure.
When to seek help and what information to provide
If you have followed the three-step sequence, cleared cache, updated firmware, and tested on a different browser or device, and the Lattice1 still cannot connect to Rabby, you have exhausted the most common fixes. At that point, contact GridPlus support, the Rabby development team (through GitHub), or both, depending on where you suspect the problem lies.
When reporting the issue, provide the following information: your browser name and version, the Lattice1 firmware version (shown in Settings on the device), the Rabby version (check the extension details page), your operating system (Windows, macOS, Linux), and a step-by-step description of what you did and where the failure occurred (e.g., “Device appears after Step One but verification times out during Step Three”). Include screenshots of error messages and browser console errors if available. Do not include your wallet addresses, seed phrase, or any private information.
The Ethereum protocol and its EVM implementations rely on standard wallet-to-application communication patterns, but wallet applications interpret these standards differently. A problem that occurs in Rabby may not occur in another wallet because the implementation details differ. Providing specific details helps developers identify whether the issue is in the wallet, the browser, the hardware wallet protocol library, or an environmental factor specific to your setup.
Preventing future disconnections and maintaining stable pairing
Once you have successfully connected your Lattice1 to Rabby, keep the connection stable by following these practices. First, enable “Auto-Lock” on the Lattice1 but set the timeout to at least 10 minutes when you are actively using the wallet. A shorter timeout (1–3 minutes) can cause the device to enter sleep mode while Rabby is still attempting to retrieve transaction details, creating a mid-process disconnection.
Second, avoid connecting the same Lattice1 to Rabby on multiple devices simultaneously. The device maintains one active connection at a time, and if you have the wallet open on your laptop and phone at the same time, whichever device tries to transact second will find the connection blocked or throttled. If you switch devices, wait 30 seconds after fully closing Rabby on the first device before opening it on the second.
Third, keep your browser cache clean but do not obsess over it. Clear cache after you have finished your session (e.g., once a week), but do not clear it between individual transactions. Clearing cache during a session can disrupt your connection. However, if you notice that transactions are taking longer to confirm or that the wallet is becoming sluggish, a full cache clear may help.
Fourth, use the address checker tool that Rabby provides. Before signing a transaction, confirm that the destination address is correct and matches what you intended. A typo in a blockchain address cannot be undone, and hardware wallets are designed to protect your keys but not to protect you from sending funds to the wrong address. The wallet’s simulation features will show you the likely outcome of a transaction, but it is your responsibility to verify the destination.
Frequently asked questions
Why does my GridPlus Lattice1 keep asking for verification after I have already confirmed it?
The most common cause is stale browser cache. The extension’s local storage contains an expired authentication token, and the device rejects it. Clear your browser’s local storage for the Rabby extension entirely (right-click the extension, go to “Manage Extensions,” then navigate to Storage settings and delete Rabby’s stored data). Restart the extension and attempt to reconnect. If you are re-pairing after a previous successful connection, also revoke the app from the Lattice1’s settings before re-pairing.
Does the rabby wallet extension work with any hardware wallet other than GridPlus?
Yes. The rabby wallet extension supports Ledger, Trezor, Keystone, OneKey, and BitBox02 in addition to GridPlus. Each device has a different connection protocol, but the same principle applies: update firmware, clear cache before re-pairing, confirm the connection on the device itself, and wait for account information to load without interruption. BitBox02 and Keystone require additional setup steps (such as choosing a name for the wallet on the device) that do not apply to USB-connected wallets like Ledger or Trezor.
What should I do if clearing cache and updating firmware do not fix the problem?
Test the Lattice1 with a different wallet application (MetaMask or Frame) to determine whether the issue is specific to Rabby. If it connects to another wallet, the problem is likely in Rabby’s implementation or your browser configuration. Try a different browser to rule out browser-specific issues. If the Lattice1 fails to connect with all wallets, contact GridPlus support. When contacting Rabby developers, provide your browser version, firmware version, operating system, and a detailed description of where the process fails, along with browser console errors if available.