Bitcom Protocol Prefix space efficiency
Opened this issue · 0 comments
breavyn commented
Currently a base58 encoded bitcoin address is used as a protocol identifier.
For example WeatherSV uses "1LtyME6b5AnMopQrBPLk4FGN8UBuhxKqrn", a 34 byte string. In its raw form, this data requires 25 20 bytes.
Base58 Pro's - inbuilt checksum, human readable (kind of)
Base58 Con's - it's big
Is it worth switching to the raw form for efficiencies sake?