public inbox for bitcoindev@googlegroups.com
 help / color / mirror / Atom feed
From: Milly Bitcoin <milly@bitcoins.info>
To: bitcoin-dev@lists.linuxfoundation.org
Subject: Re: [bitcoin-dev] BIPS proposal for implementing AML-KYC in bitcoin
Date: Thu, 27 Aug 2015 12:06:04 -0400	[thread overview]
Message-ID: <55DF356C.7020807@bitcoins.info> (raw)
In-Reply-To: <CABsx9T0BCkYqN2s0t0wvAFVOfXWiUb-zUL0FseN4yDp5CjtD3g@mail.gmail.com>

>     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




  reply	other threads:[~2015-08-27 16:06 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
     [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 [this message]
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=55DF356C.7020807@bitcoins.info \
    --to=milly@bitcoins.info \
    --cc=bitcoin-dev@lists.linuxfoundation.org \
    /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