Skip to content

Proto: Add ticket receipt to implicit->implicit/originated

Context

Adds a new ticket_updates field to the transaction receipt of implicit->implicit/originated (= Transfer_ticket manager operation).

Closes #4179 (closed)

Expected behavior

implicit->implicit

tz_a -(one ticket)-> tz_b

The ticket ownership is removed from tz_a and added to tz_b.

Manager signed operations:
    ...
    Transfer Ticket:
      From: tz_a
      ...
      Ticket updates: 
          Ticketer: KT_T
          Content: "blue"
          Content type: string
          Account updates:
              tz_a ... -1
              tz_b ... +1

implicit->contract

tz_a -(one ticket)-> KT_A
                    (stores ticket in storage)

A ticket is removed from tz_a and added to the storage of KT_A via subsequent internal operation:

Manager signed operations:
    ...
    Transfer Ticket:
      From: tz_a
      ...

      Ticket updates: 
          Ticketer: KT_T
          Content: "blue"
          Content type: string
          Account updates:
              tz_a ... -1
    Internal Transaction:
        ...
        From: tz_a
        To: KT_A
        Parameter: (Pair T (Pair "blue" 1))
        ...
        Ticket updates: 
            Ticketer: KT_T
            Content: "blue"
            Content type: string
            Account updates:
               KT_A ... +1

Manually testing the MR

Checklist

  • Document the interface of any function added or modified (see the coding guidelines)
  • Document any change to the user interface, including configuration parameters (see node configuration)
  • Provide automatic testing (see the testing guide).
  • For new features and bug fixes, add an item in the appropriate changelog (docs/protocols/alpha.rst for the protocol and the environment, CHANGES.rst at the root of the repository for everything else).
  • Select suitable reviewers using the Reviewers field below.
  • Select as Assignee the next person who should take action on that MR
Edited by Lin Oshitani

Merge request reports