-
Notifications
You must be signed in to change notification settings - Fork 510
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
Conversation
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
There was a problem hiding this 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
"rpc": "http://67.218.8.88:26660/", | ||
"rest": "http://67.28.8.88:1318/", |
There was a problem hiding this comment.
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.
There was a problem hiding this comment.
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
There was a problem hiding this comment.
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.
There was a problem hiding this comment.
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.
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? |
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. |
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. |
This is the initial push to add BlueChip to valid Keplr chains