Support for monero hard fork v15 (view tags) #7
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
|
Thanks for the PR, I'm currently testing this patchset and will merge if all looks good. |
|
Looks good, tested as working w/ the main nodejs-pool codebase. Thanks for the PR! |
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.
In Monero's upcoming hard fork (scheduled for ~August 13th, block 2,688,888), every output will begin needing to have a "view tag" as described here.
As reported in Snipa22/nodejs-pool#496, blocks won't parse after the hard fork unless support for view tags is added.
This PR adds support for view tags and was confirmed working by @osensei . I haven't gotten a dev env set up to test these changes yet myself.