Closed HS-Joe closed 2 years ago
Same error using sentinel but showing the correct address and can get balance as in keplr
Thanks guys - by the sound of it then, the slip44
path in Chain Registry is incorrect for Sentinel. Or at least doesn't match what Keplr is using, and Keplr supports Sentinel natively.
The solution for you guys is to use slip44: 118
explicitly in your networks.local.json
file. REStake uses that by default now, which is why you see the correct address when you don't set correctSlip44: true
. However this will change in the future when we use the Chain Registry version by default, and I can't be sure if the Sentinel mismatch will be solved by then.
Keeping this open for visibility/reference.
@tombeynon OK thanks for the advice, it is working.
Also had to use "correctSlip44": true
for persistence and desmos, is that expected?
That's correct. You can see the slip44
in the chain-registry, if it's different than 118 then it will need this config.
In the future 'correctSlip44' will be the default, which is why it's so noisy in the script.
OK thanks for the explanation. Should i close this issue?
Chain Registry has merged the correct Slip44 path now
Hey guys,
I have a warning for sentinel about not using the preferred derivation path, though Keplr shows me the same wallet address. When setting
and running the script again, it logs a bot wallet address I don't know about (i.e. not the one showing up in keplr with this mnemonic. Could you check that? Had the same warning for lumnetwork, and in this case the displayed wallet did match the one in keplr, so for lum it seems indeed correct.