Skip to content
This repository has been archived by the owner on Nov 15, 2023. It is now read-only.

The peer id generated by the terminal is different from the peer id generated by the subkey #7045

Open
bingryan opened this issue Sep 8, 2020 · 3 comments
Labels
J2-unconfirmed Issue might be valid, but it’s not yet known.

Comments

@bingryan
Copy link

bingryan commented Sep 8, 2020

image

when I run dev mode , get node identity 12D3KooWKEpHANYwey4BdaPRRtSRJseGNxZUo3mgKZr689MJdGv4 :

2020-09-07 18:30:29.138 main INFO sub-libp2p  🏷  Local node identity is: 12D3KooWKEpHANYwey4BdaPRRtSRJseGNxZUo3mgKZr689MJdGv4 (legacy representation: QmeXLzSXyyd8iXBSKdmtxCbCtnJQXoxALquWZzevXm2CNA)

but when I run generate-node-key --file secret_ed25519 get 12D3KooWH4DBA8CtwgFWMLcksDxD6Ybq474bUVLjytHZ34oEH3Fc

➜  network subkey generate-node-key --file secret_ed25519
12D3KooWH4DBA8CtwgFWMLcksDxD6Ybq474bUVLjytHZ34oEH3Fc
➜  network pwd
/home/rust/.local/share/node-template/chains/dev/network

Why are the two different

@github-actions github-actions bot added the J2-unconfirmed Issue might be valid, but it’s not yet known. label Sep 8, 2020
@bingryan
Copy link
Author

bingryan commented Sep 8, 2020

image

use node-key-file

@tomaka
Copy link
Contributor

tomaka commented Sep 11, 2020

Now that #7052 is merged, do we also fix the change accidentally introduced by #4954 and change back the key generation to be binary, or do we keep the new behaviour?

@bkchr
Copy link
Member

bkchr commented Sep 11, 2020

I would keep the hex format, this is better human readable.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
J2-unconfirmed Issue might be valid, but it’s not yet known.
Projects
None yet
Development

No branches or pull requests

3 participants