Bitcoin-native social infrastructure

OnlySats OnlyOrange

Dating, creator content, paid messaging, and reputation with sats as the signal. No KYC. No fiat. No platform account.

Identity Nostr npub login
Money Lightning and Cashu
Media Encrypted Blossom storage
Trust Reputation from verified interactions

The Wedge

Dating with Bitcoin escrow, paid intent, and less noise.

OnlySats starts where social apps are weakest: first contact, commitment, and trust. Sats make interaction expensive enough to kill spam, but small enough to keep the experience fluid.

01

Paid First Message

A first contact carries a sats signal and an encrypted message, so attention has value from the first tap.

02

Date Proposal

Two people agree on time, place, and minimum commitment before the date moves into confirmed state.

03

Escrow Reputation

Both sides confirm completion, simulated escrow resolves, and reputation updates without exposing sensitive details.

2,100 sats intent

Signal over spam.

Nostr identity, sats-denominated contact, and local-first discovery for the prototype.

npub verified

Protocol Stack

Client first. Protocol owned. Platform optional.

The POC stays honest: mock payments first, real protocol edges next, no fake custody promises, no central account theater.

N

Nostr for identity and signed events

Login, profile data, encrypted messages, and portable reputation can move with the user.

Lightning and Cashu for payment flows

The MVP starts with fake invoices and local escrow state, then grows into proofs and settlement.

B

Blossom-style encrypted media

Creator content and dating media should be encrypted when needed and not trapped inside one vendor.

MVP Target

One polished prototype loop before the protocol plumbing gets expensive.

Login, profile, discovery, paid message mock, date proposal, escrow mock, and a reputation badge. Enough to prove the product spine before we start wiring the dangerous grown-up stuff.

Surface

PWA shell and Nostr login

A fast web client with NIP-07 support and a dev key path for prototype speed.

Interaction

Discovery, like/pass, paid message

Local-first fake profiles make the user journey testable before relay complexity lands.

Trust

Date escrow and reputation event log

Every meaningful step should be visible in a debug log so the concept can be audited while it evolves.