No description
  • Python 60.3%
  • Vue 23.8%
  • JavaScript 15.4%
  • Makefile 0.5%
Find a file
Padreug 7b761a1aef
Some checks failed
lint.yml / fix: every ticket row gets a fresh short-hash id (no payment_hash reuse) (pull_request) Failing after 0s
lint.yml / fix: every ticket row gets a fresh short-hash id (no payment_hash reuse) (push) Failing after 0s
fix: every ticket row gets a fresh short-hash id (no payment_hash reuse)
Previous commit reused the LNbits invoice payment_hash as the
first row's id, so a 3-ticket purchase ended up with one 64-hex
id and two short-hash ids — inconsistent and noisy in My Tickets.

Switch every row to urlsafe_short_hash. The shared payment_hash
column is the join key for invoice lookups (poll endpoint, ws
notifier, on_invoice_paid); rows never need to BE the payment
hash, they only need to point at it.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
2026-05-23 22:57:00 +02:00
.github/workflows Update to use uv (#37) 2025-08-22 16:54:51 +02:00
nostr chore: rebase onto upstream v1.6.1 + bump to v1.6.1-aio.1 2026-05-22 09:24:35 +02:00
static feat: organizer-side "Republish mine" button + scoped endpoint 2026-05-23 21:02:36 +02:00
tests feat: code quality (#34) 2024-08-29 12:18:49 +02:00
.gitignore feat: code quality (#34) 2024-08-29 12:18:49 +02:00
.prettierrc feat: code quality (#34) 2024-08-29 12:18:49 +02:00
__init__.py chore: rebase onto upstream v1.6.1 + bump to v1.6.1-aio.1 2026-05-22 09:24:35 +02:00
config.json chore: rebase onto upstream v1.6.1 + bump to v1.6.1-aio.1 2026-05-22 09:24:35 +02:00
crud.py feat: multi-ticket purchases as N rows sharing one payment_hash 2026-05-23 22:57:00 +02:00
description.md docs: changes to more pages (#42) 2026-01-28 17:22:09 +01:00
LICENSE add license 2023-02-24 18:13:39 +01:00
Makefile Update to use uv (#37) 2025-08-22 16:54:51 +02:00
manifest.json [FEAT] add timestamp on register (#15) 2023-08-18 08:17:29 +02:00
migrations.py fix: if sats and fiat checkout conversion currency 2026-05-07 14:34:22 +01:00
migrations_fork.py feat: multi-ticket purchases as N rows sharing one payment_hash 2026-05-23 22:57:00 +02:00
models.py feat: multi-ticket purchases as N rows sharing one payment_hash 2026-05-23 22:57:00 +02:00
nostr_hooks.py feat: add NIP-52 Nostr publish + sync of calendar events 2026-05-22 09:20:00 +02:00
nostr_publisher.py feat: also publish allow_fiat + fiat_currency in NIP-52 tags 2026-05-23 20:37:19 +02:00
nostr_sync.py chore: rebase onto upstream v1.6.1 + bump to v1.6.1-aio.1 2026-05-22 09:24:35 +02:00
package-lock.json feat: code quality (#34) 2024-08-29 12:18:49 +02:00
package.json feat: code quality (#34) 2024-08-29 12:18:49 +02:00
pyproject.toml chore: prepare release, fix lint and uv warnings (#44) 2026-04-15 17:37:34 +02:00
README.md docs: changes to more pages (#42) 2026-01-28 17:22:09 +01:00
services.py feat: publish ticket counts in NIP-52 tags + republish on sale 2026-05-23 20:31:56 +02:00
tasks.py feat: multi-ticket purchases as N rows sharing one payment_hash 2026-05-23 22:57:00 +02:00
toc.md feat: code quality (#34) 2024-08-29 12:18:49 +02:00
uv.lock chore: prepare release, fix lint and uv warnings (#44) 2026-04-15 17:37:34 +02:00
views.py feat: make events dynamic (#43) 2026-05-04 17:01:53 +02:00
views_api.py fix: every ticket row gets a fresh short-hash id (no payment_hash reuse) 2026-05-23 22:57:00 +02:00

LNbits

License: MIT Built for LNbits

Events - LNbits extension

For more about LNBits extension check this tutorial

Sell tickets for events and use the built-in scanner for registering attendees

Events allows you to create tickets for an event. Each ticket is in the form of a unique QR code. After registering and paying, the user gets a QR code to present at registration/entrance.

Events includes a shareable ticket scanner, which can be used to register attendees.

Usage

  1. Create an event
    create event

  2. Fill out the event information:

    • event name
    • wallet (normally there's only one)
    • event information
    • closing date for event registration
    • begin and end date of the event

    event info

  3. Share the event registration link
    event ticket

    • ticket example
      ticket example

    • QR code ticket, presented after invoice paid, to present at registration
      event ticket

  4. Use the built-in ticket scanner to validate registered, and paid, attendees
    ticket scanner

Powered by LNbits

LNbits is a free and open-source lightning accounts system.

Visit LNbits Shop Try myLNbits SaaS