Cowrie Research

onekey

4 min read

OneKey

  • Name: OneKey
  • URL: https://onekey.so/
  • Category: hardware-wallet operator / signer-stack company / wallet-software and distribution boundary
  • Tags: bitcoin-ecosystem ethereum-ecosystem solana-ecosystem
  • Summary: OneKey belongs in companies/ because the practical authority is not only a multichain hardware wallet exists; it is that ONEKEY LIMITED sells the devices, ships the app and firmware stack, publishes the developer portal, operates the official store and support shell, and sets the legal/privacy perimeter users and integrators inherit. The project note stays useful for the signer mechanics and wallet surface. This entity note is for the named operator boundary around release workflow, hardware distribution, support routing, SDK packaging, and the trust shell above the OneKey product stack.
  • What it does:
    • Builds and sells OneKey hardware wallets, backup accessories, and related signer hardware through the official OneKey store
    • Operates the broader OneKey wallet stack across desktop, mobile, browser-extension, and web-app surfaces
    • Publishes the official developer portal for hardware transports, provider APIs, wallet-connect UI kits, and air-gapped QR signing flows
    • Maintains public app and firmware repositories under the OneKeyHQ GitHub organization
    • Runs the support, privacy, and user-agreement shell that governs store orders, app use, and developer-facing integration surfaces
    • Packages a broader company trust story around open-source claims, hardware-backed signing, official distribution, and multilingual customer-support channels
  • Key claims:
    • OneKey’s site-level structured data identifies the operator as ONEKEY LIMITED, headquartered in Hong Kong, founded in 2019, and describes the company as an open-source hardware-wallet company for multi-chain self-custody
    • The same official site metadata says the company is a member of SatoKey Group, which is useful context for the corporate boundary even if the hardware and wallet products are branded simply as OneKey
    • The official store metadata on onekey.so shows the same operator shell also controls worldwide hardware sales, support contact points, and payment acceptance for devices and accessories, so distribution is part of the trust boundary rather than an afterthought
    • The privacy policy says ONEKEY LIMITED is the data controller for the site and app, which makes the company note useful beyond product mechanics because the legal and data-handling boundary is explicit and first party
    • The user service agreement says the company develops and owns the OneKey mobile application and the first-party DApps on it, which sharpens the distinction between open-source product surfaces and the company-run service shell around them
    • The developer portal and GitHub organization make clear that OneKey is not only a device vendor; it also controls the official SDK, provider, transport, and wallet-connection packaging many downstream apps and users will inherit
  • Whitepaper: No standalone company whitepaper is the point here. The strongest primary-source snapshot remains ../whitepapers/onekey-primary-sources-2026-04-28.md, now complemented by the current site metadata plus the official privacy-policy and user-agreement pages.
  • Sources:

Internal linkages

Protocol / company boundary

  • Keep projects/onekey on the signer-product surface: hardware devices, companion-wallet behavior, transport and provider capabilities, and QR-based offline signing mechanics.
  • Keep this entity note on the named operator boundary: the company that ships firmware and app releases, sells the hardware, controls the official store and support workflow, publishes the developer portal, and sets the privacy / user-agreement perimeter users actually inherit.
  • That split matters because what can OneKey devices and software do? and which organization controls the release, distribution, legal, and integration shell around them? are related but not identical questions.

Control surface

  • Practical authority sits in firmware and app release workflow, official hardware-store distribution, support and replacement routing, SDK and provider packaging, privacy-policy and data-controller posture, and the company-run documentation surface that defines recommended signing and connectivity flows.

  • Even where the software is open source and the device is non-custodial, most users still inherit OneKey through company-shaped defaults: official binaries, store inventory, support guidance, hardware revisions, and the surrounding legal/privacy shell.

  • Read the durable risk here as who controls the signer stack's release and distribution shell?, not only as is the device non-custodial?

  • Last reviewed: 2026-08-08 UTC

Graph View

Backlinks