OneKey

• Name: OneKey
• URL: https://onekey.so/
• Category: hardware wallet / wallet control plane / hardware-backed signing and offline-signing infrastructure
• Tags: bitcoin-ecosystem ethereum-ecosystem solana-ecosystem
• Summary: OneKey is a multichain hardware-wallet stack with the usual companion-app sprawl: devices, wallet software, transport libraries, provider APIs, and QR signing. Useful note, but keep it in proportion. This is signing infrastructure, not a new custody model. The named operator boundary around firmware/app release workflow, official hardware distribution, developer-portal packaging, and the legal/privacy shell now lives separately in onekey.
• What it does:
  • Sells hardware devices and backup accessories for self-custody, including battery-powered and battery-free variants plus a BTC-only edition
  • Operates software wallet surfaces across desktop, mobile, browser extension, and web app contexts
  • Publishes a developer portal for hardware transport integrations over USB and BLE, dApp provider APIs, and wallet-connection UI kits
  • Supports offline signing flows using UR-encoded QR exchanges for Ethereum/EVM, Bitcoin PSBT, Solana, and Tron transactions
  • Maintains open-source app and firmware repositories and positions the product as non-custodial, with private keys and recovery seeds kept out of OneKey custody
• Key claims:
  • The official homepage positions OneKey as a hardware wallet and crypto DeFi wallet with multiple device SKUs, backup products, and broad asset support
  • The GitHub organization states that OneKey will not store private keys or recovery seeds and that its hardware and software are open source
  • The developer portal frames OneKey as infrastructure for integrating secure hardware-backed signing into dApps, wallets, and blockchain stacks
  • The Provider API docs describe a unified interface for requesting accounts, signing, and sending transactions across EVM, Bitcoin, Solana, Cosmos, Move, and other ecosystems
  • The air-gap docs show a device-stays-offline signing flow using animated QR payloads and signature exchange, with example implementations in the public hardware SDK repository
• Whitepaper: No canonical OneKey whitepaper or litepaper surfaced in this pass. The clearest current source of truth is the official developer docs, GitHub organization and repositories, and product site; see ../whitepapers/onekey-primary-sources-2026-04-28.md.
• Sources:
  • https://onekey.so/
  • https://developer.onekey.so/en/
  • https://developer.onekey.so/en/connect-to-software/provider/
  • https://developer.onekey.so/en/air-gap/
  • https://github.com/OneKeyHQ
  • https://raw.githubusercontent.com/OneKeyHQ/app-monorepo/refs/heads/onekey/README.md

Internal linkages

• Company / operator boundary for release workflow, hardware distribution, official support, and developer-portal packaging: onekey.
• Best upward reads: foundation-devices, coinkite, and sparrow-wallet.
• OneKey is mostly a broad multichain signer stack. Compare it upward to stronger hardware roots and to software-heavy operator surfaces, not sideways to every wallet vendor with a browser extension.

Protocol / company boundary

• Keep this note on the product surface: hardware devices, companion-wallet behavior, transport libraries, provider APIs, and QR-based offline-signing mechanics.
• Use onekey for the named operator layer above that stack: the company that ships firmware and app releases, runs the store and support shell, publishes the developer portal, and sets the legal/privacy perimeter users and integrators inherit.
• That split matters because what can OneKey signers and wallet software do? and which organization controls the release, distribution, and support shell around them? are related but not identical questions.

Control surface

• At the product layer, the important leverage sits in transport support, provider semantics, offline-signing UX, supported chains, and how the companion wallet makes hardware-backed signing feel default.

• Do not overstate it: this is still a broad signer stack, not a new custody primitive.

• For release workflow, official device distribution, support routing, and the broader company-run trust shell above the product surface, read onekey.

• Last reviewed: 2026-08-08 UTC