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

Add correct Sei cointypes #819

Closed
wants to merge 2 commits into from
Closed

Conversation

alexander-sei
Copy link

As dicussed here (#818), we're submitting this PR with some changes made:

Both Sei EVM and Sei Cosmos both get Cointype 60 and Cointype 118 set as supported, with cointype 118 set as main and cointype 60 as an additionally supported cointype.

Supporting both cointype 118 and cointype 60, with cointype 118 being the primary cointype supported.
Ddds the cointype 60 as an alternative BIP44 for the address derivation for the Cosmos compatible part of Sei mainnet (pacific-1).
Copy link

vercel bot commented Oct 9, 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 Oct 9, 2024 5:34pm

@delivan
Copy link
Member

delivan commented Oct 10, 2024

@alexander-sei Unfortunately, we should do some works to support cointype 60 in alternativeBIP44s for now. We understand this is important for cosmos-evm chains, so It is in our short-term roadmap. Let me re-open and merge this PR if the issue is resolved.

@delivan delivan closed this Oct 10, 2024
@cordt-sei
Copy link

Hey @delivan all we need really is to have both 118 and 60 accessible to the user as an option. Without having both of these (or a single unified cointype, which ultimately is also harmful to users) for both the Cosmos and EVM side of Sei the functionality is completely broken as it is a necessity for the interoperability features of the chain.

If it makes more sense, please set up a call and we can discuss this: https://calendly.com/cordt-seifdn/30min

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.

3 participants