Solflare Hardware Wallet Support Roadmap: When Will It Support Trezor and AirGap?

A Solana user with a hardware wallet faces a practical friction point. Solflare, the leading non-custodial wallet for Solana, supports Ledger Nano S and Keystone hardware devices, but not Trezor, AirGap, or several other mainstream hardware platforms. For users who have invested in those devices for security or who prefer their particular signing workflow, the lack of compatibility creates a choice: accept software-only custody, find an alternative Solana wallet, or adopt a workaround that may sacrifice some convenience.

The question is not whether Solflare works well for its supported hardware. Ledger integration is mature and straightforward; Keystone’s air-gapped approach appeals to users who want signing separated from a network-connected device. The strategic question is why those two platforms dominate Solflare’s hardware roadmap and whether the ecosystem is likely to expand. Understanding the constraints—technical, commercial, and operational—can help users decide whether to wait for broader support, migrate to an alternative, or implement a hybrid approach that combines Solflare’s strengths with other tools.

Current hardware wallet support: Ledger and Keystone only

Solflare’s integration with Ledger and Keystone reflects two different security models, both valuable but operationally distinct. Ledger integration allows a Nano S, Nano X, or Nano S Plus device to store the master private key while Solflare handles the user interface, transaction construction, and interaction with the Solana blockchain. When a transaction is initiated, Solflare displays the details on the browser or mobile screen, but the signing operation itself occurs on the Ledger device, where the user confirms the action and the Ledger firmware applies its own verification rules.

This design keeps the most sensitive operation—private key signing—isolated from any network-connected machine. A compromised browser, malicious website, or supply-chain attack on Solflare itself cannot extract the private key or forge transactions without physical confirmation on the hardware device. Ledger’s maturity in this space, its install base among cryptocurrency users, and its Solana app availability made it a logical first choice for Solflare’s development team.

Keystone represents a different philosophy. Rather than connecting to a computer or phone via USB or Bluetooth, Keystone operates as a fully air-gapped device. Communication occurs through QR codes: the user’s main device generates an unsigned transaction as a QR code, displays it on screen, the user scans it with the Keystone hardware device, reviews it on the Keystone’s own screen, and confirms the signing. The signed transaction is then encoded as another QR code and scanned back into Solflare. This workflow eliminates any direct electronic connection between the signing device and the internet, a meaningful advantage for users who suspect their computer may be compromised or who prefer not to rely on USB driver security.

Both approaches succeed because Solflare designed clear, step-by-step flows for each. The difficulty is replicating that effort for every hardware wallet platform that exists. Trezor, AirGap Vault, Ngrave, SafePal, and others each have different signing protocols, driver requirements, approval flows, and UI expectations. Supporting each one requires engineering time, security testing, and ongoing maintenance as firmware versions and APIs change.

Why Trezor and AirGap are not yet integrated

Trezor has been slower to appear in Solflare’s roadmap despite being widely adopted. Part of the reason is technical: Trezor’s Solana support came later than Ledger’s, and the Trezor team prioritized firmware development for larger ecosystems first. There is no conspiracy here, simply resource allocation. Trezor’s strongest user bases have historically been Bitcoin and Ethereum holders; Solana was initially less central to the platform’s development priorities.

AirGap Vault faces a different constraint. AirGap’s air-gapped design is conceptually similar to Keystone—signing happens offline and communication occurs through QR codes. However, AirGap Vault’s mobile-first approach and its reliance on a separate AirGap Wallet app as the network-connected companion creates integration complexity that Solflare would need to test and maintain. The two-device model is not inherently problematic, but it introduces more states and edge cases than Ledger’s single connection or Keystone’s straightforward scan-and-sign flow.

Commercially, hardware wallet integrations also follow market signals. Solflare’s parent company, Dokia Capital, has visibility into which hardware wallets its users actually own. If the majority of Solflare users with hardware wallets are using Ledger, the return on investment for supporting Trezor or AirGap is lower. This is not cynical; it is rational prioritization. A small team allocates time where it provides the most value to the largest user base.

Community requests and GitHub issues can influence this calculus, but they are not always decisive. A hundred comments asking for Trezor support may come from fifty users, while a handful of Ledger users might represent thousands of transactions. The visibility of user demand does not necessarily match the actual prevalence of the hardware. Solflare could prioritize incorrectly if it relies solely on vocal feedback rather than transaction data or user surveys.

The workaround landscape for unsupported hardware

Users with Trezor, AirGap, or other unsupported hardware have several practical options, each involving different trade-offs. The most straightforward is to operate Solflare as a software wallet, deriving the same keypair from a 12 or 24-word seed phrase that the hardware wallet also controls. This requires importing the seed into Solflare, effectively giving the private key to the software application. If the computer is compromised or the seed is mishandled, the security advantage of the hardware wallet is lost, but the approach works functionally.

A more secure variation is to create a separate Solflare-only keypair that is never exposed to the hardware device. The user generates a new seed in Solflare, backs it up offline, and treats the Solflare wallet as a “hot wallet” for smaller amounts or frequent operations. Larger or longer-term holdings remain on the hardware wallet, accessed through Solflare’s software wallet mode when necessary, or through an alternative tool that does support the hardware device. This splits the risk: daily transactions use software-only custody, while significant balances remain hardware-protected.

A third option is to use a different Solana wallet that does support the user’s hardware. Solflare wallet is excellent for Solana-native use, but it is not the only option. Other non-custodial wallets such as Phantom or Magic Eden offer software implementations, while some tools support broader hardware compatibility. The trade-off is leaving Solflare’s ecosystem and potentially losing features such as built-in staking, integrated NFT storage, or the specific interface design that users prefer.

For users with higher security demands, a final option is to manage keys offline using Solana’s command-line tools and interact with Solflare through its public API or JSON-RPC, signing transactions with a hardware device through a separate signing flow. This is technical, requires familiarity with command-line operations, and defeats much of the point of using a user-friendly wallet. However, for advanced users who prioritize maximum control and security, it is available.

Technical barriers to expanding hardware support

Adding hardware wallet support to Solflare requires building against each device’s specific APIs and firmware. Ledger uses the Ledger Live framework and provides SDKs for browser extensions and mobile apps; integrating a new chain or device requires implementing the correct BIP32 derivation path, signing protocol, and approval screen flow. Keystone uses a different QR-code-based protocol that Solflare had to design around from scratch.

Trezor’s integration would require implementing Trezor’s signing protocol, managing USB communication (on desktop) or bridge services, and testing across firmware versions. AirGap Vault would involve coordinating between the Vault app (signing) and the AirGap Wallet app (broadcast), requiring careful state synchronization and error handling if the scan fails or the transaction is rejected. Each integration is not merely a matter of writing a few API calls; it requires security review, user testing, and handling edge cases such as device disconnection, firmware updates, or user error.

The Solana ecosystem’s blockchain structure does not inherently make hardware support harder or easier than on Bitcoin or Ethereum, but Solana’s transaction model has some specific quirks. Transactions include rent-bearing accounts and may require signers beyond the wallet owner. Hardware wallets must display these details accurately, which means Solflare must format transactions in a way that each hardware device can understand and display properly. Misalignment between what Solflare shows on screen and what the hardware device shows could create security theater—users might approve a transaction they do not actually understand.

Maintenance is an ongoing burden that many teams underestimate. Each hardware wallet manufacturer releases firmware updates, changes APIs, or discovers security issues. Solflare’s integrations must remain compatible with these changes. A single breaking change in Ledger’s API could disable Solflare’s hardware support until the update is released and deployed to users. Supporting more hardware means more platforms to monitor and update.

Mobile and browser differences complicate the roadmap

Solflare offers both a browser extension and mobile applications, and hardware support differs between them. The browser extension can integrate with Ledger Live on desktop systems using USB or Bluetooth. Mobile versions face different constraints: iOS has strict permissions around USB communication, and Bluetooth can be unreliable depending on the device. Android offers more flexibility but still requires careful driver management.

AirGap Vault, designed for mobile air-gapping, may be more practical on mobile than on desktop, but coordinating the QR-code-based signing flow through Solflare’s mobile interface introduces complexity. Keystone hardware on mobile operates more smoothly because it relies on camera scanning rather than direct device communication. Ledger on mobile requires a Bluetooth connection, which works but is not universally preferred.

Supporting hardware across both the browser extension and mobile app essentially doubles the engineering work. A hardware integration that works on desktop may require a completely different implementation on iOS or Android. This is partly why Solflare’s team has progressed cautiously: the apparent simplicity of “add Trezor support” masks a matrix of platform combinations, each requiring testing and maintenance.

The roadmap is also affected by the fact that Solflare’s users are not uniformly distributed across browser extension and mobile. If most hardware-wallet users use the browser extension, mobile support for additional hardware becomes lower priority. Understanding these usage patterns requires data that is visible to Dokia Capital’s team but not necessarily public, which can make the roadmap appear inscrutable to external observers.

What would accelerate broader hardware support

The most direct catalyst would be standardized hardware wallet protocols that all manufacturers adopt. If Trezor, Ledger, Keystone, AirGap, and others all implemented a common signing API, wallet developers could write integration code once and deploy it across all hardware platforms. This would require industry coordination that has not yet materialized. Standards bodies such as the Crypto Open Standard Alliance (COSA) or emerging blockchain standards do not yet enforce hardware wallet interoperability.

Increased user demand, particularly from paying customers or institutional users, could prioritize hardware support higher in Dokia Capital’s roadmap. If a significant portion of Solflare’s users request Trezor support and voice willingness to pay for premium features, that calculus changes. Currently, Solflare is free to use, which means the revenue incentive to accelerate hardware support is indirect.

Community-driven development could also accelerate progress. If Trezor’s team or AirGap’s maintainers contributed integration code to Solflare, the burden on Dokia Capital’s engineering team would decrease. Open-source projects can benefit from external contributions, but accepting code requires security review, testing, and maintenance assumptions that the core team must still bear.

Hardware wallet manufacturers themselves could invest in supporting Solana more broadly. If Trezor released a robust Solana app with full feature support, and their team reached out to wallet developers, adoption would be faster. Conversely, if Solana’s ecosystem continues to grow and Solflare remains the leading non-custodial wallet, manufacturers may prioritize Solflare integration more aggressively to reach Solana users.

Using Solflare securely with current hardware options

For users choosing between Ledger and Keystone with Solflare, or deciding whether to use solflare browser extension setup guide with hardware or software custody, the decision depends on threat model and workflow. A Ledger Nano S or Nano X is a USB device, familiar to many users, with a large ecosystem of compatible tools. It works with Solflare’s browser extension seamlessly on Windows, Mac, or Linux, and with mobile apps via Bluetooth.

Keystone is air-gapped, eliminating direct electronic connection to the signing device, which is valuable if the user suspects supply-chain attacks or compromised computers. The QR-code-based workflow is slower than USB but more transparent—the user scans and reviews the transaction with their eyes rather than trusting a USB driver to transmit data accurately. For users with high holdings or long-term cold storage, this additional friction is often preferred.

If neither Ledger nor Keystone is an option, and the user owns Trezor or AirGap, the pragmatic choice is to create a separate Solflare software-only wallet for hot usage and continue using the hardware device for larger balances through an alternative tool or by importing the seed into Solflare (with the understanding that this sacrifices hardware signing for that portion). This hybrid approach accepts some risk on the hot portion while maintaining hardware security for the majority of funds.

Solflare security depends ultimately on protecting the seed phrase and controlling which device signs transactions. Hardware wallet support is valuable, but it is not the only security consideration. A user with a Ledger can still expose the private key by writing down the seed incorrectly, sharing it in an email, or using it on a compromised computer. Conversely, a user who treats their Solflare software wallet with discipline—keeping the seed offline, using strong passwords, and not importing it into untrusted applications—can achieve reasonable security even without hardware signing.

The realistic timeline for future hardware integrations

Predicting when Solflare will support Trezor or AirGap requires understanding the team’s capacity and priorities, which change as the Solana ecosystem evolves. If Solflare’s user base grows significantly, Dokia Capital may expand the team and allocate engineers specifically to hardware integrations. If Solana’s market importance declines relative to other chains, the company might shift focus elsewhere.

Based on public statements and GitHub activity, there is no announced timeline for new hardware support. This does not mean the company is against it; it more likely reflects uncertainty about when resources will be available and whether the payoff justifies the effort. A realistic expectation is that new hardware support, if it comes, would arrive incrementally: perhaps Trezor support arrives in 2025 or 2026, followed later by other platforms.

Users who absolutely require unsupported hardware should plan now rather than wait. Migrating to a compatible wallet, adopting a hybrid approach, or accepting software-only custody are all viable strategies, each with trade-offs. Betting on “Solflare will support my hardware eventually” is not a secure custody strategy; it is speculation.

The broader lesson is that wallet support is not delivered evenly across all platforms, and users should make purchasing decisions with the ecosystem already in mind. If a hardware wallet is important, ensure it works with the wallet software you prefer before buying the device. If you already own unsupported hardware, Solflare’s Ledger and Keystone options, combined with hybrid custody strategies, provide workable alternatives for most users.