Duplicate of #3413, which was auto-closed for inactivity without resolution. Same setup, same wall.
Setup
| Item |
Value |
| Hardware |
Ledger |
| Cosmos app path |
44'/118'/0'/0/0 |
| Native address |
sei178wsr62lq25crpvag0r5wep2jplw3jqvtyvmuv |
| Associated EVM address (pre-SIP-03) |
0x6fDbd0C807E734E8916F11BAdDc38bF8410A7C19 |
| Ethereum app address (path 60) |
*** — different address/keypair |
Verified
- Cosmos app at path 118 derives my
sei1... address (confirmed via @ledgerhq/hw-app-cosmos)
- Ledger Ethereum app rejects
getAddress at path 118 → 0x6a15
- Ledger Sei app rejects same call →
0x6984
- Cosmos-format txs no longer broadcastable post-June 15
Problem
I provably hold the key, but no Ledger app will produce an EVM signature from the path-118 keypair. Funds (including staked SEI) are accessible only at 0x6fDb..., which nothing can sign for.
Questions (same as #3413, unanswered)
- Does the chain accept a path-118 keypair signature calling the staking precompile (
0x...1005)?
- What tooling can produce such a signature with a Ledger (no key export)?
- Is there a sanctioned recovery flow for this case?
Duplicate of #3413, which was auto-closed for inactivity without resolution. Same setup, same wall.
Setup
Verified
sei1...address (confirmed via@ledgerhq/hw-app-cosmos)getAddressat path 118 →0x6a150x6984Problem
I provably hold the key, but no Ledger app will produce an EVM signature from the path-118 keypair. Funds (including staked SEI) are accessible only at
0x6fDb..., which nothing can sign for.Questions (same as #3413, unanswered)
0x...1005)?