# Ticket updates in receipts

**URL:** https://forum.tezosagora.org/t/ticket-updates-in-receipts/4786
**Category:** Research and Development
**Created:** [October 14, 2022, 1:58pm UTC](https://forum.tezosagora.org/t/ticket-updates-in-receipts/4786 "2022-10-14T13:58:43Z")
**Posts on this page:** 1
**Page:** 1

<div class="post-metadata">

### Author: ![Marigold](https://forum.tezosagora.org/user_avatar/forum.tezosagora.org/marigold/32/1009_2.png) [@Marigold](https://forum.tezosagora.org/u/Marigold)
#### Post date: [October 14, 2022, 1:58pm UTC](https://forum.tezosagora.org/t/ticket-updates-in-receipts/4786/1 "2022-10-14T13:58:43Z")

</div>

By [Lin Oshitani](https://www.marigold.dev/team#protocol)

## Introduction

After the [Lima protocol update](https://research-development.nomadic-labs.com/lima-preview.html#improvements-to-tickets), you will notice a new `Ticket updates` field is added to the transaction receipt.

```auto
// ... fields omitted for clarity
Balance updates:
    KT1LPnsqkZnddGUWZWFE5GtGBFtq6bT6EB7Q ... -ꜩ0.027
    storage fees ........................... +ꜩ0.027
Ticket updates:
    Ticketer: KT1WuPpnvefGFqKMDHWHEXz7FpnTc5JfYCB7
    Content type: string
    Content: "blue"
    Account updates:
        KT1LPnsqkZnddGUWZWFE5GtGBFtq6bT6EB7Q ... +3
// ... fields omitted for clarity

```

In this post, we will go over what it means and why it is important for the future of Tezos.

## What are tickets?

First, a quick recap on tickets.

Tickets are first-class tokens in Tezos. Contracts can mint tickets, store tickets, and transfer tickets to other contracts. Every ticket is classified by the following three elements:

- **Ticketer** :
  - The address of the contract that minted this ticket.

- **Content type** :
  - The type of the ticket’s content.

- **Content** :
  - An arbitrary value set when the ticket was minted.

For example, a ticket minted by `KT1Wu...` with a content type `string` and content `"blue"` can be classified by:

```auto
Ticketer: KT1WuPpnvefGFqKMDHWHEXz7FpnTc5JfYCB7
Content type: string
Content: "blue"

```

You can read more about tickets in [this blog post](https://www.marigold.dev/post/tickets-for-dummies).

## Why tickets matter

Two upcoming changes will increase the importance of tickets:

- Layer 2 solutions.
- Direct ticket ownership by implicit accounts.

### Layer 2 solutions

Tezos rollups ([TORU/SCORU](https://research-development.nomadic-labs.com/next-generation-rollups.html)) and sidechains ([Deku](https://www.marigold.dev/deku)) utilize tickets to transfer assets between layer 1 and layer 2. By using tickets, Tezos layer 2 solutions can bridge not only tez (by wrapping them in [ctez](https://ctez.app/faq), etc.) but also arbitrary fungible/non-fungible tokens.

If you want to learn more about this new ticket update field, please read our blogpost on Marigold website 👉 [Ticket updates in receipts](https://www.marigold.dev/post/ticket-updates-in-receipts)