Skip to content

For apps · Free sign-in · No IDs

Sign-in that keeps bots out.

Let in only accounts backed by bitcoin, without collecting IDs. Signing people in is free.

The problem

For apps

A bot farm can pretend to be a crowd for almost nothing.

The usual fixes ask your real users for more:

  • a phone number
  • a puzzle
  • an ID

You can ask for

An account with bitcoin behind it.

Keeps bots outNo IDsFree sign-inPays your users once payouts are live

How it works

Ask for something a bot can’t fake cheaply.

Three steps. Your users sign in the way they already do; you decide who gets in.

  1. 01

    People sign in as usual

    Email, Google, GitHub or a wallet. Anyone can back their account with bitcoin they hold.

  2. 02

    You set the bar

    In your project’s settings: at least so many sats, held so many days. Your server lets in the accounts that clear it.

  3. 03

    You never see the coin

    No sats change hands. The coin stays in its owner’s wallet. You see the account’s orangecheck id and a rough amount and age for the coin, like “at least 100,000 sats, held 30 days”, never the coin itself, and you can block it.

Set your bar
Backed by at least100,000 sats
Held for at least30 days
An account with bitcoin behind it

A coin of at least 250,000 sats, held 180 days or more, already in their wallet. Signing spends nothing.

Gets in
A bot farm · 1,000 accounts
1BTCheld 30 days or more
Too costly
Backed accounts pass. A thousand fresh ones don’t.

A thousand fake accounts means a thousand coins, each holding your floor and left unspent for as long as your bar asks. Honest users only wait. A blocked coin stays blocked until it moves, and moving it starts its age again.

What it does

Your sign-in provider doesn’t pay your users. This one can.

Keeps bots out
Backed by one coin of at least the sats you ask, held as long as you ask
Pays your users
When you choose, in bitcoin. Paid once payouts are live.
What you pay for
Only the events you pay your users for. Signing people in is free.
Builds a graph of your users
No, and we sell none. Policy today, not cryptography
Records that outlive the provider
Yes. Anchored receipts check against Bitcoin, without us.
An open spec you can run
Yes, in full

What you get

Open packages for the stack you already run.

01 · @orangecheck/me-client

Sign-in that keeps bots out

A sign-in button, and session checks for Next.js, Express and Hono that hold accounts to your bar.

Shell
yarn add @orangecheck/me-client
@orangecheck/me-client in Next.js. Express and Hono have their own.
import { withOcAuth } from '@orangecheck/me-client/server';

// Lets in accounts backed by a coin that clears the bar
// set in your project's settings. Everyone else gets a 403.
export default withOcAuth(postHandler, {
  audience: 'https://yourapp.example',
  projectKey: process.env.OC_PROJECT_KEY!,
});
02 · @orangecheck/me-client

Pay your users, when you choose

Report the events you value. Always or in promos, your users get paid and you get a receipt. Payouts are in testing, so no sats move yet.

  • Off, always, or in promos.
  • Your users get about 80%
  • A receipt for every event

The specs and the TypeScript SDK are open, under MIT, and the HTTP API works from any language. The hosted services' code is private. github.com/orangecheck. Other tools, from a drop-in gate to a Nostr relay filter, are in the docs.

What it costs

Signing people in is free. Paying your users is up to you.

Turn paying on, run a promo, or leave it off. When you pay, you say what each event earns your user: if they earn 100 sats, you pay 125, the 20% fee included.

See pricing
Of what you pay
80%
20%
80%
Your user earns about this
20%
Platform fee

A sat is a tiny piece of bitcoin: one hundred-millionth of one.