By Lin Oshitani
After the Lima protocol update, you will notice a new
Ticket updates field is added to the transaction receipt.
// ... 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.
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:
- The address of the contract that minted this ticket.
- The type of the ticket’s 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:
Ticketer: KT1WuPpnvefGFqKMDHWHEXz7FpnTc5JfYCB7 Content type: string Content: "blue"
You can read more about tickets in this blog post.
Two upcoming changes will increase the importance of tickets:
- Layer 2 solutions.
- Direct ticket ownership by implicit accounts.
Tezos rollups (TORU/SCORU) and sidechains (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, 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