Update specs/networking/node-identification.md
Co-Authored-By: mslipper <me@matthewslipper.com>
This commit is contained in:
parent
5a9ef0fd98
commit
22e6212e6f
|
@ -23,7 +23,7 @@ It is RECOMMENDED that clients set their TCP port to the default of `9000`.
|
||||||
|
|
||||||
## Peer ID Generation
|
## Peer ID Generation
|
||||||
|
|
||||||
The `libp2p` networking stack identifies peers via a "peer ID." Simply put, a node's Peer ID is the SHA2-256 `multihash` of the node's public key. `go-libp2p-crypto` contains the canonical implementation of how to hash `secp256k1` keys for use as a peer ID.
|
The `libp2p` networking stack identifies peers via a "peer ID." Simply put, a node's Peer ID is the SHA2-256 `multihash` of the node's public key struct (serialized in protobuf, refer to the [Peer ID spec](https://github.com/libp2p/specs/pull/100)). `go-libp2p-crypto` contains the canonical implementation of how to hash `secp256k1` keys for use as a peer ID.
|
||||||
|
|
||||||
# See Also
|
# See Also
|
||||||
|
|
||||||
|
|
Loading…
Reference in New Issue