▶ Hackathon project
§ Project file

OpenStays

The permanent record for this hackathon project: write-up, links, team, tags, and prizes.
Best use of Wavelength building consensus
An open-source booking engine where availability and self-custodial Bitcoin payments converge on one conflict-proof reservation state, with OpenTimestamps receipts and Wavelength signet rewards.
View code ↗ Live demo ↗ Docs ↗
1 / 4
The write-up

OpenStays: Consensus Commons

Booking systems have a consensus problem.

A guest, property, payment provider, notification service, and booking channel can all report different versions of the same reservation. OpenStays gives them one authoritative booking state: inventory is reserved transactionally, payment is independently reconciled, and only then is the reservation confirmed.

OpenStays is a real open-source booking engine and property-management system for independent accommodations—including cabins, campgrounds, glamping properties, and small resorts. Operators run their own deployment and retain control of their booking and guest data.

The Bitcoin++ contribution

At Bitcoin++ Toronto, we extended OpenStays with Consensus Receipt + Reward:

  1. A guest completes a reservation using the experimental Wavelength signet payment flow.
  2. OpenStays confirms the booking only after the merchant bridge reports authoritative settlement.
  3. The confirmed reservation produces an immutable, privacy-safe Consensus Receipt.
  4. OpenStays commits that receipt through OpenTimestamps.
  5. The guest can download the canonical JSON and .ots proof for independent verification.
  6. Once the proof is submitted, the guest can claim a one-time 1,000 signet-sat reward into a self-custodial Wavelength browser wallet.

The receipt excludes guest identity, email, stay dates, room details, messages, invoices, wallet information, and payment hashes. It proves that the booking system reached a particular state without publishing the guest’s private reservation data.

A newly submitted OpenTimestamps proof is shown honestly as pending Bitcoin confirmation. It becomes Bitcoin anchored only after verification reports a real Bitcoin block attestation. Wavelength payments and rewards use signet test sats; OpenTimestamps’ public calendars ultimately anchor their commitments into Bitcoin mainnet.

Why it matters

Consensus Commons demonstrates how an open booking system can provide:

  • conflict-proof availability and protection against double-booking;
  • authoritative payment reconciliation instead of trusting browser redirects;
  • portable, privacy-safe evidence of the agreed reservation state;
  • self-custodial Bitcoin-native payments and guest rewards;
  • auditable notifications, messages, and manual refund intervention;
  • an optional Channex adapter for future channel distribution—ready, but not connected.

The booking engine, payment foundations, messaging, email, refunds, and channel adapter existed before the hackathon. The immutable OpenTimestamps Consensus Receipt and one-time Wavelength reward are the transparent Bitcoin++ contribution.

One booking. Multiple participants. One authoritative state.