fix(schema): align wallet audit field (#2682) - #3595
Open
Larslllllll wants to merge 1 commit into
Open
Conversation
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
1 participant
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.
Summary
Adds the minimal
json-toolsprerequisite for approved DBIP #2682 and the coordinated data PR #3563.Changes
$defs.wallets.properties.audittoauditsPerformedauditcolumn metadataauditsPerformedmetadata already used by bridges, oracles, and rampsWhy this PR
The previous tools attempt #3114 was closed after CI issues and included an unrelated workflow rewrite. This recreation changes only the two schema/meta files needed by the approved DBIP.
Validation
auditsPerformedand no legacyauditauditsPerformedmetadata exists; legacyauditmetadata is removedgit diff --checkpassesCoordination
This targets
json-tools. After merge, I will isolate existing data PR #3563 ontoupstream/mainso it contains only the 90 header renames and can pass CI.No separate reward is claimed for this prerequisite; the approved DBIP's 10 USDC remains assigned once to the complete data implementation in #3563.