Join GitHub today
GitHub is home to over 28 million developers working together to host and review code, manage projects, and build software together.Sign up
Spentaddresses are persisted upon pruning #1258
This persists to the spent addresses db column family all the spent addresses from pruned transactions that were verified by the bundle validator.
We want the node to correctly verify spent addresses even after the corresponding transactions were pruned.
Type of change
How Has This Been Tested?
TBD... Blocked from merging until tested.
Jan 8, 2019
6 checks passed
Tested by setting up a node in testnet, and generating transactions and milestones until the node started taking snapshots. Then some value transactions were sent (while still spamming milestones and zero values) and I waited until they were close to pruning depth. I used
Once this process was completed I stopped the spammers and restarted the node. When I rechecked the consistency and checked for persisted SpentAddress objects again, the transactions were pruned and the db SpentAddress objects were still there.