patch: More work to get wildcard addresses to work (includes local patch to skar-client for testing) #11
+2,745
−27
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
|
Sorry this is the main branch. The rebase is WIP. |
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.
feat: Allow multiple wildcard addresses by varying the last byte of 0x000000...
Added a local patch for the skar-client for testing.
Sorry this was easier to get a built version with the changes to copy into node_modules.
Added non-wildcards to show up as both event and sigHash queries (since it's extremely unlikely there will be an overlap on the first 4 digits of the hash it's capable of monitoring both Events and sigHash of the same items. It will construct fake Log entries to correctly decode the function signature and parameters.