chore(db): Link vault archival job to Issue 37#191
Merged
JerryIdoko merged 1 commit intoVesting-Vault:mainfrom Mar 26, 2026
Merged
chore(db): Link vault archival job to Issue 37#191JerryIdoko merged 1 commit intoVesting-Vault:mainfrom
JerryIdoko merged 1 commit intoVesting-Vault:mainfrom
Conversation
Adds documentation mapping the existing vault archival job to the cold storage issue requirements. Fixes Vesting-Vault#37
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Resolves #37
Summary
This PR officially closes Issue #37. The requested cold storage mechanism is already fully implemented and actively running in the application. I have added a documentation comment to explicitly link the file to the issue.
Verification Details
archived_vaultstable creation logic is verified and present inVaultArchivalJob.initializeTable().claimable_balanceis zero andend_timehas passed before moving the data to the archive table and deleting the active record within a safe database transaction.