Raúl Kripalani 3795cc2bd2 segregate chain and state blockstores. ... This paves the way for better object lifetime management. Concretely, it makes it possible to: - have different stores backing chain and state data. - having the same datastore library, but using different parameters. - attach different caching layers/policies to each class of data, e.g. sizing caches differently. - specifying different retention policies for chain and state data. This separation is important because: - access patterns/frequency of chain and state data are different. - state is derivable from chain, so one could never expunge the chain store, and only retain state objects reachable from the last finality in the state store.		2021-02-28 22:49:44 +00:00
..
api.go	workers: Simple storage diagnostics	2020-03-16 18:50:07 +01:00
beacon.go	Draw the rest of the owl	2020-09-10 17:41:55 -04:00
bootstrap.go	Assign positive scores to drand bootstrappers	2020-06-08 11:34:46 +02:00
chain.go	Get network name from genesis	2020-04-01 01:15:49 +02:00
miner.go	Allow miners to filter (un)verified deals	2020-12-02 01:32:34 -05:00
mpool.go	Config for default max gas fee	2020-10-29 20:50:11 +01:00
scorekeeper.go	support extended pubsub peer scores	2020-07-31 11:27:22 +03:00
shutdown.go	update storage miner and seal worker document	2020-07-11 16:55:13 +08:00
storage.go	segregate chain and state blockstores.	2021-02-28 22:49:44 +00:00