package tezos-protocol-alpha
Install
Dune Dependency
Authors
Maintainers
Sources
sha256=ad9e08819871c75ba6f4530b125f7d157799398e4d77a1e6bfea9d91ff37ff55
sha512=c5dc4d40cc09bc6980fbbdb5c2e105bf4252cf9cfcb2b49660b0ebe4dc789f6709ec3b3bf2f87d81580d3eed9521eeb1c960f24d9b14eb0285aaba1f84d10a9b
doc/tezos-protocol-alpha.raw/Tezos_raw_protocol_alpha/Tx_rollup_l2_context_sig/index.html
Module Tezos_raw_protocol_alpha.Tx_rollup_l2_context_sigSource
An integer used to identified a layer-2 address. See Tx_rollup_l2_address.index.
An integer used to identified a layer-1 ticket deposited in a transaction rollup.
type metadata = {counter : int64;public_key : Tezos_protocol_environment_alpha.Bls.Public_key.t;
}The metadata associated to a layer-2 address.
The counter is an counter-measure against replay attack. Each operation is signed with an integer (its counter). The counter is incremented when the operation is applied. This prevents the operation to be applied once again, since its integer will not be in sync with the counter of the account. The choice of int64 for the type of the counter theoretically prevents the rollup to an integer overflow. However, it can only happen if a single account makes more than 1.8446744e+19 operations. If an account sends 1000 operations per seconds, it would take them more than 5845420 centuries to achieve that.
The public_key allows to authenticate the owner of the address, by verifying BLS signatures.
type Tezos_protocol_environment_alpha.Error_monad.error += | Balance_too_low| Balance_overflow| Invalid_quantity| Unknown_address_index of address_index| Metadata_already_initialized of address_index| Too_many_l2_addresses| Too_many_l2_tickets| Counter_overflow