package octez-shell-libs
Install
Dune Dependency
Authors
Maintainers
Sources
sha256=dbc3b675aee59c2c574e5d0a771193a2ecfca31e7a5bc5aed66598080596ce1c
sha512=b97ed762b9d24744305c358af0d20f394376b64bfdd758dd4a81775326caf445caa57c4f6445da3dd6468ff492de18e4c14af6f374dfcbb7e4d64b7b720e5e2a
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.