Overview
While working on the Constantinople demo, we ran into an issue with the keyless and immutable variants of QMDB where we were unable to partially state sync a global log of transactions.
We should establish a way to only retain a recent range of items in these databases to enable applications to maintain large logs of items, for example committing to all transactions the chain has processed or a nullifier tree.
The answer here might just be for the application to coordinate a prune call during the state transition, though it would be nice for the database to maintain a recent window of items on its own without the application having to concern itself with this.
Overview
While working on the Constantinople demo, we ran into an issue with the
keylessandimmutablevariants of QMDB where we were unable to partially state sync a global log of transactions.We should establish a way to only retain a recent range of items in these databases to enable applications to maintain large logs of items, for example committing to all transactions the chain has processed or a nullifier tree.
The answer here might just be for the application to coordinate a
prunecall during the state transition, though it would be nice for the database to maintain a recent window of items on its own without the application having to concern itself with this.