From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from sog-mx-4.v43.ch3.sourceforge.com ([172.29.43.194] helo=mx.sourceforge.net) by sfs-ml-4.v29.ch3.sourceforge.com with esmtp (Exim 4.76) (envelope-from ) id 1Yqf69-0003FJ-BK for bitcoin-development@lists.sourceforge.net; Fri, 08 May 2015 10:01:37 +0000 Received-SPF: pass (sog-mx-4.v43.ch3.sourceforge.com: domain of gmail.com designates 209.85.214.175 as permitted sender) client-ip=209.85.214.175; envelope-from=benjamin.l.cordes@gmail.com; helo=mail-ob0-f175.google.com; Received: from mail-ob0-f175.google.com ([209.85.214.175]) by sog-mx-4.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128) (Exim 4.76) id 1Yqf68-0006oY-Hm for bitcoin-development@lists.sourceforge.net; Fri, 08 May 2015 10:01:37 +0000 Received: by obbkp3 with SMTP id kp3so51664106obb.3 for ; Fri, 08 May 2015 03:01:31 -0700 (PDT) MIME-Version: 1.0 X-Received: by 10.202.232.14 with SMTP id f14mr2311204oih.66.1431079291163; Fri, 08 May 2015 03:01:31 -0700 (PDT) Received: by 10.202.214.208 with HTTP; Fri, 8 May 2015 03:01:31 -0700 (PDT) In-Reply-To: References: Date: Fri, 8 May 2015 12:01:31 +0200 Message-ID: From: Benjamin To: Mike Hearn Content-Type: text/plain; charset=UTF-8 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 (benjamin.l.cordes[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: 1Yqf68-0006oY-Hm Cc: Bitcoin Dev Subject: Re: [Bitcoin-development] Assurance contracts to fund the network with OP_CHECKLOCKTIMEVERIFY X-BeenThere: bitcoin-development@lists.sourceforge.net X-Mailman-Version: 2.1.9 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 08 May 2015 10:01:37 -0000 Interesting. 1. How do you know who was first? If one node can figure out where more transactions happen he can gain an advantage by being closer to him. Mining would not be fair. 2. "A merchant wants to cause block number 1 million to effectively have a minting fee of 50BTC." - why should he do that? That's the entire tragedy of the commons problem, no? On Fri, May 8, 2015 at 11:49 AM, Mike Hearn wrote: > Looks like a neat solution, Tier. > > ------------------------------------------------------------------------------ > One dashboard for servers and applications across Physical-Virtual-Cloud > Widest out-of-the-box monitoring support with 50+ applications > Performance metrics, stats and reports that give you Actionable Insights > Deep dive visibility with transaction tracing using APM Insight. > http://ad.doubleclick.net/ddm/clk/290420510;117567292;y > _______________________________________________ > Bitcoin-development mailing list > Bitcoin-development@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/bitcoin-development >