btcutil VS keripy

Your IDs are []byte of len=11. Those bytes can be represented in many ways.

You can represent them as hex strings via encoding/hex.EncodeToString(id), or base64 strings via encoding/base64.StdEncoding.EncodeToString(id), or base32 strings via encoding/base32.StdEncoding.EncodeToString(id), or etc.

Looks like the most used base58 package is https://pkg.go.dev/github.com/btcsuite/btcutil/base58, but looking at the implementation [0] I'm not impressed, and confident there's a better implementation

[0] https://github.com/btcsuite/btcutil/blob/v1.0.2/base58/base5...

But how you encode 11 bytes of data is kind of orthogonal to the important thing, which is that you have 11 bytes of data. They should be always be store in memory (in your application, or a DB, or anything else) as the actual 11 bytes of the ID, and not as a base58 or base64 or JSON or whatever other kind of string that can be decoded to the actual 11 bytes of data.

Likewise, a UUID shouldn't be stored as a string like "64d3f2e0-a4dc-48d3-98ad-7f09eb3b082f", that's a specific encoding of the actual 16 UUID bytes, you should store, process, etc. those bytes directly.

Golang: https://github.com/btcsuite/btcutil