add 2021 testnet to api constructors #797
Open
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.
Per report from @uscinski
We've been deploying archive nodes on OPF side. So far we have Testnet gRPC 2022-03-03 and 2021-04-13. We tried to run Nexus analyzer that includes these both archive nodes. But Nexus crashes with the following error:
To me it looks like Nexus lacks implementation of the historical API and therefore cannot work with the said node. Is this correct or do we need to configure it differently (both Nexus and gRPC node)? We also tried to include only the 2022-03-03 archive node and so far looks good.