package tezos-protocol-015-PtLimaPt
- Overview
- No Docs
You can search for identifiers within the package.
in-package search v0.2.0
Install
dune-project
Dependency
Authors
Maintainers
Sources
sha256=ad9e08819871c75ba6f4530b125f7d157799398e4d77a1e6bfea9d91ff37ff55
sha512=c5dc4d40cc09bc6980fbbdb5c2e105bf4252cf9cfcb2b49660b0ebe4dc789f6709ec3b3bf2f87d81580d3eed9521eeb1c960f24d9b14eb0285aaba1f84d10a9b
doc/tezos-protocol-015-PtLimaPt.raw/Tezos_raw_protocol_015_PtLimaPt/Tx_rollup_message_repr/index.html
Module Tezos_raw_protocol_015_PtLimaPt.Tx_rollup_message_reprSource
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).
type deposit = {sender : Tezos_protocol_environment_015_PtLimaPt.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.