diff options
| author | Jeff Garzik <jgarzik@bitpay.com> | 2015-05-07 11:17:03 -0400 |
|---|---|---|
| committer | bitcoindev <bitcoindev@gnusha.org> | 2015-05-07 15:17:30 +0000 |
| commit | efcd0aa42b087d75f3f188be1cd5a0fe93923975 (patch) | |
| tree | 7c37f0361affcdb01e25b45351c3234ad3776fab | |
| parent | 763c02059255a361823ee330ce96f7d29af20be8 (diff) | |
| download | pi-bitcoindev-efcd0aa42b087d75f3f188be1cd5a0fe93923975.tar.gz pi-bitcoindev-efcd0aa42b087d75f3f188be1cd5a0fe93923975.zip | |
Re: [Bitcoin-development] Block Size Increase
| -rw-r--r-- | b1/f5cd3b82fe05f28dd3115c86e3be46400e4802 | 134 |
1 files changed, 134 insertions, 0 deletions
diff --git a/b1/f5cd3b82fe05f28dd3115c86e3be46400e4802 b/b1/f5cd3b82fe05f28dd3115c86e3be46400e4802 new file mode 100644 index 000000000..c401cf810 --- /dev/null +++ b/b1/f5cd3b82fe05f28dd3115c86e3be46400e4802 @@ -0,0 +1,134 @@ +Received: from sog-mx-4.v43.ch3.sourceforge.com ([172.29.43.194] + helo=mx.sourceforge.net) + by sfs-ml-2.v29.ch3.sourceforge.com with esmtp (Exim 4.76) + (envelope-from <jgarzik@bitpay.com>) id 1YqNYI-0002HZ-Fk + for bitcoin-development@lists.sourceforge.net; + Thu, 07 May 2015 15:17:30 +0000 +Received-SPF: pass (sog-mx-4.v43.ch3.sourceforge.com: domain of bitpay.com + designates 209.85.214.181 as permitted sender) + client-ip=209.85.214.181; envelope-from=jgarzik@bitpay.com; + helo=mail-ob0-f181.google.com; +Received: from mail-ob0-f181.google.com ([209.85.214.181]) + by sog-mx-4.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128) + (Exim 4.76) id 1YqNYH-0000u3-GP + for bitcoin-development@lists.sourceforge.net; + Thu, 07 May 2015 15:17:30 +0000 +Received: by obblk2 with SMTP id lk2so33946771obb.0 + for <bitcoin-development@lists.sourceforge.net>; + Thu, 07 May 2015 08:17:23 -0700 (PDT) +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:from:date + :message-id:subject:to:cc:content-type; + bh=8wmaRkUhwHH4THURybnPk+z5Eq2mm9TJ2rEpJpb2QxU=; + b=RBO0IyUU2cPFhxogfGf9Mff/bVlZjprI8pMeyJPon2We9+wkAJ6rU5/6Iwu8F/Yc67 + XtZQmf2I/erArLduilzt6xQNGo+l3S8is/W934pdCNxxo5YStIFyRkH21KmzWb2TGRKs + xoAbQjSFUiW+5rTRsfv9gC0SWY/I3cu+5yUn8rfdLPMG/nTUPcYdyfMX4fB2IRafxYCa + wEvEGd6+0JN+iyEJVXPPvzCUkJj9MkAvE4sFq7YxGi90CitQhvASLUQvgXabFy0WhNhI + bR4uGr7PWqYSz9eUF9bGFHynY1rkiZ0VAS089kIPesY4v7shfpOTLA7mRqqPyKCph5cl + ZTrA== +X-Gm-Message-State: ALoCoQkeMbWyrUrknaMN65EA6diC85RiM0KqwU9gmDSKKsvWFann1K3sduge/f3XUV2R060Ik+Lb +X-Received: by 10.182.230.104 with SMTP id sx8mr3652010obc.61.1431011843682; + Thu, 07 May 2015 08:17:23 -0700 (PDT) +MIME-Version: 1.0 +Received: by 10.202.108.149 with HTTP; Thu, 7 May 2015 08:17:03 -0700 (PDT) +In-Reply-To: <CANEZrP1tCda9EbYgYu5QHN8ZgBCtGP7zRiDaXnq-rWU0ZHR9NQ@mail.gmail.com> +References: <554A91BE.6060105@bluematt.me> + <CANEZrP3wGWHdz+ut6pvke5TJJsc1rTFt8sn2KziX35oL5LAsyg@mail.gmail.com> + <CABm2gDpDvk2VsQ+mJ-BoeBKmvu9jBXNujZEFKuCStRNjFL6VOA@mail.gmail.com> + <CANEZrP2zAGCCBhNa4=9yw+A_Dn5o4SQXoPTE_qcJzZ1dFuF2tw@mail.gmail.com> + <CABm2gDqd6iHRUDKZWWTudcC1QkYa+rCuHjz7pMC2K1Db8wpgfA@mail.gmail.com> + <CANEZrP1CU0kB0vXeXUX1L8byaT-Zf2xg+3N+GeNthi_i6bn1qw@mail.gmail.com> + <CABsx9T2Nxvr4fqREMw3_LXftzsxrUAR1+9sVMa8_EpTnH1nN1Q@mail.gmail.com> + <CAPWm=eUFe7dKJCLeNACZ4n9vw0Xj9rHVM_RRLSczGXNU-ShR2w@mail.gmail.com> + <CANEZrP1tCda9EbYgYu5QHN8ZgBCtGP7zRiDaXnq-rWU0ZHR9NQ@mail.gmail.com> +From: Jeff Garzik <jgarzik@bitpay.com> +Date: Thu, 7 May 2015 11:17:03 -0400 +Message-ID: <CAJHLa0Nrp4QEQqrBu6Tb+dohxX2VhWKMnO40xscZF1OJdfPF-A@mail.gmail.com> +To: Mike Hearn <mike@plan99.net> +Content-Type: multipart/alternative; boundary=001a1134be5e9cc58605157f6863 +X-Spam-Score: -0.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 SPF_PASS SPF: sender matches SPF record + 1.0 HTML_MESSAGE BODY: HTML included in message + -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: 1YqNYH-0000u3-GP +Cc: Bitcoin Dev <bitcoin-development@lists.sourceforge.net> +Subject: Re: [Bitcoin-development] Block Size Increase +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: Thu, 07 May 2015 15:17:30 -0000 + +--001a1134be5e9cc58605157f6863 +Content-Type: text/plain; charset=UTF-8 + +On Thu, May 7, 2015 at 11:12 AM, Mike Hearn <mike@plan99.net> wrote: + +> +> That's why I conclude the opposite - if there is no fork, then people's +> confidence in Bitcoin will be seriously damaged. +> + +Yes, that is a possibility. + + + +> If it's impossible to do something as trivial as removing a temporary hack +> Satoshi put in place, then what about bigger challenges? +> + +This is absolutely not a trivial change. + +It is a trivial *code* change. It is not a trivial change to the economics +of a $3.2B system. + +-- +Jeff Garzik +Bitcoin core developer and open source evangelist +BitPay, Inc. https://bitpay.com/ + +--001a1134be5e9cc58605157f6863 +Content-Type: text/html; charset=UTF-8 +Content-Transfer-Encoding: quoted-printable + +<div dir=3D"ltr"><div class=3D"gmail_extra"><div class=3D"gmail_quote">On T= +hu, May 7, 2015 at 11:12 AM, Mike Hearn <span dir=3D"ltr"><<a href=3D"ma= +ilto:mike@plan99.net" target=3D"_blank">mike@plan99.net</a>></span> wrot= +e:<br><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-l= +eft:1px #ccc solid;padding-left:1ex"><div dir=3D"ltr"><div class=3D"gmail_e= +xtra"><br><div class=3D"gmail_quote"><span class=3D""></span>That's why= + I conclude the opposite - if there is no fork, then people's confidenc= +e in Bitcoin will be seriously damaged.</div></div></div></blockquote><div>= +<br></div><div>Yes, that is a possibility.<br></div><div><br>=C2=A0</div><b= +lockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px = +#ccc solid;padding-left:1ex"><div dir=3D"ltr"><div class=3D"gmail_extra"><d= +iv class=3D"gmail_quote">If it's impossible to do something as trivial = +as removing a temporary hack Satoshi put in place, then what about bigger c= +hallenges?</div></div></div></blockquote><div><br></div><div>This is absolu= +tely not a trivial change.<br><br></div><div>It is a trivial <i>code</i> ch= +ange.=C2=A0 It is not a trivial change to the economics of a $3.2B system.<= +br clear=3D"all"></div></div><br>-- <br><div class=3D"gmail_signature">Jeff= + Garzik<br>Bitcoin core developer and open source evangelist<br>BitPay, Inc= +. =C2=A0 =C2=A0 =C2=A0<a href=3D"https://bitpay.com/" target=3D"_blank">htt= +ps://bitpay.com/</a></div> +</div></div> + +--001a1134be5e9cc58605157f6863-- + + |