From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from sog-mx-1.v43.ch3.sourceforge.com ([172.29.43.191] helo=mx.sourceforge.net) by sfs-ml-2.v29.ch3.sourceforge.com with esmtp (Exim 4.76) (envelope-from ) id 1Wd8R7-0006YD-2V for bitcoin-development@lists.sourceforge.net; Thu, 24 Apr 2014 01:26:49 +0000 X-ACL-Warn: Received: from mail-pd0-f179.google.com ([209.85.192.179]) by sog-mx-1.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128) (Exim 4.76) id 1Wd8R6-0006ZB-29 for bitcoin-development@lists.sourceforge.net; Thu, 24 Apr 2014 01:26:49 +0000 Received: by mail-pd0-f179.google.com with SMTP id g10so1357346pdj.10 for ; Wed, 23 Apr 2014 18:26:42 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:message-id:date:from:user-agent:mime-version:to :subject:references:in-reply-to:content-type :content-transfer-encoding; bh=SEyVtYo+TGIjLnFfwdY2Qpvl1j9yzSpk1OiQut7DvSI=; b=aliqaReCDII8BMRa7erbUB3YHZkH0kgxhC1xkBmh5XkPuav5vIrs049l+DYq17ylw2 CjX6MCXUz1rxiFRcg8ziIoqlY0c2ESl70xVrXaefbeSaq9JwvgtQ+56LK8WSlTU26k1s B+oYrGpwGl4SMYX1j13vy5FLMWgb9U4EPiulzvQCaVVArz/4Ky5ef8+OiqCtE+ymw4zu bS956pH23Kt3nhVvvZgCBpJXsvYtj2EzvAPPYLbJOrPJtgvvswqc8ZUlJyQ+ge2aBUtY WRyEVlGr7U4DjVidguTYe5Oj+cekb6RWr9bYN1OYFPzCZWYYXUhYikNiwSY7eVr0GfMm eEVg== X-Gm-Message-State: ALoCoQkeYfudvLP45Pt7QfWYN48mUqWRjzLUqT/WRrTAPXBDOYUUxIMDwGUs1DEMUyrOjSD3vP5b X-Received: by 10.68.201.10 with SMTP id jw10mr60131365pbc.25.1398300945911; Wed, 23 Apr 2014 17:55:45 -0700 (PDT) Received: from [10.100.1.239] ([204.58.254.99]) by mx.google.com with ESMTPSA id wd2sm12080250pab.0.2014.04.23.17.55.44 for (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Wed, 23 Apr 2014 17:55:45 -0700 (PDT) Message-ID: <535860F6.20205@thinlink.com> Date: Wed, 23 Apr 2014 17:55:18 -0700 From: Tom Harding User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.4.0 MIME-Version: 1.0 To: bitcoin-development@lists.sourceforge.net References: In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Score: 0.6 (/) X-Spam-Report: Spam Filtering performed by mx.sourceforge.net. See http://spamassassin.org/tag/ for more details. -0.0 RCVD_IN_DNSWL_NONE RBL: Sender listed at http://www.dnswl.org/, no trust [209.85.192.179 listed in list.dnswl.org] 0.6 RCVD_IN_SORBS_WEB RBL: SORBS: sender is an abusable web server [204.58.254.99 listed in dnsbl.sorbs.net] X-Headers-End: 1Wd8R6-0006ZB-29 Subject: Re: [Bitcoin-development] Coinbase reallocation to discourage Finney attacks 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: Thu, 24 Apr 2014 01:26:49 -0000 On 4/23/2014 2:23 PM, Tier Nolan wrote: > An interesting experiment would be a transaction "proof of > publication" chain. What if a transaction could simply point back to an earlier transaction, forming a chain? Not a separately mined blockchain, just a way to establish an official publication (execution) order. Double spends would be immediately actionable with such a sequence. Transactions in a block could eventually be required to be connected in such a chain. Miners would have to keep or reject a whole mempool chain, since they lack the keys to change the sequence. They would have to prune a whole tx subchain to insert a double spend (and this would still require private keys to the double spend utxo's). This idea seemed promising, until I realized that with the collision rebasing required, it would barely scale to today's transaction rate. Something that scales to 10,000's of transactions per second, and really without limit, is needed. Anyway, I wrote it up here: https://github.com/dgenr8/out-there/blob/master/tx-chains.md