> For the complete documentation index, see [llms.txt](https://docs.altlayer.io/altlayer-documentation/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.altlayer.io/altlayer-documentation/rollup-types/flash-layer-rollups/example-use-cases/event-ticketing.md).

# Event Ticketing

The issues with the global ticketing industry are well-documented at this point. Bot-based tech has us fighting due to dynamic pricing, and getting into a mode of panic buying. Then there’s hidden fees, queues and scams, scalping, counterfeiting, pricing wars in the resale market and more. It’s all wildly unfair and unethical.&#x20;

NFT-based ticketing has been making the rounds as a viable alternative. NFT ticketing could provide a more flexible and customizable ticketing experience for fans. For example, event organizers could create special NFT tickets for VIP experiences or exclusive events, or allow fans to purchase collectible NFT tickets that could increase in value over time. Not to mention, there could be transparency around the number of tickets available and their pricing - without the interference of systems generated to trick consumers. With the provenance that comes from NFTs, ticketing fraud could be eliminated and more data would be collected on the nature  of, and appetite around secondary sales.&#x20;

But if implemented on a vast scale for major global events -  how can the underlying chain support the millions of users who make transactions on the network at the same time? After all, the NFT world is no stranger to congestion issues, network downtime and gas wars.&#x20;

An app-specific scaling solution could help in such cases. But having an entire chain built just for an event is just not feasible! Following the event there will be no on-chain activity, making it a wasted resource. In such cases, a flash layer’s event-driven model could do wonders. One can spin up an on-demand layer for the duration of the event, use it to issue tickets and then once it is sold, the layer gets disposed of and the NFTs live on the underlying chain.&#x20;

A flash layer refers to a disposable off-chain network that facilitates transactions by providing a boost in transaction speed and scalability. It operates in sync with the underlying blockchain. Flash layers are particularly useful when a developer expects an increased demand for a dApp. With a quick-to-deploy flash layer, they could integrate a rollup as per their needs to avoid congestion across the Layer1, and subsequently when a campaign ends or when demand tapers, they are free to easily dispose of the rollup via an “end-of-life” settlement on the Layer1.&#x20;


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.altlayer.io/altlayer-documentation/rollup-types/flash-layer-rollups/example-use-cases/event-ticketing.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
