From ed25519 seed to Polkadot.js about substrate-ledger-ed25519 HOT 5 CLOSED

Dangit, my bad. It is indeed expected, I should have explained above, guess I need more coffee.

So the extension only does sr25519, no ed25519 when creating from seed.

So if you wish to import into the extension, it is a bit of work-around.

• Add it to the apps UI
• Export the JSON (or just use the one created at creation)
• Import this to the extension

So basically on import the extension allows anything, ed25519, sr25519 or edcsa.

from substrate-ledger-ed25519.

The extension doesn't support Ethereum/Bitcoin/Other-style derivation paths. Only Polkadot/substrate derivation paths are supported since that is the standard in the ecosystem.

With this cli tool, once you have generated the raw seed, you can just add it to the extension where the mnemonic is supposed to go, i.e. past 0x... into the seed box. (The extension supports both mnemonics and hex-seeds there)

from substrate-ledger-ed25519.

pasting the 0x... seed (ed25519 seed from this tool) into the seed box of polkadotjs extension leads to an address that doesn't match the expectations (address (DOT) from this tool)... No derivation path inserted.

Doing the same in polkadot js web app kind of work instead, but only if you tune the advanced creation options from the default Shnorkell to Edwards

Is this expected ? wdyt ?

from substrate-ledger-ed25519.

Very nice, thanks.
I think we can close it.

Have a good one

from substrate-ledger-ed25519.

Hi, can you explain how to import account with JSON file using the extension as import through web app is no longer possible ? How can I get that JSON file ? This file is generated by the tool or I need to generate it myself using seed generated by the tool ?
Thank you

from substrate-ledger-ed25519.