Skip to content

docs: SIP-03 migration path for mnemonic-only and hardware wallets#25

Merged
alexander-sei merged 1 commit into
mainfrom
docs/sip-03-migrate-without-private-key
Jun 8, 2026
Merged

docs: SIP-03 migration path for mnemonic-only and hardware wallets#25
alexander-sei merged 1 commit into
mainfrom
docs/sip-03-migrate-without-private-key

Conversation

@alexander-sei

Copy link
Copy Markdown
Collaborator

What is the purpose of the change?

Adds new content to the SIP-03 Migration Guide. It documents how to migrate a Cosmos account to Sei EVM in the cases where the usual "export your private key into an EVM wallet" advice doesn't apply — a recurring support question.

Describe the changes to the documentation

Target audience: non-technical end users migrating during SIP-03 whose wallet won't hand them a usable raw private key.

New section "Migrating a hardware or mnemonic-only wallet" (placed after the USDC tools, before the FAQ), plus a matching FAQ entry that links to it.

It clarifies a distinction that trips people up:

  • Exporting a raw private key always works — a private key carries no coin type, so it reproduces the same 0x and sei1 addresses in any wallet. If you can export one, that's still the recommended path.
  • What actually fails:
    • Mnemonic-only wallets — Sei Cosmos accounts derive on coin type 118; importing the phrase into an EVM wallet re-derives at coin type 60, landing on a different account.
    • Ledger / hardware wallets — export nothing at all; you can only switch between the Cosmos app (118) and Ethereum app (60), which are different accounts.

The workaround documented: create a brand-new account in an EVM wallet you control → fund it (~0.1 SEI for the association tx) → associate it on dashboard.sei.io to reveal its paired sei1... address → send your old Cosmos funds to that sei1... (1 SEI test transfer first) → confirm → send the rest. The assets end up on a key you control via EVM. Includes a test-first warning and notes on timing, staking (unbond first), and verifying the destination via the addr precompile.

Notes

  • Also fixes a pre-existing dead anchor: the USDC.n FAQ linked to #3-usdc-on-sei, but the heading is ### 2) USDC on Sei (#2-usdc-on-sei).
  • mint broken-links passes (run under Node 22 — the CLI doesn't support Node 25+).
  • Content-only change to the user-facing migration page; the exchange/custodian page is untouched.

🤖 Generated with Claude Code

@cursor

cursor Bot commented Jun 8, 2026

Copy link
Copy Markdown

PR Summary

Low Risk
Documentation-only edits to the migration guide; no runtime or security-sensitive code changes.

Overview
Adds SIP-03 guidance for users who cannot migrate by exporting a raw private key (mnemonic-only wallets and hardware wallets such as Ledger), including when raw-key import still works versus coin-type 118 vs 60 pitfalls.

A new section Migrating a hardware or mnemonic-only wallet documents the fund-move workaround: create a new EVM account, fund it for gas, associate on the Sei Dashboard to get the paired sei1... address, then Cosmos-send funds (1 SEI test first) to that address so balances are spendable from the EVM wallet. It includes warnings, pre-upgrade timing, staking/unbonding limits, and optional addr precompile verification.

The FAQ gains a matching entry; frontmatter keywords expand for Ledger/hardware/mnemonic topics. A broken USDC.n FAQ anchor is corrected from #3-usdc-on-sei to #2-usdc-on-sei.

Reviewed by Cursor Bugbot for commit e85520a. Bugbot is set up for automated code reviews on this repo. Configure here.

@mintlify

mintlify Bot commented Jun 8, 2026

Copy link
Copy Markdown
Contributor

Preview deployment for your docs. Learn more about Mintlify Previews.

Project Status Preview Updated (UTC)
sei-docs 🟢 Ready View Preview Jun 8, 2026, 11:19 AM

💡 Tip: Enable Workflows to automatically generate PRs for you.

Adds a "Migrating a hardware or mnemonic-only wallet" section to the
SIP-03 migration guide for users whose wallet can't hand them a usable
raw private key.

Covers:
- Why raw private-key export always works (the key carries no coin
  type) but exporting a mnemonic does not (re-derived at coin type 60
  in EVM wallets), and Ledger exports nothing — you can only switch
  between the Cosmos (118) and Ethereum (60) apps.
- The workaround: create a new EVM account, fund it (~0.1 SEI for the
  association tx), associate it on the Sei Dashboard to reveal its
  paired sei1 address, then send old Cosmos funds there (1 SEI test
  first), so the assets land on a key the user controls via EVM.
- A matching FAQ entry pointing to the new section.

Also fixes a dead anchor: the USDC.n FAQ linked to #3-usdc-on-sei, but
the heading is "### 2) USDC on Sei" (#2-usdc-on-sei).

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
@alexander-sei alexander-sei force-pushed the docs/sip-03-migrate-without-private-key branch from 4a54959 to e85520a Compare June 8, 2026 15:07
@alexander-sei alexander-sei merged commit 1473e16 into main Jun 8, 2026
10 checks passed
@alexander-sei alexander-sei deleted the docs/sip-03-migrate-without-private-key branch June 8, 2026 15:28
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.

1 participant