Tezos Stack Exchange is a question and answer site for users, experts, and developers of the Tezos blockchain project. It only takes a minute to sign up.
Sign up to join this community
The Michelson documentation for the Edo protocol mentions four new operations for tickets and this blog post has an example of how tickets are used. I see that the contract in that example can take a ticket type as a parameter, but I am still confused as to how tickets are actually passed into the contract.
When a ticket is created, is there a unique identifier that is created and the contract caller has to pass that in manually? Or what is the exact process?
Internally, tickets are represented as triples (the address of ticketer, the wrapped piece of data, and the amount) but Michelson type system guarantees that tickets can only be produced by smart contracts. The instruction to create a ticket is TICKET.
TRANSFER_TOKENS operation would not be involved. Now it seems like tickets mostly live in the contracts. With an implicit account or contract it exposes an address that can be passed off chain and on chain, whereas with tickets it seems to be just on chain in the contracts, you wouldn't be passing a ticket id off and on chain).