Pair over the same codes Sparrow, MetaMask, Rabby and Solflare already understand.
Back to home
Keep your wallet
Keys stay put
Checked against Ownbit
Public protocol
One cold signer for the wallets you already use
An Ownbit cold wallet now speaks the same published QR standards other wallets already read. Pair it once, then sign their transactions on an offline phone — the other wallet only ever sees public keys and finished signatures.
Android 5.xPublished QR standardsOffline signing
BTCETHBSCARBOPMATICSOLTRX
Pairing shares public keys only. Signing happens on the offline phone and comes back as a code.
Every pairing code is re-derived and compared with Ownbit’s own addresses before it is shown.
What it does
A signer that other wallets already know how to talk to
No bridge app and no private format. Ownbit exports and answers the QR types these wallets were already built to read.
Published formats
Pairing and signing use the public BC-UR types, plus BBQR and PSBT files for Bitcoin.
Four chain families
Bitcoin, EVM networks, Solana and TRON, from one recovery phrase.
Watch-only on the other side
The online wallet tracks balances and builds transactions. It never receives a key.
The whole request, in full
Amount, destination, network and contract data are decoded and shown before you approve.
Addresses cross-checked
Before any code is shown, the addresses are re-derived and matched against Ownbit’s own.
No new hardware
A spare Android phone is the signer. Nothing to buy, ship or trust in the supply chain.
How it works
Three codes, one direction at a time
Nothing but a camera connects the two phones. There is no cable, no pairing server and no network on the cold side.
Protocol
What is exported, and what comes back
The full field-level reference, including how to decode a code by hand, lives in the docs.
| Chain | Pairing export | Signing request → response |
|---|---|---|
| Bitcoin | crypto-account (account XPUB) or a plain address | crypto-psbt → crypto-psbt |
| EVM | crypto-hdkey (account node) or a plain address | eth-sign-request → eth-signature |
| Solana | crypto-multi-accounts or a plain address | sol-sign-request → sol-signature |
| TRON | address #0 | tron-sign-request → tron-signature |
Scope, stated plainly
The public protocol covers personal wallets on standard derivation paths — not Ownbit MultiSig wallets, which keep using Ownbit’s own co-signing flow. TRON shares address #0 only. It ships on Android 5.x today.
Compatibility
Wallets on the other end
Grouped by what they do with an Ownbit pairing code: sign a full round trip, or watch balances only.
Pair and sign
full round tripImport the pairing code, build a transaction, show the request, and take the signature back.
SparrowBTC
BlueWalletBTC
NunchukBTC
Bitcoin KeeperBTC
SpecterBTC
Bitcoin SafeBTC
BULL BitcoinBTC
ZEUSBTC
MetaMaskEVM
RabbyEVM
imTokenEVM
AmbireEVM
SolflareSOL
Helium WalletSOL
TronLinkTRON
TokenPocketEVMWatch only
balances, no signingThese read an address export and follow the balance. Signing still happens in Ownbit.
ElectrumBTC
PhantomSOL
BackpackSOL
JupiterSOLTokenPocketTRON
OKX WalletMULTI
OneKeyMULTI
Trust WalletEVMWallet names are the property of their owners and are listed to describe interoperability, not partnership. Support follows each wallet’s own published QR handling and can change with their releases.
Security design
Why a phone, offline, is the signer
The properties below are what make an ordinary phone usable as a cold signer.
Phrase from the system random source
A new recovery phrase is drawn from the operating system’s cryptographic random source — never a seed the app invents — and turned into words by the standard BIP39 checksum.
Bring your own phrase
Import an existing BIP39 phrase, with or without a BIP39 passphrase. The passphrase is never stored with the phrase.
Offline from end to end
The cold phone stays off Wi-Fi and mobile data. Everything crosses the gap through the camera.
No bespoke chip to trust
The signer is a normal Android phone, so there is no custom secure element or vendor firmware in the trust path.
Every code is readable
Pairing and signing use published formats, and Ownbit’s own QR encoding is published too, so any code can be decoded and checked independently.
Proven against Ownbit itself
Addresses are re-derived and compared before every pairing code. A mismatch shows no code at all.
Get started
Turn a spare phone into the signer for your wallets
Set up the cold wallet, pair it once with the wallet you already use, and keep signing from offline.