Skip to content

Optimistic transactional rollup: feature flag & origination

Sylvain R. requested to merge tx_rollup@creation into master

Context

This MR is the first of a series to introduce optimistic transactional rollups into tezos. The merge process is described here.

This first MR set a feature flag tx_rollup_enable that is checked for each rollup operation and prevents its application. When all the transactional rollup MR are merged this flag can be entirely removed from the codebase until then it must only be set to true in tests when activating the protocol with genesis as a predecessor. The migration process set it to false by default.

It also adds the first operation for the transactional rollups: tx_rollup_origination. The initiated storage is set to unit for the moment until the next MR because the correct types have not yet been introduced.

This tx_rollup_origination operation burns currently 15 tez, the maximum an operation is allowed to burn in storage. this value should be change to a more adequate value later when we have an implementation of the actual storage a tx rollup is going to use. See #2152 (closed)

smart contract rollup first MR : !3941 (merged)

next MR2 on tx rollup: !3921 (closed)

depends on: !3928 (merged)

Manually testing the MR

  • Change the default value tx_rollup_enable in proto_alpha/parameters/sandbox-parameters.json to true
  • Runs a sanboxed tezos node and create a new tx rollup with the following command :
tezos-client --wait none originate tx rollup from <source> --storage-limit 60_000

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, the Development Version section of CHANGES.md 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 Sylvain R.

Merge request reports