Definition and scope
TicketSoft is a fiat-first ticketing product. Fans buy tickets through familiar checkout flows. TicketSoft records ticket issuance on Base, an Ethereum layer-2 network. This page explains what that record is and what it does and does not prove.
The purchase
A fan chooses an event and pays the way they usually pay. The fan does not need a wallet, a token or any understanding of blockchains to buy or use a ticket. The blockchain work happens behind the ticketing experience.
The record
When a ticket is issued, TicketSoft creates a ticket token on Base through its production contracts. That mint is the ticket’s onchain record. It can be inspected by anyone with the transaction hash, without contacting TicketSoft.
What a mint demonstrates:
- A ticket token was created by a qualifying production contract at a known block and time.
- The network fee that the mint cost, which the reporting system allocates per ticket.
What a mint does not demonstrate on its own:
- That the ticket was paid for, refunded or used. Paid sales need reconciliation with payment records.
- Who the fan is, where they sat or whether they attended. Public reporting keeps those out of scope.
Events on Base
Organisers’ events are registered onchain through the reviewed registry or factory contracts. The dashboard counts unique qualifying registrations as events created onchain. Third-party discovery listings that TicketSoft may aggregate elsewhere are a different inventory and are not counted.
Reporting
The reporting system follows the reviewed TicketSoft contracts and records their activity as aggregate metrics, daily charts and a transaction feed. Every figure carries its source classification, period, coverage and update time. See How we report activity for the definitions and Contracts and sources for the registry.