Skip to content

Files

This branch is 2 commits ahead of, 1541 commits behind cosmos/cosmos-sdk:main.

store

Folders and files

NameName
Last commit message
Last commit date

parent directory

..
Mar 21, 2024
Apr 8, 2024
Mar 8, 2024
Mar 25, 2024
Nov 28, 2023
Mar 21, 2024
Mar 25, 2024
Apr 8, 2024
Mar 21, 2024
Apr 1, 2024
Dec 8, 2023
Feb 23, 2024
Mar 20, 2024
Mar 25, 2024
Apr 9, 2024
Apr 9, 2024
Feb 13, 2024
Jan 25, 2023
Mar 20, 2024
Mar 28, 2024
Oct 18, 2023

Store

The store package contains the implementation of store/v2, which is the SDK's abstraction around managing historical and committed state. See ADR-065 and Store v2 Design for a high-level overview of the design and rationale.

Migration

Pruning

The root.Store is NOT responsible for pruning. Rather, pruning is the responsibility of the underlying SS and SC layers. This means pruning can be implementation specific, such as being synchronous or asynchronous.

Usage

The store package contains a root.Store type which is intended to act as an abstraction layer around it's two primary constituent components - state storage (SS) and state commitment (SC). It acts as the main entry point into storage for an application to use in server/v2. Through root.Store, an application can query and iterate over both current and historical data, commit new state, perform state sync, and fetch commitment proofs.

A root.Store is intended to be initialized with already constructed SS and SC backends (see relevant package documentation for instantiation details). Note, from the perspective of root.Store, there is no notion of multi or single tree/store, rather these are implementation details of SS and SC. For SS, we utilize store keys to namespace raw key/value pairs. For SC, we utilize an abstraction, commitment.CommitStore, to map store keys to a commitment trees.