summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorSteven Pine <steven.pine@gmail.com>2015-05-08 10:57:50 -0400
committerbitcoindev <bitcoindev@gnusha.org>2015-05-08 14:57:57 +0000
commit59bd2bc1662600a9a31dc7ea1fe616556aa36199 (patch)
treef7bfefc8dbcd10fb307cb4e5dfa5611160c9db18
parentab8aae276a10d78ab6e5a42b40057827567ae83d (diff)
downloadpi-bitcoindev-59bd2bc1662600a9a31dc7ea1fe616556aa36199.tar.gz
pi-bitcoindev-59bd2bc1662600a9a31dc7ea1fe616556aa36199.zip
Re: [Bitcoin-development] Proposed alternatives to the 20MB step function
-rw-r--r--9b/954b317941548ccdd49201b75753b9f3c8eca972
1 files changed, 72 insertions, 0 deletions
diff --git a/9b/954b317941548ccdd49201b75753b9f3c8eca9 b/9b/954b317941548ccdd49201b75753b9f3c8eca9
new file mode 100644
index 000000000..78c8ed1ab
--- /dev/null
+++ b/9b/954b317941548ccdd49201b75753b9f3c8eca9
@@ -0,0 +1,72 @@
+Received: from sog-mx-3.v43.ch3.sourceforge.com ([172.29.43.193]
+ helo=mx.sourceforge.net)
+ by sfs-ml-1.v29.ch3.sourceforge.com with esmtp (Exim 4.76)
+ (envelope-from <steven.pine@gmail.com>) id 1Yqjiv-0002DX-0z
+ for bitcoin-development@lists.sourceforge.net;
+ Fri, 08 May 2015 14:57:57 +0000
+Received-SPF: pass (sog-mx-3.v43.ch3.sourceforge.com: domain of gmail.com
+ designates 209.85.213.170 as permitted sender)
+ client-ip=209.85.213.170; envelope-from=steven.pine@gmail.com;
+ helo=mail-ig0-f170.google.com;
+Received: from mail-ig0-f170.google.com ([209.85.213.170])
+ by sog-mx-3.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128)
+ (Exim 4.76) id 1Yqjiu-0002xQ-C0
+ for bitcoin-development@lists.sourceforge.net;
+ Fri, 08 May 2015 14:57:57 +0000
+Received: by igbpi8 with SMTP id pi8so22859860igb.1
+ for <bitcoin-development@lists.sourceforge.net>;
+ Fri, 08 May 2015 07:57:51 -0700 (PDT)
+MIME-Version: 1.0
+X-Received: by 10.107.33.21 with SMTP id h21mr5511737ioh.1.1431097071141; Fri,
+ 08 May 2015 07:57:51 -0700 (PDT)
+Received: by 10.79.0.38 with HTTP; Fri, 8 May 2015 07:57:50 -0700 (PDT)
+Received: by 10.79.0.38 with HTTP; Fri, 8 May 2015 07:57:50 -0700 (PDT)
+Date: Fri, 8 May 2015 10:57:50 -0400
+Message-ID: <CAAjy6kBVgHNpqHfbngGXgxc6-6CDz6SCE=DuYLpKOyef7cBWfA@mail.gmail.com>
+From: Steven Pine <steven.pine@gmail.com>
+To: bitcoin-development@lists.sourceforge.net
+Content-Type: multipart/alternative; boundary=001a1140408c9087fa0515934094
+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 FREEMAIL_FROM Sender email is commonly abused enduser mail provider
+ (steven.pine[at]gmail.com)
+ -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: 1Yqjiu-0002xQ-C0
+Subject: Re: [Bitcoin-development] Proposed alternatives to the 20MB step
+ function
+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: Fri, 08 May 2015 14:57:57 -0000
+
+--001a1140408c9087fa0515934094
+Content-Type: text/plain; charset=UTF-8
+
+Block size scaling should be as transparent and simple as possible, like
+pegging it to total transactions per difficulty change.
+
+--001a1140408c9087fa0515934094
+Content-Type: text/html; charset=UTF-8
+
+<p dir="ltr">Block size scaling should be as transparent and simple as possible, like pegging it to total transactions per difficulty change.</p>
+
+--001a1140408c9087fa0515934094--
+
+