public inbox for bitcoindev@googlegroups.com
 help / color / mirror / Atom feed
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 19:09:40 +0530	[thread overview]
Message-ID: <CALoZ_LF_2pbczmHm5ZGc4=ffDqTmcoAYZzkFTUUV9a05q6wTfQ@mail.gmail.com> (raw)
In-Reply-To: <CABsx9T06Pot0QqZ9bbok6_FH5kyDh+-QV=fdUGma=cmr=iESsg@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1069 bytes --]

Fine point.

So where is the solution? What to do?

Prabhat Kumar Singh

Prabhat Kumar Singh


On Thu, Aug 27, 2015 at 6:58 PM, Gavin Andresen <gavinandresen@gmail.com>
wrote:

> Have you talked with anybody at the Bitcoin Foundation about this proposal?
>
> As Chief Scientist of the Foundation, I am strongly opposed to any
> proposal that puts the Foundation in a position of centralized authority,
> so this is unacceptable: "The Bitcoin Foundation will act as fair play
> party and enforcement body to control the misuse of vast financial powers
> which bitcoin has."
>
> The idea that a central organization can be trusted to keep secrets secure
> is just fundamentally wrong. In the very recent past we have seen
> government organizations fail in that task (the NSA, the OPM) and we see
> commercial organizations that SHOULD be highly motivated to do a good job
> also fail (e.g. the Ashley Madison leak).
>
> Even if it were technically possible, I would be opposed because
> decentralization is a bedrock principle of Bitcoin.
>
> --
> --
> Gavin Andresen
>

[-- Attachment #2: Type: text/html, Size: 1802 bytes --]

  reply	other threads:[~2015-08-27 13:40 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 [this message]
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='CALoZ_LF_2pbczmHm5ZGc4=ffDqTmcoAYZzkFTUUV9a05q6wTfQ@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