Received-SPF: pass (sog-mx-1.v43.ch3.sourceforge.com: domain of petertodd.org
	designates 62.13.148.99 as permitted sender)
	client-ip=62.13.148.99; envelope-from=pete@petertodd.org;
	helo=outmail148099.authsmtp.net; 
Date: Tue, 17 Jun 2014 03:23:51 -0400
From: Peter Todd <pete@petertodd.org>
To: Bitcoin-development@lists.sourceforge.net
Message-ID: <20140617072351.GA7205@savin>
MIME-Version: 1.0
Content-Type: multipart/signed; micalg=pgp-sha256;
	protocol="application/pgp-signature"; boundary="YZ5djTAD1cGYuMQK"
Content-Disposition: inline
User-Agent: Mutt/1.5.21 (2010-09-15)
Subject: [Bitcoin-development] Proposal: allocate 8 service bits for
	experimental use
Precedence: list


--YZ5djTAD1cGYuMQK
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

For my replace-by-fee implementation(1) I used service bit 26 to let
preferential peering work so that replace-by-fee nodes could easily find
each other. Of course, that's a temporary/experimental usage that can be
dropped after wider adoption, so I included the following comment:

    // Reserve 24-31 for temporary experiments
    NODE_REPLACE_BY_FEE =3D (1 << 26)

Service bits are never a guaranteed thing anyway, so occasional
collisions can and should be tolerated by applications using these
experimental service bits.


Alternately Wladimir J. van der Laan brought up elsewhere(2) the
possibility for a wider notion of an extension namespace. I'm personally
not convinced of the short-term need - we've got 64 service bits yet
NODE_BLOOM is the first fully fleshed out proposal to use one - but it's
worth thinking about for the long term.

1) https://github.com/petertodd/bitcoin/tree/replace-by-fee-v0.9.1
2) https://github.com/bitcoin/bitcoin/pull/4351#issuecomment-46272958

--=20
'peter'[:-1]@petertodd.org
000000000000000058ca7ee3a40438ea5a96e499910638352468c6d69abdb226

--YZ5djTAD1cGYuMQK
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: Digital signature

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.14 (GNU/Linux)

iQGrBAEBCACVBQJTn+0EXhSAAAAAABUAQGJsb2NraGFzaEBiaXRjb2luLm9yZzAw
MDAwMDAwMDAwMDAwMDA1OGNhN2VlM2E0MDQzOGVhNWE5NmU0OTk5MTA2MzgzNTI0
NjhjNmQ2OWFiZGIyMjYvFIAAAAAAFQARcGthLWFkZHJlc3NAZ251cGcub3JncGV0
ZUBwZXRlcnRvZC5vcmcACgkQJIFAPaXwkfu8lgf/eNA3o7PHVKRoKxSLNPTTP9cm
PW9BrbRuDFwkHAtpZHF/ynFauKJA3KPiY6B9txiaPyoofXEa+G5qar4Q3VmUtECD
DHc9yUKx6U+sMhQFMc+l4/IV8bKELvlR7+3S0O045wuFkdmkgGXs+30+1b33fp7a
hmC15AyWlaCkRyfqUh7yINm3CjLej1xrKYeHj50MaWbelRrJ8qxU7KUF29LT66vD
bPUP+Orvx2/qqV7Hzhjd8xDkxBW45VdGH/kKIq7YqCpleFVGkDHwhkTNjdDZOHpV
VAX8IdFDBwkBlTJlNKR9ulgJ43FdVKYMd+KekhMWTDuelchZb7YQ9WAvECI3cw==
=1z8P
-----END PGP SIGNATURE-----

--YZ5djTAD1cGYuMQK--