[go: up one dir, main page]

Tezlink/Kernel: Add operations in Tezlink blocks and operations application

Previous MR

!17771 (merged)

What

Introduce operation in Tezlink blocks, and handle the application of an operation

How

Currently in the kernel there's only a notion of operation, or what is stored in a Tezos is what I call in this MR an AppliedOperation it's an operation with its hash and its receipt.

So like for Etherlink, Tezlink will have two collection related to operation in its BlockInProgress, a vector of AppliedOperation and a vector of Operation.

For now in Tezlink, we don't handle the reboot mechanism, but it would be the same approach as the one in Etherlink (store a BlockInProgress if there's a reboot to handle it later)

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 Arnaud Bihan

Merge request reports

Loading