> For the complete documentation index, see [llms.txt](https://circular-protocol.gitbook.io/whitepaper/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://circular-protocol.gitbook.io/whitepaper/circular-protocol-architecture/ticketing-system.md).

# Ticketing System

The Ticketing System (TS) is a supporting component in the Circular Protocol reference architecture that can provide ordering “tickets” for coordinating event sequence. A ticket consists of a UTC timestamp plus an incremental counter that increases each time a ticket is issued (and resets on a daily boundary).

The purpose of TS is to help preserve a consistent sequence of events in parts of the workflow where deterministic ordering is useful, reducing the risk of improper sorting that could lead to inconsistencies. It is intended for non-critical coordination points and is designed so it does not become a throughput bottleneck. A ticket may be requested when a new transaction is created or when a new block is assembled.

As a simple metaphor, the Ticketing System is similar to the number used in stores to preserve service order. Different deployments may implement this function through redundant services or equivalent mechanisms.