package tezos-protocol-014-PtKathma
Tezos/Protocol: economic-protocol definition
Install
Dune Dependency
Authors
Maintainers
Sources
tezos-16.1.tar.gz
sha256=43723d096307603703a1a89ed1b2eb202b365f5e7824b96b0cbf813b343a6cf7
sha512=b2a637f2e965000d3d49ad85277ca24d6cb07a1a7cf2bc69d296d8b03ad78c3eaa8e21e94b9162e62c2e11649cd03bc845b2a3dafe623b91065df69d47dc8e4f
doc/tezos-protocol-014-PtKathma.raw/Tezos_raw_protocol_014_PtKathma/Tx_rollup_message_repr/index.html
Module Tezos_raw_protocol_014_PtKathma.Tx_rollup_message_repr
Source
Communication from the layer-1 (Tezos) to the layer-2 (a transaction rollup) happens thanks to messages, crafted in the layer-1 to be interpreted in the layer-2.
Messages are constructed and gathered in the layer-1, in inboxes (see Tx_rollup_repr_storage.append_message
).
Source
type deposit = {
sender : Tezos_protocol_environment_014_PtKathma.Signature.Public_key_hash.t;
destination : Tx_rollup_l2_address.Indexable.value;
ticket_hash : Ticket_hash_repr.t;
amount : Tx_rollup_l2_qty.t;
}
Smart contract on the layer-1 can deposit tickets into a transaction rollup, for the benefit of a Tx_rollup_l2_address.t
. The sender
is an implicit account where the deposit is returned in form of a withdrawal, should the application of the deposit fail.
A message
is a piece of data originated from the layer-1 to be interpreted by the layer-2.
Transaction rollups feature two kind of messages:
- An array of bytes that supposedly contains a valid sequence of layer-2 operations; their interpretation and validation is deferred to the layer-2..
- A deposit order for a L1 ticket.
size msg
returns the number of bytes that are allocated in an inbox by msg
.
sectionYPositions = computeSectionYPositions($el), 10)"
x-init="setTimeout(() => sectionYPositions = computeSectionYPositions($el), 10)"
>