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
..
f00_system.go	consolidate all blockstores in blockstore package.	2021-01-29 20:01:00 +00:00
f01_init.go	consolidate all blockstores in blockstore package.	2021-01-29 20:01:00 +00:00
f02_reward.go	consolidate all blockstores in blockstore package.	2021-01-29 20:01:00 +00:00
f03_cron.go	consolidate all blockstores in blockstore package.	2021-01-29 20:01:00 +00:00
f04_power.go	consolidate all blockstores in blockstore package.	2021-01-29 20:01:00 +00:00
f05_market.go	consolidate all blockstores in blockstore package.	2021-01-29 20:01:00 +00:00
f06_vreg.go	consolidate all blockstores in blockstore package.	2021-01-29 20:01:00 +00:00
genblock.go	proper genesis block history	2020-08-17 21:13:43 -07:00
genesis.go	segregate chain and state blockstores.	2021-02-28 22:49:44 +00:00
miners.go	segregate chain and state blockstores.	2021-02-28 22:49:44 +00:00
util.go	use the correct network version in genesis	2020-10-21 12:18:38 -07:00