Today we would like to announce an important change coming in your way. As part of our next protocol proposal, we will remove support for tickets of zero amount.
Tickets of zero amount was previously allowed at the introduction of tickets initially. However, as Tezos protocol developers work on transaction and smart contract rollups, tickets of this kind has become the source of inconvenience and potential security issues. To simplify and provide more safeguards to the ticket system, a more systematic accounting method for tickets is being introduced and, along with it, tickets of zero amount will be phased out of support.
Tickets of zero amount will be rejected while there are safeguards and assertions in several places. They will not be accepted as a valid value of any given ticket type, when parsing a Micheline node into a Michelson value. They will not be able to get instantiated using
SPLIT_TICKET instructions. Therefore, during execution of smart contracts, those instructions will return
NONE when tickets of zero amount may be created.
This will potentially impact the existing originated contract on the Tezos blockchain. However, after gathering recent Tezos mainnet data, we come to a conclusion that there is a rather low risk in carrying out this migration. Here is how.
We try to identify contracts that has recently created, stored or read tickets of zero amount. Specifically, we fixed a date, 10th of August, 2022, and replay those Tezos mainnet blocks baked after the level
2608372. First, we took the snapshot and imported it into a
If you want to learn more about this Tezos bridge, please read our blogpost on Marigold website Remove support for tickets with zero amount