Return-Path: Received: from smtp1.linuxfoundation.org (smtp1.linux-foundation.org [172.17.192.35]) by mail.linuxfoundation.org (Postfix) with ESMTPS id A8A4B83D for ; Sun, 28 Jun 2015 10:29:30 +0000 (UTC) X-Greylist: whitelisted by SQLgrey-1.7.6 Received: from mail-ob0-f170.google.com (mail-ob0-f170.google.com [209.85.214.170]) by smtp1.linuxfoundation.org (Postfix) with ESMTPS id 4B543139 for ; Sun, 28 Jun 2015 10:29:30 +0000 (UTC) Received: by obpn3 with SMTP id n3so89309171obp.0 for ; Sun, 28 Jun 2015 03:29:29 -0700 (PDT) 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=p3X8NvsH/Eir0Eq/LHDmUVtxchz38ubv4H+E+LDIbDU=; b=lQeSp1jvjc0eEu6oxOj1GqnMKRFQfemvEo5WaJJbbNF9gamMMirc55gjNDMq/OnDn1 JQq9k7ow7D1ymJSx97AmjL4KU1aMR3nJT/BNPIR/RRtwaj+wBhBTRJE/9oMETDW8Iqf6 nXkkILN3ZeS5I+27RB0ONxIwawvrl4VD72Vix9YH3EFLH4wXxbd1UpwUlWKkL/Pxp9F7 1lxcYdpvsKFw+e64/TPcSE2cEeNInZ4PyltQnhngVUrqB8qbQsJ1/2dFXFY+uB4QdFrd Kevcr+LNN3L1cVLB23z9sVVILjRitc58OfUbjZXWquQH/50GxeRt2klaU5woLHW5ml0I cJ+g== MIME-Version: 1.0 X-Received: by 10.60.37.166 with SMTP id z6mr9002938oej.63.1435487369743; Sun, 28 Jun 2015 03:29:29 -0700 (PDT) Received: by 10.202.87.197 with HTTP; Sun, 28 Jun 2015 03:29:29 -0700 (PDT) In-Reply-To: References: Date: Sun, 28 Jun 2015 12:29:29 +0200 Message-ID: From: Benjamin To: Adam Back Content-Type: multipart/alternative; boundary=089e013c6856c0d515051991727d 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 Cc: bitcoin-dev@lists.linuxfoundation.org Subject: Re: [bitcoin-dev] A Proposed Compromise to the Block Size Limit 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, 28 Jun 2015 10:29:30 -0000 --089e013c6856c0d515051991727d Content-Type: text/plain; charset=UTF-8 I agree that naive scaling will likely lead to bad outcomes. They might have the advantage though, as this would mean not changing Bitcoin. Level2 and Lightning is not well defined. If you move money to a third party, even if it is within the constrained of a locked contract, then I don't think that will solve the issues. Blockchain does not know about offchain and moving between offchain and onchain requires liquidity and a pricing mechanism. That is exactly the problem with side-chains. If you have off-chain transactions on an exchange, they are ID'ed in their system, subject to KYC/AML. --089e013c6856c0d515051991727d Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
I agree that naive scaling will likely lead to bad outcome= s. They might have the advantage though, as this would mean not changing Bi= tcoin.=C2=A0

Level2 and Lightning is not well defined. If you move money to a third par= ty, even if it is within the constrained of a locked contract, then I don&#= 39;t think that will solve the issues. Blockchain does not know about offch= ain and moving between offchain and onchain requires liquidity and a pricin= g mechanism. That is exactly the problem with side-chains. If you have off-= chain transactions on an exchange, they are ID'ed in their system, subj= ect to KYC/AML.
--089e013c6856c0d515051991727d--