After receiving a RAV and verifying/storing it the associated receipts can be deleted. This issue is to track adding this feature.
Some details to design around:
Best way to delete the correct receipts:
currently verify_and_store_rav only receives the received and expected RAV, so the only info we have there is what is on the RAV. We could therefore delete all receipts up to that timestamp. If there were any receipts that were received after the RAV request but with an earlier timestamp then they would be included in the deletion but not the RAV.
we could alternatively store a list of receipt IDs with the expected RAV and provide that list to be deleted
When/if to delete the receipts:
probably YAGNI, but should we allow the user to config whether or not receipts get deleted?
If the receipts are deleted should it be done as a side affect of verify_and_store_rav, as a stand alone function, or some other time?
After receiving a RAV and verifying/storing it the associated receipts can be deleted. This issue is to track adding this feature.
Some details to design around:
verify_and_store_ravonly receives the received and expected RAV, so the only info we have there is what is on the RAV. We could therefore delete all receipts up to that timestamp. If there were any receipts that were received after the RAV request but with an earlier timestamp then they would be included in the deletion but not the RAV.verify_and_store_rav, as a stand alone function, or some other time?