[hermes] Move GuardianSet sourcing from Ethereum to PythNet #894
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.
The code currently relies on reading GuardianSet state updates from Ethereum, this PR switches that to relying on reading GuardianSet accounts from Wormhole deployed on PythNet. We should be safe to do this as Wormhole upgrade all other target chain contracts before Ethereum, so we will not run into a situation where we receive VAA's that are signed by keys we have not yet seen.