OC Chat

Built by OrangeCheck on its own OC Lock confidentiality crypto, the family BIP-322 identity, and Lightning settlement. Ships on the shared @orangecheck/* SDKs (lock-core, lock-device, lock-crypto, nostr-core, wallet-adapter) and the family design system.

Live at chat.ochk.io (M2): an auth-wired, design-wired site plus a gated /app. Your Bitcoin address is your inbox, resolved from your session — never a typed-in address. Two honestly-weighted identity tiers are built: a BIP-322 bitcoin-address tier (sovereign, offline-verifiable, shown as a 'verified' shield) and a did:oc session on-ramp (a named trust anchor, shown as 'via ochk.io', with a graduation nudge to go sovereign). Three canonical send modes are specified and building: speak-now (free 1:1 E2EE to any Bitcoin address), pay-to-reach (a stranger attaches Lightning postage — a real preimage paid to you, not OC, verified offline), and seal-til-block (a content key released only after the Bitcoin chain passes block N, beacon-enforced — we don't call it trustless). Nostr kinds 30110-30112 + 30114 (directory) are allocated; transport is NIP-59 gift-wrap. We're honest about v0: per-message forward secrecy waits for the double-ratchet, and every trust anchor is named.

A protocol-minded engineer to build the messaging surface — real threads, compose, the three send modes, and the double-ratchet — plus capital for relay infrastructure and reliability hardening. The crypto and identity model are done; the product surface needs a builder.

A full-time messaging-UI + double-ratchet engineer (largest line). Relay infrastructure (the family strfry on Fly). Device-key revocation + reliability hardening. A security review of the seal-til-block beacon path.

Patronage, not equity. Backing endorses a Bitcoin-native, no-KYC messenger and buys a sweat-equity conversation off-platform — never shares, tokens, or a return. Lightning postage settles to recipients, not OC; OC custodies nothing.