Skip to Content
HardwareConceptsChain Support

Chain Support

This page is the Hardware SDK public method matrix, not the OneKey App coin list. App marketing numbers (100+ chains, 30,000+ tokens) are wallet-catalog figures. Integrators should count only methods you can call on HardwareSDK.

Source of truth for Pro 2 / Neo: each Core method’s getSupportedProtocols(). Default is Protocol V1 only. A chain is on Pro 2 / Neo only when the method returns ['V1', 'V2']. Firmware min versions go stale; check the method page and the device firmware, do not copy them here.

Protocol V1 and V2 (Pro 2 / Neo)

FamilyPublic methodsClassic 1s / Touch / ProMiniPro 2 / Neo
EVMevmGetAddress evmGetPublicKey evmSignMessage evmSignTransaction evmSignTypedData evmVerifyMessageYesYesV1+V2
Bitcoin & forksbtcGetAddress btcGetPublicKey btcSignMessage btcSignTransaction btcVerifyMessage btcSignPsbtYes (see caveats)YesV1+V2 (Bitcoin). Neurai is V1-only
SolanasolGetAddress solSignMessage solSignTransaction solSignOffchainMessageYesYesV1+V2
AptosaptosGetAddress aptosGetPublicKey aptosSignMessage aptosSignTransaction aptosSignInMessageYes (see caveats)YesV1+V2
SuisuiGetAddress suiGetPublicKey suiSignMessage suiSignTransactionYesYesV1+V2
CosmoscosmosGetAddress cosmosGetPublicKey cosmosSignTransactionYesYesV1+V2
NEARnearGetAddress nearSignTransactionYesYesV1+V2
TONtonGetAddress tonSignMessage tonSignProof tonSignDataYes. Classic (not 1s): noAddress yes; sign/proof: noV1+V2
TRONtronGetAddress tronSignMessage tronSignTransactionYesAddress yes; sign message: noV1+V2
CardanocardanoGetAddress cardanoGetPublicKey cardanoSignMessage cardanoSignTransactionYesYesV1+V2
PolkadotpolkadotGetAddress polkadotSignTransactionYesYesV1+V2
Ripple (XRP)xrpGetAddress xrpSignTransactionYesYesV1+V2
FilecoinfilecoinGetAddress filecoinSignTransactionYesYesV1+V2
ConfluxconfluxGetAddress confluxSignMessage confluxSignMessageCIP23 confluxSignTransactionYesYesV1+V2
KaspakaspaGetAddress kaspaSignTransactionYesYesV1+V2
AlgorandalgoGetAddress algoSignTransactionYesYesV1+V2
NEMnemGetAddress nemSignTransactionYesYesV1+V2
NostrnostrGetPublicKey nostrSignEvent nostrSignSchnorr nostrEncryptMessage nostrDecryptMessageYesYesV1+V2
StarcoinstarcoinGetAddress starcoinGetPublicKey starcoinSignMessage starcoinSignTransaction starcoinVerifyMessageYesYesV1+V2

Protocol V1 only — not supported on Pro 2 / Neo

These methods declare Protocol V1 only. Do not call them on Pro 2 or Neo. Stellar, Alephium, and Neo (the chain, not the OneKey Neo device) are explicitly out of the Pro 2 / Neo set.

FamilyPublic methodsNotes
StellarstellarGetAddress stellarSignTransactionNot on Pro 2 / Neo
AlephiumalephiumGetAddress alephiumSignMessage alephiumSignTransactionNot on Pro 2 / Neo. Classic / Mini / Touch signing is listed in compatibility test exceptions
BenfenbenfenGetAddress benfenGetPublicKey benfenSignMessage benfenSignTransactionNot on Pro 2 / Neo. Classic is listed in compatibility test exceptions
NexanexaGetAddress nexaSignTransactionNot on Pro 2 / Neo
DynexdnxGetAddress dnxSignTransactionNot on Pro 2 / Neo. Pro / Classic 1s / Mini / Touch are listed in compatibility test exceptions
NervosnervosGetAddress nervosSignTransactionNot on Pro 2 / Neo
SCDOscdoGetAddress scdoSignMessage scdoSignTransactionNot on Pro 2 / Neo. Classic / Mini / Touch are listed in compatibility test exceptions
Neo (chain)neoGetAddress neoSignTransactionNot on Pro 2 / Neo. Classic / Mini / Touch are listed in compatibility test exceptions. Not the OneKey Neo device
LightninglnurlAuthNot on Pro 2 / Neo
EVM extraevmSignMessageEIP712Legacy typed-data path; prefer evmSignTypedData (V1+V2)

Device caveats (compatibility tests)

These are method/model combinations that repository compatibility tests permit to fail. This is a test-coverage limitation, not a fresh hardware test result. Do not advertise support for these combinations without validating the exact firmware and method on the device.

ModelDo not rely on
ClassicTON, Alephium, SCDO, Benfen, Neo (chain), btcSignPsbt, aptosSignInMessage
Classic 1s / PureDynex
MiniAlephium sign, Dynex sign, Neo (chain) sign, SCDO sign, TON sign/proof, TRON sign message. No BLE
TouchAlephium sign, Dynex sign, Neo (chain) sign, SCDO sign
ProDynex
Pro 2Chain methods with ['V1', 'V2'] above. Has camera (Air-Gap)
NeoSame chain methods as Pro 2. No camera, NFC, fingerprint, or Find My — no Air-Gap QR

EIP-7702 (authorizationList) is not supported on Classic.

Batch address helper

allNetworkGetAddress / allNetworkGetAddressByLoop are V1+V2 helpers. They still fail for a network whose own method is V1-only on a Protocol V2 connection.

Bitcoin forks

btc* methods take a coin / coin_name. Most forks follow the Bitcoin row (V1+V2). Neurai is Protocol V1 only.

How to decide at runtime

getSupportedProtocols() is a Core method-class hook, not a public HardwareSDK call. Use this page plus the live device:

  1. Does the SDK export the method?
  2. Is the device connectProtocol 'V1' or 'V2'?
  3. Does this page list the method as V1+V2, or V1-only?
  4. Does this model appear in the caveats table?
  5. Does the firmware meet the method page’s version line?

Do not branch on USB PID or BLE name. See Protocol V1 and V2 and Devices.

Next

Last updated on