where the docs live.
OC Vault docs are split intentionally: this site hosts the product landing, the unified docs site hosts the SDK and integration reference, and the protocol repository hosts the normative spec. Three surfaces, one family.
docs.ochk.io/vault ↗
Reference: quickstart, integration guide, API surface for @orangecheck/lock-core / lock-device / lock-crypto, recipes (TOTP migration, API-key rotation, team-shared vaults), and the security model. This is where developers go.
oc-lock-protocol ↗
Normative protocol spec. SPEC.md, PROTOCOL.md, WHY.md, SECURITY.md, plus test vectors. OC Vault is the consumer-facing productization of Flow 4 (self-vault). The protocol governs the .lock envelope format and the BIP-322 binding.
lock.ochk.io ↗
Reference web client for the broader OC Lock protocol (Flows 1–3: device-to-device, group-to-device, time-locked). If you want to send a secret to someone else, that's the Lock client. OC Vault is specifically the self-vault productization.
quick orientation
- who is oc vault for?
- Bitcoin-native devs and professionals who already manage a Bitcoin wallet and don't want to add a separate SaaS account just to store passwords, TOTP codes, API keys, and recovery codes. Broader audience welcome. It is not a place for your seed (seeds belong on metal, offline).
- what's the trust model?
- OC holds ciphertext only. Your entries open with your vault passphrase, or your recovery code, and neither ever reaches us. Your sign-in only fetches the ciphertext.
- is this the same as a hardware wallet?
- No. Your wallet protects your sats and can be your sign-in. It does not decrypt your vault; your passphrase does.
- can I self-host?
- Not the sync service yet. You can skip the cloud entirely: the free tier keeps everything in your browser, and an encrypted backup file restores anywhere. Cloud sync on vault.ochk.io is the paid convenience.