Michael Sproul 363f15f362 Use the database to persist the pubkey cache (#2234) ... ## Issue Addressed Closes #1787 ## Proposed Changes * Abstract the `ValidatorPubkeyCache` over a "backing" which is either a file (legacy), or the database. * Implement a migration from schema v2 to schema v3, whereby the contents of the cache file are copied to the DB, and then the file is deleted. The next release to include this change must be a minor version bump, and we will need to warn users of the inability to downgrade (this is our first DB schema change since mainnet genesis). * Move the schema migration code from the `store` crate into the `beacon_chain` crate so that it can access the datadir and the `ValidatorPubkeyCache`, etc. It gets injected back into the `store` via a closure (similar to what we do in fork choice).		2021-03-04 01:25:12 +00:00
..
attestation_production.rs	Disallow attestation production earlier than head (#2130)	2021-01-20 06:52:37 +00:00
attestation_verification.rs	Fix head tracker concurrency bugs (#1771)	2020-10-19 05:58:39 +00:00
block_verification.rs	Pass failed gossip blocks to the slasher (#2047)	2020-12-04 05:03:30 +00:00
op_verification.rs	Use the database to persist the pubkey cache (#2234)	2021-03-04 01:25:12 +00:00
persistence_tests.rs	Use the database to persist the pubkey cache (#2234)	2021-03-04 01:25:12 +00:00
store_tests.rs	Use the database to persist the pubkey cache (#2234)	2021-03-04 01:25:12 +00:00
tests.rs	Advance state to next slot after importing block (#2174)	2021-02-15 07:17:52 +00:00