blob: ff75013f773d5bb20c898bfb155073bce40cd705 (
plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
|
Return-Path: <milly@bitcoins.info>
Received: from smtp1.linuxfoundation.org (smtp1.linux-foundation.org
[172.17.192.35])
by mail.linuxfoundation.org (Postfix) with ESMTPS id 90E61CF5
for <bitcoin-dev@lists.linuxfoundation.org>;
Thu, 27 Aug 2015 16:06:23 +0000 (UTC)
X-Greylist: from auto-whitelisted by SQLgrey-1.7.6
Received: from mail.help.org (mail.help.org [70.90.2.18])
by smtp1.linuxfoundation.org (Postfix) with ESMTPS id 5224718D
for <bitcoin-dev@lists.linuxfoundation.org>;
Thu, 27 Aug 2015 16:06:13 +0000 (UTC)
Received: from [10.1.10.25] (B [10.1.10.25]) by mail.help.org with ESMTPA
; Thu, 27 Aug 2015 12:06:09 -0400
To: bitcoin-dev@lists.linuxfoundation.org
References: <CALoZ_LG7POrwNqtG9prvG_1T3+OcWNo9cKbiwHDu9xP85zqOEA@mail.gmail.com>
<CAC0TF==iEPzMpjcGO+ukV6rVkM-4yH3jX0Obu4Aint1eWzK5bQ@mail.gmail.com>
<CALoZ_LE4eWO6NaP2nR4PsRBP8p_u1uhgs1PSMo7hiVf_e2=CvA@mail.gmail.com>
<fcbeee9eacd7a58b950f965eb1450180@xbt.hk>
<CALoZ_LHU7LDywjiNX53Z=5i4fkiLbRwBpCwpzTB0beWW=UHN8w@mail.gmail.com>
<CABsx9T06Pot0QqZ9bbok6_FH5kyDh+-QV=fdUGma=cmr=iESsg@mail.gmail.com>
<CALoZ_LF_2pbczmHm5ZGc4=ffDqTmcoAYZzkFTUUV9a05q6wTfQ@mail.gmail.com>
<CABsx9T0BCkYqN2s0t0wvAFVOfXWiUb-zUL0FseN4yDp5CjtD3g@mail.gmail.com>
From: Milly Bitcoin <milly@bitcoins.info>
Message-ID: <55DF356C.7020807@bitcoins.info>
Date: Thu, 27 Aug 2015 12:06:04 -0400
User-Agent: Mozilla/5.0 (Windows NT 6.3; WOW64; rv:38.0) Gecko/20100101
Thunderbird/38.2.0
MIME-Version: 1.0
In-Reply-To: <CABsx9T0BCkYqN2s0t0wvAFVOfXWiUb-zUL0FseN4yDp5CjtD3g@mail.gmail.com>
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 7bit
X-Spam-Status: No, score=-1.9 required=5.0 tests=BAYES_00 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] 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 <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: Thu, 27 Aug 2015 16:06:23 -0000
> So where is the solution? What to do?
AML-KYC is mostly something that sits on top of the Bitcoin protocol.
Take Coinase, inc. as an example. They check bank accounts before they
open your account and they link your Bitcoin address to your account in
their database. Then they ask for an explanation of why you are using
the account. Then they track your coins to a certain extent once you
actually buy Bitcoins. None of these activities are directly involving
the protocol or would require changes to the Bitcoin system.
What you can do is develop standards for using Bitcoin and entities that
need to follow AML-KYC can choose to follow those standards if they want
when they conduct business using Bitcoin. You can add a small amount of
extraneous data to transactions that could show you followed some
AML-KYC procedure. If you did that you could have a "white list" of
complaint transactions rather than a "black list" of non-compliant
transactions as you seem to be proposing. I am not sure how you would
actually do something like that or how it would work but it is an
interesting concept (not necessarily good, but interesting).
Russ
|
