From: Ahmed Zsales <ahmedzsales18@gmail.com>
To: prabhat <prabhatkr@gmail.com>,
Bitcoin Dev <bitcoin-dev@lists.linuxfoundation.org>
Subject: Re: [bitcoin-dev] BIPS proposal for implementing AML-KYC in bitcoin
Date: Thu, 27 Aug 2015 10:04:33 +0100 [thread overview]
Message-ID: <CADr=VrT9BBR_CGhr0ODvggtJx7tXW=uMky+S9UXgrXS3CmHHyw@mail.gmail.com> (raw)
In-Reply-To: <CALoZ_LG7POrwNqtG9prvG_1T3+OcWNo9cKbiwHDu9xP85zqOEA@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 2440 bytes --]
I would prefer not to download an attachment.
Generally and without having the benefit of reading your document, AML and
or KYC requirements are treated on a jurisdiction by jurisdiction basis.
You would probably need to factor obtaining a universal agreement between
all of the governments and regional enforcement bodies of the world on the
nature and scope of an acceptable set of policies before attempting to
attach rules to the protocol. Clearly, when one country unilaterally places
politicians of another country on banned lists and vice versa, for example,
would create some problems with implementation and automating checks
against banned lists produced by each country.
While you could apply a 'home rule' approach, you would be pushing
regulatory controls down to individuals transacting between each other
without having to go through any regulated intermediaries. This means you
have no way to enforce KYC or verify that the details are correct unless
you create a system of third party checkers in each country who would
enable transactions to proceed. To overcome all of this you would probably
need some identity verification system in place first and to add extra fees
into the network to pay for the maintenance of the system.
As has already been pointed out, the above would lead to individual coins
being tainted with previous ownership details creating the possibility for
blacklists rendering some coins worthless and creating the possibility of
these coins being passed on to unsuspecting users. All this goes against
the spirit of monetary systems, so you are back to regulating end points as
and when users come into contact with regulated entities.
Lastly, it might be worth knowing that criminal liability can be placed on
individuals responsible for implementing AML and KYC procedures and
policies that do not work or allow criminals to circumvent the systems of
controls.
On Thu, Aug 27, 2015 at 9:10 AM, prabhat via bitcoin-dev <
bitcoin-dev@lists.linuxfoundation.org> 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
>
>
[-- Attachment #2: Type: text/html, Size: 3617 bytes --]
next prev parent reply other threads:[~2015-08-27 9:04 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-27 8:10 [bitcoin-dev] BIPS proposal for implementing AML-KYC in bitcoin prabhat
2015-08-27 8:15 ` Patrick Strateman
2015-08-27 9:33 ` s7r
2015-08-27 9:04 ` Ahmed Zsales [this message]
[not found] ` <CAC0TF==iEPzMpjcGO+ukV6rVkM-4yH3jX0Obu4Aint1eWzK5bQ@mail.gmail.com>
2015-08-27 12:06 ` prabhat
2015-08-27 12:14 ` jl2012
2015-08-27 12:19 ` prabhat
2015-08-27 13:28 ` Gavin Andresen
2015-08-27 13:39 ` prabhat
2015-08-27 13:48 ` Gavin Andresen
2015-08-27 16:06 ` Milly Bitcoin
2015-08-27 17:33 ` prabhat
2015-08-27 18:55 ` Oliver Petruzel
2015-08-27 18:56 ` prabhat
2015-08-27 19:42 ` Dave Scotese
2015-08-27 14:02 ` Chris Pacia
2015-08-27 16:02 ` Sergio Demian Lerner
2015-08-28 2:09 ` odinn
2015-08-28 2:00 ` odinn
2015-08-28 2:17 ` Yifu Guo
2015-08-30 12:47 ` s7r
2015-08-30 15:16 ` Vinyas
2015-08-30 15:56 ` [bitcoin-dev] [META] Mailing list etiquette " jl2012
2015-08-31 11:28 ` [bitcoin-dev] " prabhat
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CADr=VrT9BBR_CGhr0ODvggtJx7tXW=uMky+S9UXgrXS3CmHHyw@mail.gmail.com' \
--to=ahmedzsales18@gmail.com \
--cc=bitcoin-dev@lists.linuxfoundation.org \
--cc=prabhatkr@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox