§ sign in · sign up

One identity, however you sign in.

Two paths, one identity. Email needs no wallet. A Bitcoin wallet signs natively and keeps its own keys — OrangeCheck only verifies signatures.

After signing in, also link a Bitcoin wallet — optional, one more signature.

§ one cookie, every subdomain

Both paths set oc_session on Domain=.ochk.io. attest, lock, vote, stamp, agent, pledge — every sibling recognizes you immediately. One identity, every surface, no separate password anywhere.

§ what you get

> an OC identity scoped family-wide
> attest tier (anonymous default; upgrade later)
> sats from the sites that wire it in, once the payout rail settles
> graduation to your own keys is not live: no federation is bound yet · /custody
> OrangeCheck holds your accrued sats during bring-up — it is operating every role until independent operators take them. Federation custody and graduation to your own keys are what replace it.

§ what we never see · who signs

> no password — the OTP is the proof, single-use
> bip322 · you sign with your own Bitcoin key. OrangeCheck never sees key material and only verifies signatures
> email · you signed in with email, so you hold no key here. OrangeCheck signs on your behalf
> no kyc, no third-party tracker, no cross-app behavior graph (policy commitment, see /security)