Skip to content

oasis-node: Independent consensus light history and pruning #6430

@martintomazic

Description

@martintomazic

Context

It has become impractical to keep all state from the genesis thus more and more nodes are pruning it.

Problem

  1. Pruning is already causing availability issues:
  2. Consensus light blocks are computed ad-hoc, from the full state:
    • Running observer with historical state requires all consensus data, just to fetch light blocks - see.

Solution:

  1. Create additional DB for consensus light blocks and query them from there.
  2. Independent full-state (NodeDB && blockstore) vs light state pruning.
    • E.g. keep 1 year of light history by default (should be few GB max).

Follow-ups:

  1. Similar thing should be done for the runtime state and its pruning (go: Storage committee worker should be responsible for both runtime light history and state #6400).
  2. History expiry.

Metadata

Metadata

Assignees

Labels

No labels
No labels

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions