aiolabs/events
8
0
Fork 0
Code Issues 19 Pull requests Projects Releases 2 Packages Wiki Activity Actions

Replace user_id with nostr pubkey for ticket identification #3

New issue
Open
opened 2026-04-24 06:58:16 +00:00 by padreug · 0 comments
padreug commented 2026-04-24 06:58:16 +00:00
Owner
Copy link

Currently tickets can be created with a user_id (LNbits internal user ID) as an alternative to name/email. This works but ties ticket identity to LNbits internals.

Proposal: Use a nostr pubkey instead of user_id. This would:

  • Decouple ticket identity from LNbits user management
  • Allow ticket lookup across instances (pubkey is portable)
  • Align with the nostr-native architecture used by the webapp
  • Enable future features like nostr-based ticket transfer

Changes needed:

  • Rename user_id column/field to nostr_pubkey (or add alongside)
  • Update CreateTicket validator
  • Update get_tickets_by_user_id → get_tickets_by_pubkey
  • Update API endpoints
  • Migration to rename/add column

Considerations:

  • Backward compatibility with existing user_id tickets
  • Whether to keep user_id as a fallback or drop entirely
Currently tickets can be created with a `user_id` (LNbits internal user ID) as an alternative to name/email. This works but ties ticket identity to LNbits internals. **Proposal:** Use a nostr pubkey instead of `user_id`. This would: - Decouple ticket identity from LNbits user management - Allow ticket lookup across instances (pubkey is portable) - Align with the nostr-native architecture used by the webapp - Enable future features like nostr-based ticket transfer **Changes needed:** - Rename `user_id` column/field to `nostr_pubkey` (or add alongside) - Update `CreateTicket` validator - Update `get_tickets_by_user_id` → `get_tickets_by_pubkey` - Update API endpoints - Migration to rename/add column **Considerations:** - Backward compatibility with existing `user_id` tickets - Whether to keep `user_id` as a fallback or drop entirely
Sign in to join this conversation.
No Branch/Tag specified
Branches Tags
main
ticket-scanner-nostr
backup/main-pre-v1.3-rebase-2026-05-05
feat/event-approval-workflow
fix/sqlite-ticket-extra-serialization
v1.6.1-aio.6
v1.6.1-aio.5
v1.6.1-aio.3
v1.6.1-aio.2
v1.6.1-aio.1
v1.3.0-aio.6
v1.3.0-aio.5
v1.3.0-aio.4
v1.3.0-aio.3
v1.3.0-aio.2
v1.3.0-aio.1
v1.2.1-aio.2
v1.2.1-aio.1
v1.2.1
v0.0.2
v0.0.1
v1.2.0
v1.1.0
v1.0.0
v0.2.0
v0.1.6
v0.1.5
v0.1.4
v0.1.3
0.1.2
0.1.1
0.1
Labels
Clear labels
No items
No labels
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
aiolabs/events#3
No description provided.