summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorsickpig <sickpig@gmail.com>2014-02-10 12:54:36 +0100
committerbitcoindev <bitcoindev@gnusha.org>2014-02-10 11:55:04 +0000
commitfa3818c8c2257a8cdf6422144aa75e6ec6d777ee (patch)
tree2ee9f43181bbd1f7be6e8b6114ca4d5e885215fc
parent4cae231e1aabad01ee22d55add45aae781e06f98 (diff)
downloadpi-bitcoindev-fa3818c8c2257a8cdf6422144aa75e6ec6d777ee.tar.gz
pi-bitcoindev-fa3818c8c2257a8cdf6422144aa75e6ec6d777ee.zip
Re: [Bitcoin-development] MtGox blames bitcoin
-rw-r--r--78/a9ab2b456c8aa35136b8bf4fa90406f911c8cf73
1 files changed, 73 insertions, 0 deletions
diff --git a/78/a9ab2b456c8aa35136b8bf4fa90406f911c8cf b/78/a9ab2b456c8aa35136b8bf4fa90406f911c8cf
new file mode 100644
index 000000000..0612a3647
--- /dev/null
+++ b/78/a9ab2b456c8aa35136b8bf4fa90406f911c8cf
@@ -0,0 +1,73 @@
+Received: from sog-mx-3.v43.ch3.sourceforge.com ([172.29.43.193]
+ helo=mx.sourceforge.net)
+ by sfs-ml-3.v29.ch3.sourceforge.com with esmtp (Exim 4.76)
+ (envelope-from <sickpig@gmail.com>) id 1WCpS4-0006JD-52
+ for bitcoin-development@lists.sourceforge.net;
+ Mon, 10 Feb 2014 11:55:04 +0000
+Received-SPF: pass (sog-mx-3.v43.ch3.sourceforge.com: domain of gmail.com
+ designates 209.85.217.181 as permitted sender)
+ client-ip=209.85.217.181; envelope-from=sickpig@gmail.com;
+ helo=mail-lb0-f181.google.com;
+Received: from mail-lb0-f181.google.com ([209.85.217.181])
+ by sog-mx-3.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128)
+ (Exim 4.76) id 1WCpS2-0001ke-W3
+ for bitcoin-development@lists.sourceforge.net;
+ Mon, 10 Feb 2014 11:55:04 +0000
+Received: by mail-lb0-f181.google.com with SMTP id z11so3615412lbi.26
+ for <bitcoin-development@lists.sourceforge.net>;
+ Mon, 10 Feb 2014 03:54:56 -0800 (PST)
+X-Received: by 10.112.74.39 with SMTP id q7mr370770lbv.64.1392033296323; Mon,
+ 10 Feb 2014 03:54:56 -0800 (PST)
+MIME-Version: 1.0
+Received: by 10.152.121.101 with HTTP; Mon, 10 Feb 2014 03:54:36 -0800 (PST)
+In-Reply-To: <CANAnSg1LgpHGf-vTV0to1Z7sogf1ic6WTbogEsrQy1wh4C5zfw@mail.gmail.com>
+References: <CANAnSg1LgpHGf-vTV0to1Z7sogf1ic6WTbogEsrQy1wh4C5zfw@mail.gmail.com>
+From: "sickpig@gmail.com" <sickpig@gmail.com>
+Date: Mon, 10 Feb 2014 12:54:36 +0100
+Message-ID: <CA+c4Zowae-YHE6yqfM_z1MUzTANBgOv=jH3ZR+EtT5Q+TWDz6Q@mail.gmail.com>
+To: Drak <drak@zikula.org>
+Content-Type: text/plain; charset=ISO-8859-1
+X-Spam-Score: -1.6 (-)
+X-Spam-Report: Spam Filtering performed by mx.sourceforge.net.
+ See http://spamassassin.org/tag/ for more details.
+ -1.5 SPF_CHECK_PASS SPF reports sender host as permitted sender for
+ sender-domain
+ 0.0 FREEMAIL_FROM Sender email is commonly abused enduser mail provider
+ (sickpig[at]gmail.com)
+ -0.0 SPF_PASS SPF: sender matches SPF record
+ -0.1 DKIM_VALID_AU Message has a valid DKIM or DK signature from
+ author's domain
+ 0.1 DKIM_SIGNED Message has a DKIM or DK signature,
+ not necessarily valid
+ -0.1 DKIM_VALID Message has at least one valid DKIM or DK signature
+X-Headers-End: 1WCpS2-0001ke-W3
+Cc: Bitcoin Dev <bitcoin-development@lists.sourceforge.net>
+Subject: Re: [Bitcoin-development] MtGox blames bitcoin
+X-BeenThere: bitcoin-development@lists.sourceforge.net
+X-Mailman-Version: 2.1.9
+Precedence: list
+List-Id: <bitcoin-development.lists.sourceforge.net>
+List-Unsubscribe: <https://lists.sourceforge.net/lists/listinfo/bitcoin-development>,
+ <mailto:bitcoin-development-request@lists.sourceforge.net?subject=unsubscribe>
+List-Archive: <http://sourceforge.net/mailarchive/forum.php?forum_name=bitcoin-development>
+List-Post: <mailto:bitcoin-development@lists.sourceforge.net>
+List-Help: <mailto:bitcoin-development-request@lists.sourceforge.net?subject=help>
+List-Subscribe: <https://lists.sourceforge.net/lists/listinfo/bitcoin-development>,
+ <mailto:bitcoin-development-request@lists.sourceforge.net?subject=subscribe>
+X-List-Received-Date: Mon, 10 Feb 2014 11:55:04 -0000
+
+Hi,
+
+On Mon, Feb 10, 2014 at 12:28 PM, Drak <drak@zikula.org> wrote:
+> What is the official response from the Bitcoin Core developers about MtGox's
+> assertion that their problems are due to a fault of bitcoin, as opposed to a
+> fault of their own?
+>
+> The technical analysis preluding this mess, was that MtGox was at fault for
+> their faulty wallet implementation.
+
+this seems a fair explanation of what happened:
+
+http://www.reddit.com/r/Bitcoin/comments/1x93tf/some_irc_chatter_about_what_is_going_on_at_mtgox/cf99yac
+
+