Pruning

The sequencer and CometBFT have pruning options that can be used to ensure storage use is kept within reasonable bounds.

Pruning can also be configured for the participant, but we don’t currently recommend enabling it for the SVs.

Sequencer pruning

Can be enabled in helm through the following config:

domain:
  sequencerPruningConfig:
    # Enable or disable sequencer pruning
    enabled: true
    # The pruning interval is the time between two consecutive prunings.
    pruningInterval: "1 hour"
    # The retention period is the time for which the sequencer will retain the data.
    retentionPeriod: "30 days"

Note

It is recommended that sequencer pruning is enabled and the pruningInterval is set to 1 hour and the retentionPeriod to 30 days.

CometBFT pruning

It is enabled by default. Pruning is defined as the number of blocks to keep. Older blocks are pruned.

The number of blocks to keep can be configured under the node helm values key.

  # Number of blocks to keep, used for pruning. 0 -> keep all blocks.
  # Number of blocks to keep for 30 days with an upper bound of 7k blocks/h.
  retainBlocks: 5040000