waku-org
/
nwaku
mirror of https://github.com/waku-org/nwaku.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

Use config nodekey for deterministic node id from CLI

This commit is contained in:
Oskar Thoren 2020-05-21 12:16:58 +08:00
parent 3d69658dab
commit 438f2ecab2
No known key found for this signature in database
GPG Key ID: B2ECCFD3BC2EF77E
1 changed files with 4 additions and 7 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

11
waku/node/v2/wakunode.nim
View File

@ -144,13 +144,10 @@ proc run(config: WakuNodeConf) =
hostAddress = MultiAddress.init(DefaultAddr)
# Difference between announced and host address relevant for running behind NAT, however doesn't seem like nim-libp2p supports this. GHI?
#
# TODO: Convert config.nodekey eth.key to libp2p.crypto key. Should work with Secp256k1, just need to ensure representation etc is the same. Using random now for spike.
#nodekey = config.nodekey
#keys = crypto.KeyPair(nodekey)
privKey = PrivateKey.random(Secp256k1)
keys = KeyPair(seckey: privKey, pubkey: privKey.getKey())
peerInfo = PeerInfo.init(privKey)
# NOTE: This is a privatekey
nodekey = config.nodekey
keys = KeyPair(seckey: nodekey, pubkey: nodekey.getKey())
peerInfo = PeerInfo.init(nodekey)
info "Initializing networking (host address and announced same)", address