Built by the BITBILL team
Ownbit's core developers come from BITBILL, one of the early Bitcoin wallet teams, building since 2013. More than a decade of shipping wallets brings deep industry insight and a long memory for how wallets fail.
Trust center
Trust, earned since 2017.
Ownbit has protected self-custody wallets through every market cycle since 2017 without a single security incident. Here is the record, the code and the exit plan behind that trust.
2017Operating since
0Security incidents
2013Team building wallets since
20Chains supported
Track record
Every market cycle since 2017. Zero security incidents.
Since Ownbit launched in 2017 it has never had a security incident, through bull runs, crashes, exchange collapses and wave after wave of wallet exploits elsewhere. Many users have stayed with us for years and recommend Ownbit to each other. That loyal community is the best evidence we can offer.
- 2013
The BITBILL team starts building Bitcoin wallets.
- 2017
Ownbit launches as a self-custody wallet.
- 2018
The MultiSig smart-contract source goes public on GitHub.
- 2026
Ownbit 5: the iOS key-handling core is open-sourced, Ownbit Vault v2 encryption ships, and the MultiSig contracts get two AI security reviews.
Self-custody by design
Ownbit never holds your keys or your funds. There is no custodial account to freeze, hack or take down with a bankruptcy: your keys stay encrypted on your own devices.
A community that stays
From individual holders to families and treasury teams, people have trusted Ownbit with their savings for years, and keep bringing their friends.
Open source
The code that touches your keys is public.
From version 5.0, the code that handles your secrets in the iOS app (mnemonic generation, key storage, key derivation and transaction signing), together with the JavaScript signing bundles both apps load, is open source under the MIT license. Anyone can read it, build and test it, and compare the published bundle hashes with the ones in the app. The Android core is to follow.
The open-source core is exactly the part that handles secrets. The interface and the code that talks to Ownbit's servers are kept outside it.
bitbill / ownbit-app-50MIT license · iOS Swift package · JavaScript signing bundles
- Mnemonic generation
BIP39 phrases of 12 or 24 words, generated from the operating system's secure random generator.
- Key storage: Ownbit Vault v2
scrypt and AES-256-GCM, bound to your device. Secrets are never stored in plain text.
- Key derivation and signing
Keys are derived and transactions are signed on your device, by JavaScript bundles whose SHA-256 hashes are published.
- Cold-wallet public protocol
Signing requests from other wallets are parsed and verified before anything is signed.
Smart contracts
bitbill / ownbit-multisig-contractsSolidity (EVM) · Rust / Anchor (Solana)
MultiSig contracts: public source, reviewed by two AI models.
Ownbit's MultiSig smart contracts have been public on GitHub since 2018. In October 2026 the current versions (Standard V10, Accident Protection V11, Enterprise V21 and the Solana program) went through two AI security reviews, by GPT-6-Astra and by Opus 5.
GPT-6-AstraOWNBIT-SCA-2026-1026
MultiSig Security Audit
No confirmed way to spend below the signing threshold was found.
- 0Critical
- 0High
- 1Medium
- 2Low
- 5Informational
Commit 1f8c784 · 6 source files · 1,395 linesRead the full report (PDF)
Opus 5OMS · 16
MultiSig Contracts Security Assessment
Core signature logic is sound. No finding lets an outsider who holds no key move funds.
- 0Critical
- 3Major
- 4Medium
- 4Minor
- 5Informational
Commit 1f8c784 · 6 source files · 1,395 linesRead the full report (PDF)
What the reviewers confirmed
- On every EVM contract, each spending signature is bound to the wallet address, its nonce and the chain ID.
- EVM proxies are immutable, with no admin key and no upgrade path.
- dApp signatures made through Ownbit use a separate signing domain, so they cannot be reused as spending approvals.
- Key findings were reproduced with executable proof-of-concept tests, not just read.
These are AI-assisted security reviews, not certifications by a third-party audit firm. We publish both reports in full, open findings included, so you can judge for yourself.
No lock-in
If Ownbit disappeared tomorrow, your assets would not.
Self-custody means you never need us to reach your money. Ownbit is built on open standards and public contracts, so you can always recover on your own, without depending on our servers.
Personal wallets
Ownbit wallets are standard BIP39 / BIP32 / BIP44 wallets. Import the same recovery phrase into a compatible wallet and, in almost every case, the same addresses and balances appear; the guide covers the few exceptions.
Restores in wallets such as
BitTool Wallet
TokenPocket
imToken
MetaMask
Trust Wallet
Solflare
TronLink
and most other mainstream wallets
MultiSig wallets
MultiSig funds do not depend on Ownbit's servers either. With the signers' keys and the MultiSig Recovery Tool built into the app, which works fully offline, you can move them yourself at any time, even if Ownbit's servers were gone for good.
Go deeper
Don't trust. Verify.
The Ownbit security model
The Ownbit cold wallet is a permanently offline signing device: your private key lives only on this non-networked phone, and its only channel to the outside world is a human-readable QR code.
How Ownbit encrypts your seed
How Ownbit Vault v2 encrypts your seed, compared with the original v1.
Threat model
An honest threat model states what a design removes and what it does not.
Audits and code
Here is our audit stance, stated plainly.
Verify it yourself
You don't have to believe us.
Security FAQ
Straight answers to the security questions we're asked most.
Self-custody you can verify.
Download Ownbit, then read the code that protects your keys.