From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from smtp1.linuxfoundation.org (smtp1.linux-foundation.org [172.17.192.35]) by mail.linuxfoundation.org (Postfix) with ESMTPS id 86101F9D for ; Fri, 28 Aug 2015 02:18:10 +0000 (UTC) X-Greylist: whitelisted by SQLgrey-1.7.6 Received: from mail-oi0-f69.google.com (mail-oi0-f69.google.com [209.85.218.69]) by smtp1.linuxfoundation.org (Postfix) with ESMTPS id 874BFF2 for ; Fri, 28 Aug 2015 02:18:09 +0000 (UTC) Received: by oibi18 with SMTP id i18so47360238oib.0 for ; Thu, 27 Aug 2015 19:18:09 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=coinapex.com; s=google; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type; bh=h1OscmiEWyQV0q2Zy1SvtnDX+Ffjzzk1VlxRtPEXjYc=; b=QjPKJ9mhLY3+SwNrgw1ax5/MKPlbhC98o2CkbfHq9vLBOnVJl8AGDnGGYvQw24Q0l6 lmsgunqbt0hjzRov1Lj4oyrxWDI9oD3ERdQXI2NvtQC009PzmCMQtowzNLQxg/4EDHCw fI5X2vfS4PHoMYXpNQFIsPGqGtyWI4mmHAz4o= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc:content-type; bh=h1OscmiEWyQV0q2Zy1SvtnDX+Ffjzzk1VlxRtPEXjYc=; b=IkCxPpbXPrbJln1SLz5R+FOjRgfWWIF6saRGa6uBRBvr+MwFHOmuHwYf+LF/ifBcy0 HTE7a6rOV9QljXs8PIRzknJ/9Ri82A6QZ3KoBY5BHvXGrftN/0+ECZkC8DaS1L+0DMDO V27G8ieskpzywJYE2VE64SBEIjnFSzcE5ZI471+7hkB5i5qWilx2PY1XsICZw3lgQsmM TmH6+9msRgWlx4GG8gW4QakytNMTm5eRLKKAj4M5sQ2RyH4VfgRsDPUA1Cs44FZhdtlj ojQ2K3eICRDM3ocDrcf7keDlXuY8MoRW/6uQpGSoKZk860IuHSWJHuya0CSKsMljskmy x3DA== X-Gm-Message-State: ALoCoQmksczQRYngTiPUj2PAs78Ey9xmswHwE5+y8Jm6LINcVw+KvUTd3EmKJ4Icfkjx2/FxmzsN X-Received: by 10.202.102.24 with SMTP id a24mr4329727oic.62.1440728288848; Thu, 27 Aug 2015 19:18:08 -0700 (PDT) MIME-Version: 1.0 Received: by 10.202.84.69 with HTTP; Thu, 27 Aug 2015 19:17:29 -0700 (PDT) In-Reply-To: <55DFC0C6.80607@riseup.net> References: <55DFC0C6.80607@riseup.net> From: Yifu Guo Date: Thu, 27 Aug 2015 22:17:29 -0400 Message-ID: To: odinn Content-Type: multipart/alternative; boundary=001a11409626e003c3051e55b124 X-Spam-Status: No, score=-2.7 required=5.0 tests=BAYES_00,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,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 Cc: prabhat , bitcoin-dev Subject: Re: [bitcoin-dev] BIPS proposal for implementing AML-KYC in bitcoin X-BeenThere: bitcoin-dev@lists.linuxfoundation.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: Bitcoin Development Discussion List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 28 Aug 2015 02:18:10 -0000 --001a11409626e003c3051e55b124 Content-Type: text/plain; charset=UTF-8 I've done some work in this area. see http://coinvalidation.com/ it's currently shelved due to lack of legal and regulatory framework. 1. this should not be directly implemented on the protocol level. I believe its Jeff Garzik who once said "stolen bitcoins is a legal problem, not a technical one." Legal problems are not technical problems. 2. it is the responsibility of company and individuals to answer questions. example, stolen bitcoins gets send to address X, and address X is a payment address of company Y. it is company Y's responsibility to answer to corresponding agencies responsible. What actions comes out of that is yet to be determent. other examples such as, you are using a wallet app, and sending bitcoin payments to a known malicious address. ( e.g. crypto-locker or other malware address that replaces the output address.), does the wallet app warn its users? Again, while these are not technical problems, they will need answers eventually. I'll be happy to discuss further off this mailing list as it is off-topic. On Thu, Aug 27, 2015 at 10:00 PM, odinn via bitcoin-dev < bitcoin-dev@lists.linuxfoundation.org> wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > No. > > On 08/27/2015 01:10 AM, prabhat via bitcoin-dev wrote: > > Hi, > > > > I am proposing to create a AML-KYC module to control the network > > and also qualify use cases in OFAC compliant way. Here is the > > attached doc. > > > > Please provide your feedback and suggestions. > > > > Best, Prabhat Kumar Singh > > > > > > _______________________________________________ bitcoin-dev mailing > > list bitcoin-dev@lists.linuxfoundation.org > > https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev > > > > - -- > http://abis.io ~ > "a protocol concept to enable decentralization > and expansion of a giving economy, and a new social good" > https://keybase.io/odinn > -----BEGIN PGP SIGNATURE----- > Version: GnuPG v1 > > iQEcBAEBAgAGBQJV38DGAAoJEGxwq/inSG8CkYkIAJwHOnjesbq+UHogUkGJsuph > 2ipSIcBEzbeVH8fQ2sij5jKULE0n8J7K/DtfzzRJj+IiaYB1Ecjl0kLVQ0ug6T/8 > p5iuGQ2fvt1tMOy9+ptZbOZhtjUTWWSMqmFgsPkh5s/uGHeKy/jBjYsZv4FZ57Hm > DUUvGYIdaGQ2eYm4y4dLnvI0T5WFQvf0Vs4wvWZdKvD5oliSwGy4KNVIxlcGya8w > FPYaDe8q0rN5Aqp4V2jjfuF4KBC8dwHa9dyHTfSPA43I1qbcIVraSdJg1lCJ/bXh > rFz+MXcGmsxxzHMbv6C4y+YSET2TPuNUs4w6MVw2ZO0lYe1suWYeYvfccQA1+Uk= > =17NP > -----END PGP SIGNATURE----- > _______________________________________________ > bitcoin-dev mailing list > bitcoin-dev@lists.linuxfoundation.org > https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev > -- *Yifu Guo* *"Life is an everlasting self-improvement."* --001a11409626e003c3051e55b124 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
I've done some work in this area. see=C2=A0http://coinvalidation.com/ it's current= ly shelved due to lack of legal and regulatory framework.

1. this should not be directly implemented on the protocol level. I belie= ve its Jeff Garzik who once said "stolen bitcoins is a legal problem, = not a technical one." Legal problems are not technical problems.
=

2. it is the responsibility of company and individuals = to answer questions. example, stolen bitcoins gets send to address X, and a= ddress X is a payment address of company Y. it is company Y's responsib= ility to answer to corresponding agencies responsible. What actions comes o= ut of that is yet to be determent.

other examples = such as, you are using a wallet app, and sending bitcoin payments to a know= n malicious address. ( e.g. crypto-locker or other malware address that rep= laces the output address.), does the wallet app warn its users?
<= br>
Again, while these are not technical problems, they will need= answers eventually. I'll be happy to discuss further off this mailing = list as it is off-topic.

On Thu, Aug 27, 2015 at 10:00 PM, odinn via bitcoin-dev = <bitcoin-dev@lists.linuxfoundation.org> = wrote:
-----BEGIN PGP SIGNED MESSAGE-----=
Hash: SHA1

No.

On 08/27/2015 01:10 AM, prabhat via bitcoin-dev wrote:
> Hi,
>
> I am proposing to create a AML-KYC module to control the network
> and also qualify use cases in OFAC compliant way. Here is the
> attached doc.
>
> Please provide your feedback and suggestions.
>
> Best, Prabhat Kumar Singh
>
>
> _________________________________________= ______ bitcoin-dev mailing
> list bitcoin-= dev@lists.linuxfoundation.org
> https://lists.linuxfoundation.org= /mailman/listinfo/bitcoin-dev
>

- --
http://abis= .io ~
"a protocol concept to enable decentralization
and expansion of a giving economy, and a new social good"
h= ttps://keybase.io/odinn
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1

iQEcBAEBAgAGBQJV38DGAAoJEGxwq/inSG8CkYkIAJwHOnjesbq+UHogUkGJsuph
2ipSIcBEzbeVH8fQ2sij5jKULE0n8J7K/DtfzzRJj+IiaYB1Ecjl0kLVQ0ug6T/8
p5iuGQ2fvt1tMOy9+ptZbOZhtjUTWWSMqmFgsPkh5s/uGHeKy/jBjYsZv4FZ57Hm
DUUvGYIdaGQ2eYm4y4dLnvI0T5WFQvf0Vs4wvWZdKvD5oliSwGy4KNVIxlcGya8w
FPYaDe8q0rN5Aqp4V2jjfuF4KBC8dwHa9dyHTfSPA43I1qbcIVraSdJg1lCJ/bXh
rFz+MXcGmsxxzHMbv6C4y+YSET2TPuNUs4w6MVw2ZO0lYe1suWYeYvfccQA1+Uk=3D
=3D17NP
-----END PGP SIGNATURE-----
___________________________________= ____________
bitcoin-dev mailing list
bitcoin-dev@lists.= linuxfoundation.org
https://lists.linuxfoundation.org/mail= man/listinfo/bitcoin-dev



--
=
Yi= fu Guo
"Life is an everlasting self-improvement."
--001a11409626e003c3051e55b124--