From: Eric Voskuil <eric@voskuil.org>
Content-Type: text/plain;
	charset=us-ascii
Content-Transfer-Encoding: quoted-printable
Mime-Version: 1.0 (1.0)
Message-Id: <1E86A00F-0609-4DBC-9543-94AE04CC13C9@voskuil.org>
Date: Tue, 28 Jun 2016 09:17:31 +0200
References: <87h9cecad5.fsf@rustcorp.com.au>
In-Reply-To: <87h9cecad5.fsf@rustcorp.com.au>
To: Bitcoin Protocol Discussion <bitcoin-dev@lists.linuxfoundation.org>
Subject: [bitcoin-dev] BIP 151
Precedence: list

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

I haven't seen much discussion here on the rationale behind BIP 151. Apologi=
es if I missed it. I'm trying to understand why libbitcoin (or any node) wou=
ld want to support it.

I understand the use, when coupled with a yet-to-be-devised identity system,=
 with Bloom filter features. Yet these features are client-server in nature.=
 Libbitcoin (for example) supports client-server features on an independent p=
ort (and implements a variant of CurveCP for encryption and identity). My co=
ncern arises with application of identity to the P2P protocol (excluding Blo=
om filter features).

It seems to me that the desire to secure against the weaknesses of BF is bei=
ng casually generalized to the P2P network. That generalization may actually=
 weaken the security of the P2P protocol. One might consider the proper reso=
lution is to move the BF features to a client-server protocol.

The BIP does not make a case for other scenarios, or contemplate the signifi=
cant problems associated with key distribution in any identity system. Given=
 that the BIP relies on identity, these considerations should be fully vette=
d before heading down another blind alley.

e
-----BEGIN PGP SIGNATURE-----
Version: oPenGP 6.0 on iOS

iQEVAwUBV3IkYjzYwH8LXOFOAQg+iggAkFShi/ibZXiVv3A3z1a1SMd+4ar0kiZk
mCkBBZaatoW8tXVZmuv5xzLnj3ali9Y4jp/3h2nUJ1B4ov2kcB0kZIKE/a1DTFwb
4X3uSzgu0lEAqSZormOvt7Op46NPn6KJ+/wTtP4lUFU72lSd7qrVKMlCVc88VE7/
pMloKSc69nAeFIkyWbOUi/zDzefu/5tarfif85jumooYjPmAwJnkgiPCqpqBbuga
5lBdS1r47KK+SaDFl6Cbn4i/c6tBPLTnu+TR7TEKOW5vwVA7eUqb6SOK7pETWJGK
0Ii4ZWYt7MOPSEda381CMjWEwtsCNp0eI4GPZAAz+jNLo4G1+PAbaw=3D=3D
=3DBalw
-----END PGP SIGNATURE-----