docs: SIP-03 migration path for mnemonic-only and hardware wallets#25
Conversation
PR SummaryLow Risk Overview 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 The FAQ gains a matching entry; frontmatter keywords expand for Ledger/hardware/mnemonic topics. A broken USDC.n FAQ anchor is corrected from Reviewed by Cursor Bugbot for commit e85520a. Bugbot is set up for automated code reviews on this repo. Configure here. |
|
Preview deployment for your docs. Learn more about Mintlify Previews.
💡 Tip: Enable Workflows to automatically generate PRs for you. |
7d0b3c1 to
4a54959
Compare
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>
4a54959 to
e85520a
Compare
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:
0xandsei1addresses in any wallet. If you can export one, that's still the recommended path.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 thatsei1...(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 theaddrprecompile.Notes
#3-usdc-on-sei, but the heading is### 2) USDC on Sei(#2-usdc-on-sei).mint broken-linkspasses (run under Node 22 — the CLI doesn't support Node 25+).🤖 Generated with Claude Code