From: Mike Hearn <mike@plan99.net>
To: Gregory Maxwell <gmaxwell@gmail.com>
Cc: bitcoin-development@lists.sourceforge.net
Subject: Re: [Bitcoin-development] Hosting of compiled bitcoin client
Date: Mon, 15 Oct 2012 00:49:47 +0200 [thread overview]
Message-ID: <CANEZrP3L6ifvvWkZvVs-RFAEb3zNuR-E_eDBCytPgP2-0tOj6A@mail.gmail.com> (raw)
In-Reply-To: <CAAS2fgTJeTObALu2CU6A8bujM_66wuBnOywnviVTa0Qfac+MWw@mail.gmail.com>
The laws in question are OFAC sanctions:
http://en.wikipedia.org/wiki/Office_of_Foreign_Assets_Control
The specific acts that enable this are varied. In theory they apply to
any US citizen or resident. The issue is not cryptography, it's "trade
with sanctioned countries", period, where making files available to
download is considered trade.
For Bitcoin to be available in these places, the sites and download
mirrors would need to be hosted outside the USA by non-citizens. EU
sanctions are primarily financial at this time, as far as I know there
are no attempts to prevent people from serving data to Iran.
Example of places where there are no sanctions in effect: Switzerland.
Unfortunately datacenter space in Zurich is quite expensive (as is
everything here).
I would not ever describe OFAC as "effective law". The SDN list has
repeatedly been found unconstitutional, representing as it does a
complete evasion of the judicial system. If you end up on the
sanctions list no evidence is required, no process is followed and no
appeals are possible. The list itself assumes names are globally
unique.
next prev parent reply other threads:[~2012-10-14 22:49 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-14 20:52 [Bitcoin-development] Hosting of compiled bitcoin client Kyle Henderson
2012-10-14 22:02 ` Luke-Jr
2012-10-14 22:09 ` Christian Decker
2012-10-14 22:33 ` Gregory Maxwell
2012-10-14 22:49 ` Mike Hearn [this message]
2012-10-20 7:43 Mark Lister
2012-10-20 8:33 ` Wladimir
2012-10-20 14:19 ` Caleb James DeLisle
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=CANEZrP3L6ifvvWkZvVs-RFAEb3zNuR-E_eDBCytPgP2-0tOj6A@mail.gmail.com \
--to=mike@plan99.net \
--cc=bitcoin-development@lists.sourceforge.net \
--cc=gmaxwell@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