From: s7r <s7r@sky-ip•org>
To: bitcoin-dev@lists•linuxfoundation.org
Subject: Re: [bitcoin-dev] BIPS proposal for implementing AML-KYC in bitcoin
Date: Thu, 27 Aug 2015 12:33:16 +0300 [thread overview]
Message-ID: <55DED95C.9090303@sky-ip.org> (raw)
In-Reply-To: <55DEC710.4090603@gmail.com>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256
Hello,
Please stop with the nonsense. Bitcoin is a decentralized payment
network. It operates globally, so neither jurisdiction can apply to it
and have effects. It is the sole responsibility of all the
users/businesses involved in Bitcoin to comply with their local
regulations while using Bitcoin. Trying to somehow standardize this
compliance at the backbone network level will be impossible in the
first place, and even if it was possible it would be a _huge_ mistake.
The word 'Bitcoin' already rings a bell in most places of the world
where there is a reasonable level of technology available. It is
powerful and we should continue the work to improve it. No law
enforcement authority or govt. branch is asking more than for
users/businesses to comply with the regulations that bind to them.
Someone in Belize for example does not have same compliance requests
with someone in Germany - which is why this is not even a subject to
be discussed on bicoin-dev mailing list. It is unique/custom for each
user/business, the requirements depending on their jurisdiction.
On 8/27/2015 11:15 AM, Patrick Strateman via bitcoin-dev wrote:
> Are you aware of the prior work in this field?
>
> https://www.reddit.com/r/Bitcoin/comments/1qmbtu/mike_hearn_chair_of_the_bitcoin_foundations_law/
>
> On 08/27/2015 01:10 AM, prabhat via bitcoin-dev 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
>>
>>
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.22 (MingW32)
iQEcBAEBCAAGBQJV3tlbAAoJEIN/pSyBJlsR438H/Aw6PCjPxLGuxdlDVmqQG4Lz
a95OVm8KqEfbiRGc1lYjBhh3JjXoUBuZKUgbnve6oFOBdNpmtm/OCJpCBQqaLDnT
Ksao1aM42c+1RdiLRhd3QjoDHyfRpNnE+XQ4lk+H0nMlroRos1K5Dpnmiea15yMQ
1mxvnKyW5mIRu11Z/6xEJ3tX8VoAk3G2MtYf0SRkfJjbdRai1JIL/4w/JJJnkS1L
klMYPQeHOolIaSgXfy/oCGgqDLVKi3utkDZuIqLe8Pg0OoQFOnn4k3vDdQ/U0N5z
r7rzvriXBlCaZttNi8MkLujP3ugcTAjLxzntS68vXIRwSy+VzrASYdDd6vXGR4U=
=61p4
-----END PGP SIGNATURE-----
next prev parent reply other threads:[~2015-08-27 9:33 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-27 8:10 prabhat
2015-08-27 8:15 ` Patrick Strateman
2015-08-27 9:33 ` s7r [this message]
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
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=55DED95C.9090303@sky-ip.org \
--to=s7r@sky-ip$(echo .)org \
--cc=bitcoin-dev@lists$(echo .)linuxfoundation.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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