From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from smtp1.linuxfoundation.org (smtp1.linux-foundation.org [172.17.192.35]) by mail.linuxfoundation.org (Postfix) with ESMTPS id AF64CDA4 for ; Sun, 7 Feb 2016 05:21:06 +0000 (UTC) X-Greylist: whitelisted by SQLgrey-1.7.6 Received: from mail-lb0-f175.google.com (mail-lb0-f175.google.com [209.85.217.175]) by smtp1.linuxfoundation.org (Postfix) with ESMTPS id 9FA4D112 for ; Sun, 7 Feb 2016 05:21:05 +0000 (UTC) Received: by mail-lb0-f175.google.com with SMTP id bc4so68331311lbc.2 for ; Sat, 06 Feb 2016 21:21:05 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=6UG+dzu4Uaup9n9XpSMVWyIDBG4v76nMzqE34tRnABQ=; b=YaUkAqrKQO/6SwXBVgCMZZBTmgxVm2LRtW2w8/2c7gp/38De6u+pjuOYeGKwRR2lE6 voXhxpCP333d7AkRAwWytQsHMy1Aa1IQciYsyo4sbthulycYWVzGk7t1lRUO+FRi1/ai IwlkSfOUZdRi2BvLbWw2LeDiQhvb0QlfDff2thJy/BCfaTlC4Oyj0SVqFIGJF8n3rsLS HQ8Rs3PFuOvoo3rCLpVjhvF3uY8g/JqWlHLn13cBZHpIEG3sDrjzV7rTXI3dDsFs3zMx Xu/k8OMFBkMP/4Iuxh9KfEeErZ/w0t1SxnDx7CHmPnlqYA9+YSE8HyLA1hPUVITsE3c2 x5Fw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc:content-type; bh=6UG+dzu4Uaup9n9XpSMVWyIDBG4v76nMzqE34tRnABQ=; b=EDHXrqLswnOZiodbMbvz5loDJn+ysdGRXOZAaoXbHUBePC0ToXGiuabxk090YDjtOA PoaP11+WRo8QE/OVyj5Pa9ft7AEtfTXttqeCW6ytFLfARMYF8r7+HQCWnSYg248hS7fn fpOcnBO3ZX2mYA+qgp3Dos0nPSENWWiS59Iim5rgCLLNahqehkXRaTAGMjSJKDwH8kaC AtNoUJWBh0mFONzXg9P4NO/RqFVvgBJ8LshtL15vUtW0tX9EOrQUJfIqYp9PBeYgto4s 25XjEqQPbHcN76nt85ccc0C4vXR4WDb6pAS3m8cfOic9obEshbXdxfpkaA6WSe7U8Lmr AY+w== X-Gm-Message-State: AG10YOSqO8RvFfc50Wj8037JuF6dgnskdH7Ldg5FBm/HoqR4Uq+g4a3DgundU4Syw5CpWg== X-Received: by 10.112.201.67 with SMTP id jy3mr9087452lbc.25.1454822463418; Sat, 06 Feb 2016 21:21:03 -0800 (PST) Received: from mail-lb0-f173.google.com (mail-lb0-f173.google.com. [209.85.217.173]) by smtp.gmail.com with ESMTPSA id xe8sm3166908lbb.41.2016.02.06.21.21.01 for (version=TLSv1/SSLv3 cipher=OTHER); Sat, 06 Feb 2016 21:21:02 -0800 (PST) Received: by mail-lb0-f173.google.com with SMTP id cw1so68327202lbb.1 for ; Sat, 06 Feb 2016 21:21:01 -0800 (PST) MIME-Version: 1.0 X-Received: by 10.112.132.6 with SMTP id oq6mr7426150lbb.38.1454822461676; Sat, 06 Feb 2016 21:21:01 -0800 (PST) Received: by 10.112.181.164 with HTTP; Sat, 6 Feb 2016 21:21:00 -0800 (PST) Received: by 10.112.181.164 with HTTP; Sat, 6 Feb 2016 21:21:00 -0800 (PST) In-Reply-To: References: <201602060012.26728.luke@dashjr.org> Date: Sun, 7 Feb 2016 06:21:00 +0100 X-Gmail-Original-Message-ID: Message-ID: From: Jannes Faber To: Gavin Andresen Content-Type: multipart/alternative; boundary=047d7b3a825c0a4558052b274077 X-Spam-Status: No, score=-2.7 required=5.0 tests=BAYES_00,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,FREEMAIL_FROM,HTML_MESSAGE,RCVD_IN_DNSWL_LOW autolearn=ham version=3.3.1 X-Spam-Checker-Version: SpamAssassin 3.3.1 (2010-03-16) on smtp1.linux-foundation.org X-Mailman-Approved-At: Sun, 07 Feb 2016 14:45:06 +0000 Cc: Bitcoin Dev Subject: Re: [bitcoin-dev] BIP proposal: Increase block size limit to 2 megabytes X-BeenThere: bitcoin-dev@lists.linuxfoundation.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: Bitcoin Development Discussion List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 07 Feb 2016 05:21:06 -0000 --047d7b3a825c0a4558052b274077 Content-Type: text/plain; charset=UTF-8 On 6 Feb 2016 4:41 p.m., "Gavin Andresen via bitcoin-dev" < bitcoin-dev@lists.linuxfoundation.org> wrote: > > Responding to "28 days is not long enough" : > > I keep seeing this claim made with no evidence to back it up. As I said, I surveyed several of the biggest infrastructure providers and the btcd lead developer and they all agree "28 days is plenty of time." 28 days doesn't sound like enough for exchanges and others holding 3rd party coins. They will have to start untangling the Bitcoins from classiccoins immediately, while pausing all withdrawals. They *must* be able to send their customers both coins as separate withdrawals. If not, that amounts to theft of their customers funds. (Note that the above describes the honest exchanges. Imagine the dishonest ones that simply steal the classiccoins from their customers and sell them for their own profit.) The only other option is guaranteeing customers both coins in one transaction, which they can't. Surely you can't expect small entities to start putting in massive man hours into this even before the hard fork has been triggered? Or even big entities to have all that implemented and tested within *20* working days? -- Jannes --047d7b3a825c0a4558052b274077 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable


On 6 Feb 2016 4:41 p.m., "Gavin Andresen via bitcoin-dev" <bitcoin-dev@lists.lin= uxfoundation.org> wrote:
>
> Responding to "28 days is not long enough" :
>
> I keep seeing this claim made with no evidence to back it up.=C2=A0 As= I said, I surveyed several of the biggest infrastructure providers and the= btcd lead developer and they all agree "28 days is plenty of time.&qu= ot;

28 days doesn't sound like enough for exchanges and othe= rs holding 3rd party coins. They will have to start untangling the Bitcoins= from classiccoins immediately, while pausing all withdrawals. They *must* = be able to send their customers both coins as separate withdrawals. If not,= that amounts to theft of their customers funds.

(Note that the above describes the honest exchanges. Imagine= the dishonest ones that simply steal the classiccoins from their customers= and sell them for their own profit.)

The only other option is guaranteeing customers both coins i= n one transaction, which they can't.

Surely you can't expect small entities to start putting = in massive man hours into this even before the hard fork has been triggered= ? Or even big entities to have all that implemented and tested within *20* = working days?

--
Jannes

--047d7b3a825c0a4558052b274077--