-
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
Request to add Akash Network Sandbox #485
base: main
Are you sure you want to change the base?
Conversation
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
cosmos/akashsandbox.json
Outdated
"chainId": "sandbox-01", | ||
"chainName": "AkashSandbox", | ||
"chainSymbolImageUrl": "https://raw.githubusercontent.com/chainapsis/keplr-chain-registry/main/images/akashnet/chain.png", | ||
"experimental": true, |
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.
@vatsal2809 Hello Could you remove experimental
field?
@vatsal2809 Could you check your chain identifier?
|
The reason for writing chain identifier different than sandbox is explained in above screenshots. If we write "sandbox" then it gets connected to sandbox of some other chain named "nym". That is the reason why I have written Akashsandbox. |
@vatsal2809 Do you have any idea why the chain IDs overlap? |
I don't know quite about that, but akash is an old chain and it is having sandbox since 2 years and I don't know how PR of nym(They might have not done enough research) got approved and merged. It was working perfectly fine before 2 weeks but right now it's not working. And the chainId for akash is "sandbox-01" |
This is affecting Cloudmos and Akash Console users as well. Users cannot create or manage their sandbox deployments using keplr because of this. #486 |
I cleared the information with the chain id
|
Add Akash Network Sandbox