package octez-shell-libs
Install
Dune Dependency
Authors
Maintainers
Sources
sha256=ddfb5076eeb0b32ac21c1eed44e8fc86a6743ef18ab23fff02d36e365bb73d61
sha512=d22a827df5146e0aa274df48bc2150b098177ff7e5eab52c6109e867eb0a1f0ec63e6bfbb0e3645a6c2112de3877c91a17df32ccbff301891ce4ba630c997a65
doc/octez-shell-libs.shell/Tezos_shell/Prevalidator_bounding/index.html
Module Tezos_shell.Prevalidator_boundingSource
Bound the valid operations in the mempool by limiting both their cardinal and their total byte size.
type config = {max_operations : int;(*Maximal allowed number of valid operations in the mempool.
*)max_total_bytes : int;(*Maximal allowed sum of the byte sizes of all valid operations in the mempool.
*)
}Mempool bounds.
They can be retrieved/set using RPCs GET/POST /chains/<chain>/mempool/filter.
Default max_total_bytes is 10_000_000.
A block can have at most around 700k bytes of operations (see validation_passes in proto_xxx/lib_protocol/main.ml). So with this bound, a mempool can have the content of more than 10 blocks, which is more than enough.
Default max_operations is 10_000.
The smallest operations are around 140 bytes (e.g. 139 bytes for a (pre)attestation, 146 bytes for a delegation) so a block can have at most around 5_000 operations. But many operations are much larger, so in practice a block contains much less operations, so keeping 10_000 of them in the mempool is enough.
Encoding for config.
It is internally an object without any variable field, so it is possible to use it in a Data_encoding.merge_objs.
module Make
(Proto : Tezos_protocol_environment.PROTOCOL) :
T with type protocol_operation = Proto.operationBuild a mempool bounding module.