You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Since about a week Keplr is no longer working with the Akash sandbox (chain id: sandbox-01). We traced down the issue to PR #291 which add the Nyx chain with a chain id of sandbox. I'm guessing the issue is caused by both chains having the same network identifier (sandbox). This causes keplr to return a Nyx address instead of an Akash one even if Akash Sandbox was previously added to keplr with the Suggest feature.
PR #485 was created to add Akash Sandbox to the keplr registry, but it's unclear how this duplicate identifier will be handled by Keplr. This is affecting Akash users since they can no longer deploy and manage their deployment using the browser.
The text was updated successfully, but these errors were encountered:
Since about a week Keplr is no longer working with the Akash sandbox (chain id:
sandbox-01
). We traced down the issue to PR #291 which add the Nyx chain with a chain id ofsandbox
. I'm guessing the issue is caused by both chains having the same network identifier (sandbox
). This causes keplr to return a Nyx address instead of an Akash one even if Akash Sandbox was previously added to keplr with the Suggest feature.PR #485 was created to add Akash Sandbox to the keplr registry, but it's unclear how this duplicate identifier will be handled by Keplr. This is affecting Akash users since they can no longer deploy and manage their deployment using the browser.
The text was updated successfully, but these errors were encountered: