[Bitcoin-development] Proposal: allocate 8 service bits for experimental use

Wladimir laanwj at gmail.com
Tue Jun 17 08:16:01 UTC 2014

On Tue, Jun 17, 2014 at 10:08 AM, Wladimir <laanwj at gmail.com> wrote:
> On Tue, Jun 17, 2014 at 10:02 AM, Matt Whitlock <bip at mattwhitlock.name> wrote:
>> On Tuesday, 17 June 2014, at 9:57 am, Wladimir wrote:
>>> Yes, as I said in the github topic
>>> (https://github.com/bitcoin/bitcoin/pull/4351) I suggest we adapt a
>>> string-based name space for extensions.
>> Why use textual strings? These fields are not for human consumption. Why not use UUIDs, which are fixed length and will not waste as much bandwidth in the protocol? Or if you'd prefer a hierarchical namespace, you could use OIDs, a la ASN.1.

Also it IS useful for these fields to be human readable for
statistics, peer list views and such. When encountering a new, unknown
extension when connecting to a node it's much more useful to get a
google-able string to find out what it is about, than some long
hexadecimal or dotted-number identifier.


More information about the bitcoin-dev mailing list