legacy `sei1...` delegation cannot be unstaked

[wils5833]

I cannot find a supported path to undelegate a legacy sei1... delegation using the Compass wallet paired with a ledger Cosmos wallet.

I need to unstake my Cosmos SEI from Figment so I can migrate to a new EVM address. The official tooling (dashboard.sei.io STAKE page, dashboard.sei.io/dashboard Link Addresses, and the SIP-3 Wallet Upgrade Tool) does not seem to handle the use case of moving a delegation to the new EVM chain. Also I don't seem to be able to unstake anywhere (Keplr can see the stake but I can't unbond it).

This appears to be a real gap, not user error. Filing here in case (a) other delegators are hitting the same wall, and (b) Sei engineers can confirm the supported procedure or add it to docs/UI.

| Item | Value |
| Hardware | Ledger device |
| Cosmos Ledger app coin type | 118 |
| Ethereum Ledger app coin type | 60 |

These two keypairs are not auto-paired (per docs.sei.io/learn/accounts). The standard sei1 ↔ 0x linkage applies within a single keypair, not across.

What I tested (and what I observed)

1. Compass Wallet — Cosmos-side staking actions

• Stake / Claim work. Unstake button is inert (no error message, just doesn't trigger).
• Likely cause: Cosmos-side MsgUndelegate is rejected by chain post-Final-Migration. Compass hasn't shipped a fix for its end-of-life version.

2. Keplr — native staking UI

• Connected via Cosmos Ledger app. Recognises my delegation correctly: SEI to Figment.
• The SEI staking line item shows a warning triangle and is read-only — no Unstake action available.
• Likely cause: Keplr has detected that Cosmos-side undelegate transactions will be rejected and disabled the affordance.

3. dashboard.sei.io/stake connected via MetaMask (path-60)

• "My Staking → Delegations" shows: "You have no delegations."
• Banner text: "You will not be able to stake Sei until this account is associated on chain. Please visit the Dashboard to link your addresses."
• Expected — as my EVM wallet is not the keypair that owns the delegation.

4. SIP-3 Wallet Upgrade Tool (dashboard.sei.io/sip-3-upgrade)

• Successfully connects both wallets (Cosmos Source: sei1..., EVM Destination: 0x).
• Step 2 "Token Selection" tabs: CosmWasm (0), Native Tokens (1) — surfaces the SEI liquid balance.
• No "Delegations" / "Staking" tab. The tool appears to migrate liquid token balances and CW20/CW721, but not delegations.
• An "Error loading assets: Failed to fetch balances" banner is also shown intermittently (separate issue, but worth noting).

What I cannot determine from outside

• Whether the chain accepts a signature from the path-118 keypair (via Cosmos Ledger app) calling the EVM staking precompile at 0x...1005 as 0x_path118 (the auto-derived EVM form of the path-118 keypair) — and what wallet/tool can produce such a signature.
• Whether Sei has a sanctioned procedure for this case that's not surfaced in dashboard.sei.io.
• Whether seid CLI is the intended path for users in this situation (and if so, whether documented).
• Whether the SIP-3 Wallet Upgrade Tool will eventually add a delegations migration option, or if delegations are deliberately out of scope.

What I'm asking

1. What is the supported procedure for undelegating a legacy sei1... delegation post-Final-Migration when the destination is a different keypair from the source? Specifically, with a Ledger-only setup and no seed export.
2. Is the right approach to (a) sign an Associate from the path-118 keypair via Cosmos Ledger app to register the same-keypair sei1... ↔ 0x_path118 association, then (b) call the EVM staking precompile from 0x_path118 using <which wallet/tool>?
3. If yes to (2): is there a wallet that supports EVM-format signing using the Cosmos Ledger app's path-118 derivation, or is seid CLI the intended tool?
4. If neither — what is the supported path?

Reproduction

1. Have a delegation from a Ledger Cosmos-app-derived sei1... address.
2. Connect to dashboard.sei.io/stake via MetaMask using the Ledger Ethereum app (different keypair).
3. Observe: "no delegations" + redirect to address linking.
4. Try Link Addresses — signing message does not reference the legacy sei1....
5. Try SIP-3 Wallet Upgrade Tool — no delegations migration option.

Notes for maintainers

• Happy to test fixes / clarifications. Stake is still on-chain; my source address has SEI liquid for gas.

Thanks

[mike44333222-source]

@wils5833 hey mate, sorry for the inconvenience caused by this issue and are you still facing this issue?

[github-actions]

Thank you for opening this issue and taking the time to share your thoughts.
We’d love to keep moving this forward, but we need a bit more information from you.
Please add any additional details within the next 2 day(s) so we can continue collaborating on a solution together.
If we don’t hear back, the issue will close automatically — but you’re always welcome to reopen it when you’re ready.