Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Adding the BlueChip Chain #684

Closed
wants to merge 9 commits into from
Closed

Conversation

Bluechip23
Copy link
Contributor

This is the initial push to add BlueChip to valid Keplr chains

Copy link

vercel bot commented Jun 23, 2024

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name Status Preview Comments Updated (UTC)
keplr-chain-registry ✅ Ready (Inspect) Visit Preview 💬 Add feedback Sep 11, 2024 7:14am

Copy link
Collaborator

@editaahn editaahn left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Hey, please set the file format to JSON.
Also, since all the validations should be successfully done, check the instruction on the README!

cosmos/bluechip Outdated
Comment on lines 5 to 6
"rpc": "http://67.218.8.88:26660/",
"rest": "http://67.28.8.88:1318/",
Copy link
Collaborator

@editaahn editaahn Jun 24, 2024

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Could you replace the url scheme to https? http wouldn't work on iOS Keplr Mobile for now.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@editaahn I am getting this error "Chain identifier unmatched: (expected: bluechip_1, actual: bluechip)" when trying to run the verification locally. Where is this pulling information from? Our chainId is bluechip_1

Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The chain identifier is bluechip_1! Try it for the JSON name and the image directory name.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I believe that worked. Although it may be worth changing to bluechip-1 before we add more than our original validator to make things more convenient...

We are just working on getting our restAPIs to sync with the https I will hold off on re submitting until then.

@Bluechip23
Copy link
Contributor Author

we are having troubles with having a HTTPS node for RPC and REST on the same node as the validator. Is this common? Do we need a separate running node?

@editaahn
Copy link
Collaborator

editaahn commented Jul 6, 2024

Yup we found the issue last month so there now must be an error on some chains communicating via HTTP. Therefore we made a validation for it. Sorry for any inconveniences.

@Bluechip23
Copy link
Contributor Author

Ok thank you for the reply. We will work on getting a separate node to run our RPC and REST endpoints if that is required. Thank you.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants