Closed dryruner closed 5 years ago
Hey, what is your question?
@bkchr Hi what I'm asking is:
shouldn't the public key yielded by subkey -e generate
be the same public key generated by inspecting on the same mnemonic? However, as shown in the example above, they're not the same, why is that?
We noticed same issue.
Seed: 0xe989b242dd358858476667bfc3d1c92a96e00c41d8ea1f46f47c4ee154fe323f
Public key (hex): 0xe989b242dd358858476667bfc3d1c92a96e00c41d8ea1f46f47c4ee154fe323f
Note that the seed part and public key part are same. This is clearly a mistake.
I looked into this.
subkey generte
expects the seed. If you give it the seed it always outputs the correct data.
Based on the implementation, there is currently no way to recover from the mnemonic. (But implementing this should not be that complicated).
Okay, another update. You need to add ///
at the end of your mnemonic and then inspect
also works correctly.
This clearly needs some better documentation.
Re @bkchr : generate should not take any seed/mnemonic imo, as it's used to generate one :)
Also:
$ subkey -e inspect "island morning track vast rhythm rebel vendor hold buffalo place east exhaust///"
Secret Key URI `island morning track vast rhythm rebel vendor hold buffalo place east exhaust///` is account:
Seed: 0xe989b242dd358858476667bfc3d1c92a96e00c41d8ea1f46f47c4ee154fe323f
Public key (hex): 0xe989b242dd358858476667bfc3d1c92a96e00c41d8ea1f46f47c4ee154fe323f
Address (SS58): 5HLuvEbZs7SzwUMzd6RmdeN76cFYdSRvRVqXurE9z6A1cinV
Still not working
Please try with latest Master.
Example:
However, there's no such issue for -s/--sr25519 option.
Version: