diff options
| author | James MacWhyte <macwhyte@gmail.com> | 2016-06-21 22:50:36 +0000 |
|---|---|---|
| committer | bitcoindev <bitcoindev@gnusha.org> | 2016-06-21 22:50:47 +0000 |
| commit | 09fde6e94b7e0d0bbae4d60ce66daa95ba773492 (patch) | |
| tree | 54a49dc5a1b7b7c65ecc325530a66e2bff3fce07 /40 | |
| parent | a5ecd3f027b0fedb80b8b24151a97f8fb135b23a (diff) | |
| download | pi-bitcoindev-09fde6e94b7e0d0bbae4d60ce66daa95ba773492.tar.gz pi-bitcoindev-09fde6e94b7e0d0bbae4d60ce66daa95ba773492.zip | |
Re: [bitcoin-dev] Even more proposed BIP extensions to BIP 0070
Diffstat (limited to '40')
| -rw-r--r-- | 40/3825a55de775be600c9577c29b61a2f7f9fb45 | 121 |
1 files changed, 121 insertions, 0 deletions
diff --git a/40/3825a55de775be600c9577c29b61a2f7f9fb45 b/40/3825a55de775be600c9577c29b61a2f7f9fb45 new file mode 100644 index 000000000..d013bd3ce --- /dev/null +++ b/40/3825a55de775be600c9577c29b61a2f7f9fb45 @@ -0,0 +1,121 @@ +Return-Path: <keatonatron@gmail.com> +Received: from smtp1.linuxfoundation.org (smtp1.linux-foundation.org + [172.17.192.35]) + by mail.linuxfoundation.org (Postfix) with ESMTPS id 58D4C955 + for <bitcoin-dev@lists.linuxfoundation.org>; + Tue, 21 Jun 2016 22:50:47 +0000 (UTC) +X-Greylist: whitelisted by SQLgrey-1.7.6 +Received: from mail-qk0-f180.google.com (mail-qk0-f180.google.com + [209.85.220.180]) + by smtp1.linuxfoundation.org (Postfix) with ESMTPS id BF63619B + for <bitcoin-dev@lists.linuxfoundation.org>; + Tue, 21 Jun 2016 22:50:46 +0000 (UTC) +Received: by mail-qk0-f180.google.com with SMTP id a186so42519288qkf.0 + for <bitcoin-dev@lists.linuxfoundation.org>; + Tue, 21 Jun 2016 15:50:46 -0700 (PDT) +DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; + h=mime-version:references:in-reply-to:from:date:message-id:subject:to; + bh=zudmOPKvCKCUqYbJogfA7EcddUEWLdL06dmZNab5U0g=; + b=bTSGWD4hzTdUpr6gcxOkfLkh4DYn8vFQvSq1+FXEvqD8sVHGy69VjpXfMmGQZR5mGJ + TLbroRHgaJBa8ycATTBR0tQUIKC947oacFcPGrqCED7FYTyINH17Ui7ZgsrXbfKfXexH + Fb6PUPfQe9RIwvXsjnxN0ntDBwvpt+dODTufJv4trXV54GXzvTLq08/tisSuRBm8Hrlj + SbI6WdsqnkT3TfkD/QEMIuKUmrbveFy2FF4ztlurDadJpHBc5vb5OhmAgiVOyNaEQlIy + cCO1frAchNvqu6rNyn3/yBPXRI+Z61EFF1Qv/IhqhTvKWn1pLV37lz9PaNLPVXhdPz+b + 6PEA== +X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; + d=1e100.net; s=20130820; + h=x-gm-message-state:mime-version:references:in-reply-to:from:date + :message-id:subject:to; + bh=zudmOPKvCKCUqYbJogfA7EcddUEWLdL06dmZNab5U0g=; + b=hhGtcYB5McYgnTQP+Aq2D+yWKiltBfMXGqeBXeSylIw9jk3R7jx31bw+5RSs6Z2dNc + zJum5q0MSt3MlST7LoYwW4Hvid6SBTqghwV1qE+rcPfoFGYs6hX2xy6nLbi6ZxHeYHJ2 + vKGLtQAt+EU9LCLvWLYq3DZIkGtxlmQ5TT7+R0ggj+VmRDGQXQeDlwj6885/JlAofRWV + v2nkNPf1eh9o23hilY2pedXqyLS1WudQuy8w4+MCu2ElLC5Ou0ZP+jbG+s+u0EmAumlG + s5WVHKcY0rVbROuwOiaiUtMLcpoyUqHFhtW21ZVDLHSbK8Ea2DdN4FfZIp+IRlDtg4JT + nTsQ== +X-Gm-Message-State: ALyK8tIS6qES97vVPXUzNBPxgHWCOgon5xasiD8xquES7TH807ArmD6C46lFV+l9yzHT3vsRRdh81C7Azk/2rw== +X-Received: by 10.55.160.132 with SMTP id j126mr32244534qke.108.1466549445969; + Tue, 21 Jun 2016 15:50:45 -0700 (PDT) +MIME-Version: 1.0 +References: <CAJowKg+zYtUnHv+ea--srehVa5K46sjpWbHVcVGRY5x0w5XRTQ@mail.gmail.com> + <20160621221347.GC10196@fedora-21-dvm> +In-Reply-To: <20160621221347.GC10196@fedora-21-dvm> +From: James MacWhyte <macwhyte@gmail.com> +Date: Tue, 21 Jun 2016 22:50:36 +0000 +Message-ID: <CAH+Axy59VfuiY7jp7CVrg0umt_AZydvYV8TP_RPUtEyGME9aCw@mail.gmail.com> +To: Peter Todd <pete@petertodd.org>, + Bitcoin Protocol Discussion <bitcoin-dev@lists.linuxfoundation.org>, + Erik Aronesty <erik@q32.com> +Content-Type: multipart/alternative; boundary=001a114fca4ac5cdb60535d1a611 +X-Spam-Status: No, score=-2.7 required=5.0 tests=BAYES_00,DKIM_SIGNED, + DKIM_VALID,DKIM_VALID_AU,FREEMAIL_FROM,HTML_MESSAGE,RCVD_IN_DNSWL_LOW + autolearn=ham version=3.3.1 +X-Spam-Checker-Version: SpamAssassin 3.3.1 (2010-03-16) on + smtp1.linux-foundation.org +Subject: Re: [bitcoin-dev] Even more proposed BIP extensions to BIP 0070 +X-BeenThere: bitcoin-dev@lists.linuxfoundation.org +X-Mailman-Version: 2.1.12 +Precedence: list +List-Id: Bitcoin Protocol Discussion <bitcoin-dev.lists.linuxfoundation.org> +List-Unsubscribe: <https://lists.linuxfoundation.org/mailman/options/bitcoin-dev>, + <mailto:bitcoin-dev-request@lists.linuxfoundation.org?subject=unsubscribe> +List-Archive: <http://lists.linuxfoundation.org/pipermail/bitcoin-dev/> +List-Post: <mailto:bitcoin-dev@lists.linuxfoundation.org> +List-Help: <mailto:bitcoin-dev-request@lists.linuxfoundation.org?subject=help> +List-Subscribe: <https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev>, + <mailto:bitcoin-dev-request@lists.linuxfoundation.org?subject=subscribe> +X-List-Received-Date: Tue, 21 Jun 2016 22:50:47 -0000 + +--001a114fca4ac5cdb60535d1a611 +Content-Type: text/plain; charset=UTF-8 + +> Note that "client supplied identification" is being pushed for AML/KYC +> compliance, e.g. Netki's AML/KYC compliance product: +> +> +> http://www.coindesk.com/blockchain-identity-company-netki-launch-ssl-certificate-blockchain/ +> +> This is an extremely undesirable feature to be baking into standards given +> it's +> negative impact on fungibility and privacy; we should not be adopting +> standards +> with AML/KYC support, for much the same reasons that the W3C should not be +> standardizing DRM. +> +> +KYC isn't the only use case. There are other situations in which you would +want to confirm who is sending you money. Making it *required* would of +course be a horrible idea, but allowing people to identify themselves, in +many cases with an online-only identity that isn't tied to their real world +identity, will be very useful to newly-developing use cases. + +--001a114fca4ac5cdb60535d1a611 +Content-Type: text/html; charset=UTF-8 +Content-Transfer-Encoding: quoted-printable + +<div dir=3D"ltr"><br><div class=3D"gmail_quote"><blockquote class=3D"gmail_= +quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1= +ex">Note that "client supplied identification" is being pushed fo= +r AML/KYC<br> +compliance, e.g. Netki's AML/KYC compliance product:<br> +<br> +<a href=3D"http://www.coindesk.com/blockchain-identity-company-netki-launch= +-ssl-certificate-blockchain/" rel=3D"noreferrer" target=3D"_blank">http://w= +ww.coindesk.com/blockchain-identity-company-netki-launch-ssl-certificate-bl= +ockchain/</a><br> +<br> +This is an extremely undesirable feature to be baking into standards given = +it's<br> +negative impact on fungibility and privacy; we should not be adopting stand= +ards<br> +with AML/KYC support, for much the same reasons that the W3C should not be<= +br> +standardizing DRM.<br><br></blockquote><div><br>KYC isn't the only use = +case. There are other situations in which you would want to confirm who is = +sending you money. Making it *required* would of course be a horrible idea,= + but allowing people to identify themselves, in many cases with an online-o= +nly identity that isn't tied to their real world identity, will be very= + useful to newly-developing use cases.</div></div></div> + +--001a114fca4ac5cdb60535d1a611-- + |