Lunor Tix
Create, sell, and verify event tickets with digital ownership.
Ticketing for events that need a ticket you can sell, transfer, and check at the door — with ownership that survives the screenshot.
- product
- Lunor Tix
- surface
- Tix
- category
- Events
- backend
- Not attached
- status
- Coming Soon
This page describes the intended product. Nothing here accepts a payment, sells a ticket, opens a workspace, sends a campaign, or answers a support conversation.
The problem
The ticket is usually a PDF. The door is usually a guess.
Most event tickets are a file or a QR code that can be copied. The operator finds out at the door, when two people present the same code and neither record says who actually holds it.
Selling, transferring, refunding, and checking in then live in different tools. The person on the door has a list. The person who sold the ticket has another. They meet when something goes wrong.
The approach
One ticket, from the listing to the door.
Lunor Tix is the intended platform for creating an event, selling tickets, and verifying them at entry. Ownership sits on the ticket, so a transfer is a transfer and a copy is not a second admission.
Where a project already runs Lunor rewards, ticket activity can connect to that record. This site sells no tickets and checks no doors. The states below are the product being specified, not a box office.
Capabilities
What the module does.
Event setup
Name, date, venue, capacity, and ticket types before a single ticket is sold.
Ticket types
Price, quantity, and what the holder is actually admitted to.
Digital ownership
The holder of the ticket is the record, not whoever has a copy of the image.
Transfer
A ticket can move to someone else without becoming a second valid ticket.
Door check
Entry verifies the ticket and marks it used.
Operator view
Sold, remaining, checked in, and still outstanding, on one event.
Rewards link
Ticket activity can connect to Lunor rewards when the project runs them.
Not live
No event, no sale, and no scanner on this site.
How it works
The workflow, step by step.
- 01Create the event
Capacity, schedule, and the ticket types on sale.
- 02Sell
Each sale issues one ticket to one holder.
- 03Transfer, if you allow it
The ticket moves. The previous copy stops being valid.
- 04Check the door
Verify the ticket and record the entry.
- 05Close the event
Attendance and remaining inventory stay on the event record.
Specification
At a glance.
- Unit
- One ticket, one holder
- Event record
- Capacity, types, sales, check-ins
- Entry
- Verify, then mark used
- Rewards
- Optional link to a Lunor rewards record
- Sales
- None from this site
- Status
- Coming soon — no published date
Security
A copied ticket should fail at the door. This page does not pretend to be the door.
- No tickets are issued, sold, or scanned from this site
- The intended product treats ownership as the admission record, not a forwarded image
- A used ticket stays used
- No wallet connection and no payment path on the public page
- Production ticket custody, if built, is a separate operation from this marketing site
Full posture, including what we deliberately do not claim, is on the security page.
Use cases
Where it gets used.
A single event
Sell a fixed capacity and know who is admitted before doors open.
A tour or a series
The same ticket types and door check across more than one date.
Holder utility
Connect attendance to rewards for a project that already runs them.
FAQ
Questions asked before adopting this module.
Can I buy a ticket here?
No. Lunor Tix is coming soon. This page describes the product. It does not list events, take payment, or issue tickets.
What does digital ownership change at the door?
The valid ticket is the one the record says is held, and a check-in marks it used. A forwarded image is not a second admission. That is the intended behavior, not something this site performs.
How do Lunor rewards fit?
If the operator already runs rewards on Lunor, ticket activity can be connected to that record. Rewards are not issued from this page, and nothing here promises a payout.
When does it ship?
No date is published. It moves up when a real event needs it and the operator is willing to be first.
Other modules
Same Console, same project record.
Next step
Tell us if you need this one.
Modules move up the sequence when a real project needs them. If this is the one blocking you, that is useful information.