From: prabhat <prabhatkr@gmail.com>
To: Gavin Andresen <gavinandresen@gmail.com>
Cc: Bitcoin Dev <bitcoin-dev@lists.linuxfoundation.org>
Subject: Re: [bitcoin-dev] BIPS proposal for implementing AML-KYC in bitcoin
Date: Thu, 27 Aug 2015 23:03:19 +0530 [thread overview]
Message-ID: <CALoZ_LGt68K+rqSzP1_ge+-pkn6wxhdpHHDs8pris6_pQQHR7g@mail.gmail.com> (raw)
In-Reply-To: <CABsx9T0BCkYqN2s0t0wvAFVOfXWiUb-zUL0FseN4yDp5CjtD3g@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1702 bytes --]
So you mean that,
1. Govt agencies already know about everything and anything this subject
is about, but passively.
2. Due to passive nature, the actions are post incident and not pre. So
there is a risk of many ticking time-bombs which some JB (Jack Bauer or
James Bond or Jai Singh Rathore) would diffuse. Sorry for being dramatic,
the purpose is to make the point, and nothing else.
3. The subjected proposal doesn't breach the decentralisation, but just
not like swiss democracy.
I am not a legal expert, but know this much that there are 2 kinds of
crimes, one against liberty and other against life. Most of online privacy
advocacy is for liberty. But money is attached to life and not liberty. So
this has to change. It means life for many and many depend on it.
And the appeal is, Let us get active.
PS: I do not own much of bitcoins to be an advocate, but many others do and
any mayhem would affect me somehow, even if in farthest of world.
Best,
Prabhat Kumar Singh
On Thu, Aug 27, 2015 at 7:18 PM, Gavin Andresen <gavinandresen@gmail.com>
wrote:
> On Thu, Aug 27, 2015 at 9:39 AM, prabhat <prabhatkr@gmail.com> wrote:
>
>> So where is the solution? What to do?
>>
>
> This is a development list; organizations like https://coincenter.org/
> work on high-level policy issues.
>
> Last I heard, competent law enforcement organizations said they were
> perfectly capable of tracking down criminals using Bitcoin using
> traditional investigative techniques (like infiltrating criminal
> organizations or setting up honeypots). Given how many "dark markets" have
> either disappeared or been taken down, it seems they are correct.
>
> --
> --
> Gavin Andresen
>
[-- Attachment #2: Type: text/html, Size: 2810 bytes --]
next prev parent reply other threads:[~2015-08-27 17:33 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
2015-08-27 17:33 ` prabhat [this message]
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=CALoZ_LGt68K+rqSzP1_ge+-pkn6wxhdpHHDs8pris6_pQQHR7g@mail.gmail.com \
--to=prabhatkr@gmail.com \
--cc=bitcoin-dev@lists.linuxfoundation.org \
--cc=gavinandresen@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