From 9bfb3704ce7a5d230989295020027c696caca5d9 Mon Sep 17 00:00:00 2001 From: Yusef Napora Date: Wed, 8 May 2019 15:03:10 -0400 Subject: [PATCH] mention we're not using multibase for peer-ids --- peer-ids/peer-ids.md | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/peer-ids/peer-ids.md b/peer-ids/peer-ids.md index 680e453fb..4030c1c40 100644 --- a/peer-ids/peer-ids.md +++ b/peer-ids/peer-ids.md @@ -81,6 +81,10 @@ This encoding is sometimes abbreviated as `base58btc`. An example of a `base58btc` encoded SHA256 peer id: `QmYyQSo1c1Ym7orWxLYvCrM2EmxFTANf8wXmmE7DWjhx5N`. +Note that some projects using libp2p will prefix "base encoded" strings with a +[multibase](https://github.com/multiformats/multibase) code that identifies the encoding base and alphabet. +Peer ids do not use multibase, and can be assumed to be encoded as `base58btc`. + ## How Keys are Encoded and Messages Signed Four key types are supported: