Warp backend database pruning #471
Description
The warp backend has a database that saves the UnsignedMessage upon AddMessage calls, mostly to address case when node gets restarted and changes its bls key. Follow up from warp backend is to have a periodic cleanup of database messages.
Solutions:
- Two indices database of message hash and prefix timestamp Warp backend interface and implementation #452 (comment)
- Generational pruning with two tables, "new" vs "old" tables that get migrated over. Warp backend interface and implementation #452 (comment)