Repository navigation
Keep a producer's nodes when their endpoints serve this chain - #3
Merged
Merged
Conversation
On every network but EOS, a producer without a chains.json had its /bp.json treated as its EOS file and everything but the org details dropped, including its nodes. That rightly ignores EOS Nation's, EOS Rio's and others' EOS bp.json on Jungle, but also dropped panshieosbp1's Jungle-only bp.json, so it had no nodes or API endpoints. The nodes are now kept when one of the bp.json's own API endpoints reports this chain's ID. Co-Authored-By: Claude Opus 5.5 <[email protected]>
Keep a producer's nodes when their endpoints serve this chain
This file contains hidden or 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.
From Rossco99/antelope-tools#23.
panshieosbp1 didn't show up on Jungle's API Endpoints page. Producers without a
chains.jsonhad their/bp.jsontreated as their EOS file on every other network, so their nodes were dropped. That is right for EOS Nation, EOS Rio and others on Jungle, but wrong for Panshi's Jungle-only bp.json.The dashboard now asks one of the bp.json's own API endpoints which chain it serves, and keeps the nodes if it is this chain.
Effect on live producers:
Passed the build-and-smoke CI on the fork; tested on a production build of Jungle.
🤖 Generated with Claude Code