package tezos-protocol-016-PtMumbai
Install
Dune Dependency
Authors
Maintainers
Sources
sha256=7062cd57addd452852598a2214ade393130efa087b99068d53713bdf912b3680
sha512=08e4091144a03ce3c107fb91a66501bd8b65ca3278917c455a2eaac6df3e108ade63f6ab8340a4bb152d60f404326e464d0ec95d26cafe8e82f870465d24a5fc
doc/tezos-protocol-016-PtMumbai.raw/Tezos_raw_protocol_016_PtMumbai/Tx_rollup_l2_apply/index.html
Module Tezos_raw_protocol_016_PtMumbai.Tx_rollup_l2_applySource
This module introduces the interpretation (off-chain) of layer2 operations read from its inboxes.
The main concern is now to interpret operations in the layer2 context with a high-throughput and process a significant number of operations “per second.”
The operations can be crafted with indexes (see Indexable). It is meant to reduce the size of operations, and therefore, increase the number of those in a message to the layer2. You will see in this file indexables which are yet unknowns (see Indexable.unknown). They can be later on modified to indexes only (see Indexable.index_only) when the potential values have been replaced by their indexes.
Therefore, we need to have the minimal number of accesses to the context. Thus, when a value is read from its index in the context, it *must* be done once.
type Tezos_protocol_environment_016_PtMumbai.Error_monad.error += | Counter_mismatch of {account : Tx_rollup_l2_address.t;expected : int64;provided : int64;
}| Incorrect_aggregated_signature| Unallocated_metadata of int32| Multiple_operations_for_signer of Tezos_protocol_environment_016_PtMumbai.Bls.Public_key.t| Invalid_transaction_encoding| Invalid_batch_encoding| Unexpectedly_indexed_ticket| Missing_ticket of Alpha_context.Ticket_hash.t| Unknown_address of Tx_rollup_l2_address.t| Invalid_self_transfer| Invalid_zero_transfer| Maximum_withdraws_per_message_exceeded of {}
type indexes = {address_indexes : (Tx_rollup_l2_address.t * Tx_rollup_l2_address.Indexable.index) list;ticket_indexes : (Alpha_context.Ticket_hash.t * Tx_rollup_l2_context_sig.Ticket_indexable.index) list;
}Applying operations in the layer2 can result in creating indexes associated to both the addresses and the ticket hashes. We keep track of these creations in order to replace the values by their indexes in future operations.
The record of parameters used during the application of messages.