From: prabhat <prabhatkr@gmail.com>
To: bitcoin-dev@lists.linuxfoundation.org
Subject: [bitcoin-dev] BIPS proposal for implementing AML-KYC in bitcoin
Date: Thu, 27 Aug 2015 13:40:57 +0530 [thread overview]
Message-ID: <CALoZ_LG7POrwNqtG9prvG_1T3+OcWNo9cKbiwHDu9xP85zqOEA@mail.gmail.com> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 220 bytes --]
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
[-- Attachment #1.2: Type: text/html, Size: 817 bytes --]
[-- Attachment #2: Create AML-KYC - BIPS185.txt --]
[-- Type: text/plain, Size: 2728 bytes --]
Title: A AML KYC enforcement mechanism to regulate OFAC(and similar others) from Mining
==Abstract==
The document gives specification for dealing with mining and transactions in sactioned countries to follow OFAC regulations in Bitcoin.
==Motivation==
For so long, miners in sanctioned countries or miners with illicit motives have been able to enmasse wealth by bitcoins which might or might not have been funding wrong doings of one or many non-mainstream social activities, like terrorism, human traffiking, drugs, rights abuse and many more of similar or advance nature. It is important for bitcoin community to realise the responsibility to put a control on such elements and at the same time uphold the values of bitcoin's decentralised and democratic money system. The same applies for transactions orgininating to or from such sanctioned countries.
==Specification==
To counter this problem, an bitcoin account can be centrally created in control and/or oversight of Bitcoin Foundation which should be allowed to do 0-sum transactions with a Memo Flag of BLOCK or ALLOW. And empty memo transaction has no impact. And this should be considered in consensus protocol for transaction confirmation, to BLOCK or ALLOW transactions in an account if the immediate previous transaction is BLOCK or ALLOW in that account, respectively.
==Rationale==
The Bitcoin Foundation will act as fair play party and enforcement body to control the misuse of vast financial powers which bitcoin has. The BLOCK and ALLOW is end action of a possible upstream review process for every account on the bitcoin network. The freedom of unchecked mining, poses a certain threat today and even bigger threats in future.
Even if someone is BLOCKed due to certain clerical mistakes, the process has ALLOW functionality. And if law enforcement comes with more substantial reasons of BLOCKing an account, the same be done multiple times.
We are a world of human beings with rationale, who have abilities to talk, listen and communicate. Therefore, a human to human touch can never be negated in however powerful computerisation.
==Backward compatibility==
The new consensus protocol could seem unfavourable to some due to many reasons. After listening to all parties, even if some nodes would opt to stay in old protocol, they won't be able to join the new protocol ever. This would be a hard fork and natural cleanup of bitcoin protocol from illicit miners and users.
==Implementation==
The implementation is in progress. The detail code will be shared soon.
==Acknowledgements==
It is better to be violent, if there is violence in our hearts, than to put on the cloak of nonviolence to cover impotence.- Mahatma Gandhi
next reply other threads:[~2015-08-27 8:11 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-27 8:10 prabhat [this message]
2015-08-27 8:15 ` [bitcoin-dev] BIPS proposal for implementing AML-KYC in bitcoin 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
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_LG7POrwNqtG9prvG_1T3+OcWNo9cKbiwHDu9xP85zqOEA@mail.gmail.com \
--to=prabhatkr@gmail.com \
--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