Add script to sync signatures with 4bytes #855
Merged
Conversation
This file contains 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.
To run the signature sync:
yarn run:4bytes.Script will pull all event/function signatures from artifacts/ and sync them with 4bytes if we've not previously syncced that signature with 4bytes.
The
scripts/4bytes-syncced.jsonfile has been added to the repo, this file contains all the signatures we've previously syncced. The file is updated asyarn run:4bytesworks through the signatures.If you run the script locally, be sure to commit the
scripts/4bytes-syncced.jsonto history.I also added a workflow that should trigger whenever we merge to master. This workflow will trigger the sync file and commit it to history when done.