package tezos-protocol-013-PtJakart
Install
Dune Dependency
Authors
Maintainers
Sources
sha256=43723d096307603703a1a89ed1b2eb202b365f5e7824b96b0cbf813b343a6cf7
sha512=b2a637f2e965000d3d49ad85277ca24d6cb07a1a7cf2bc69d296d8b03ad78c3eaa8e21e94b9162e62c2e11649cd03bc845b2a3dafe623b91065df69d47dc8e4f
doc/tezos-protocol-013-PtJakart.raw/Tezos_raw_protocol_013_PtJakart/Tx_rollup_l2_apply/index.html
Module Tezos_raw_protocol_013_PtJakart.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_013_PtJakart.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_013_PtJakart.Bls_signature.pk| 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.