An open Nostr + Lightning protocol

A review.
A receipt.
A reason
to trust.

One review per settled payment. Receipt-Bound Review connects what was paid for with what is said about it — on open, verifiable rails.

Protocol in development. No production verification yet.

Fig. 01 / The binding
Concept receipt

The payment
is the starting point.

01 / PaymentSettled
02 / ReviewReceipt-bound
03 / VerificationPublic
One payment. One review.
Illustration / not a live receipt

01 / The principle

From payment
to a public proof.

A payment can anchor a review. It cannot prove that an opinion is fair, or that a seller delivered well.

01 — SETTLEMENT RECEIPT

Start with a settled payment.

A Lightning payment settles. The intended receipt supplies a reference for the review, with the proof format still to be specified.

02 — BOUND REVIEW EVENT

Bind the review to the receipt.

A Nostr review event references that receipt. The protocol aims to accept one review per settled payment, without a central review platform.

03 — PUBLIC VERIFICATION

Make the binding checkable.

Independent clients should be able to check the binding and reject duplicates. Exact evidence, privacy boundaries, and verification rules are being designed.

02 / Open work

Small surface.
Explicit rules.

RBR is an open protocol effort, not a hosted marketplace. This page describes the direction; it is not an implementable specification.

Specification landing under construction.

Specification — forthcoming

The normative specification, test vectors, and compatibility guidance will be published here when ready. No stable version is available yet.

Event kinds — to be defined

Receipt and review event structures, kind numbers, required tags, and signature requirements are pending. No Nostr event kinds are assigned by this landing page.

Verification rules — design in progress

Settlement evidence, payment-to-review binding, duplicate handling, review updates, and privacy considerations need precise rules. The intended invariant is one review per settled payment; enforcement is not implemented here.

03 / Two reference perspectives

See the idea in context.

Separate reference demos explore the same protocol from a developer’s desk and an independent atelier.