Lightsats

• Name: Lightsats
• URL: https://lightsats.com/
• Category: Lightning gifting app / hosted tip-claim workflow
• Tags: bitcoin-ecosystem
• Summary: Lightsats is a small hosted Lightning gifting app with reclaim-on-expiry logic. That is basically the story. Keep it as a clean specimen of a custodial claim-flow product layered over Lightning, with reminders, expiries, and returns-to-sender baked in.
• What it does:
  • Lets tippers create individual tips or bulk tip groups for recipients via a hosted web app and a first-party API
  • Supports printable Bitcoin gift cards and static/group claim flows for offline or event-based distribution
  • Tracks recipient progress from claim to withdrawal and nudges claimants with reminder messages before expiry
  • Reclaims expired or unclaimed tips back to the sender rather than leaving funds stranded
  • Supports withdrawal-oriented onboarding flows around Lightning invoices, WebLN, Lightning addresses, and LNURL-auth-compatible wallet linking
  • Exposes webhook/API surfaces so tip creation and claim tracking can be automated
• Key claims:
  • The project README describes Lightsats with the core promise “Gift sats without losing them” and directs users to create a tip at lightsats.com
  • The homepage source says that if a tippee does not claim the tip, the sats return to the tipper, highlights a “Progress tracker,” and says onboarding into the recipient’s own wallet is part of the product
  • The API reference says users can “automate the management of Lightsats tips” and documents endpoints for getting tips, creating a tip or tip group, funding tips, deleting tips, and updating tips
  • The scheduler README says the scheduled worker sends reminders to tippees to withdraw their tips, and the scheduler code also processes reclaims for expired tips
  • The app environment example shows Lightsats centered on an LNbits-backed wallet setup and optional Twilio/Short.io/SMS plumbing, which is a strong indicator that this is a hosted operational stack rather than a trust-minimized protocol
  • The reminder logic in the app code explicitly says it only sends reminders for custodial tips “for now,” which further reinforces that Lightsats currently operates as an application/service workflow with backend state and policy decisions
• Whitepaper: No canonical standalone Lightsats whitepaper or litepaper surfaced in this pass. The clearest current sources of truth were the official site, API reference, and public GitHub repo for the app and scheduler; see ../whitepapers/lightsats-primary-sources-2026-05-01.md.
• Sources:
  • https://lightsats.com/
  • https://lightsats.github.io/Lightsats-API-docs/
  • https://github.com/lightsats/lightsats
  • https://github.com/lightsats/lightsats/blob/main/README.md
  • https://github.com/lightsats/lightsats/blob/main/app/pages/index.tsx
  • https://github.com/lightsats/lightsats/blob/main/app/pages/profile.tsx
  • https://github.com/lightsats/lightsats/blob/main/app/.env.example
  • https://github.com/lightsats/lightsats/blob/main/scheduler/README.md
  • https://github.com/lightsats/lightsats/blob/main/scheduler/src/index.ts
  • https://github.com/lightsats/lightsats/blob/main/app/pages/api/reminders.ts

Internal linkages

• Best upward comparison points for hosted Lightning balance and operational-wallet questions: blink and lnbits.

Control surface

• Authority sits in tip creation, custody until withdrawal, reminder timing, expiry policy, reclaim execution, and the LNbits-style backend stack Lightsats operates behind the claim flow.

• Read it as a small hosted distribution app, not as payment infrastructure with much independent gravity.

• Last reviewed: 2026-05-22 UTC