From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from sog-mx-2.v43.ch3.sourceforge.com ([172.29.43.192] helo=mx.sourceforge.net) by sfs-ml-4.v29.ch3.sourceforge.com with esmtp (Exim 4.76) (envelope-from ) id 1RO5IU-0001Jj-H3 for bitcoin-development@lists.sourceforge.net; Wed, 09 Nov 2011 10:22:22 +0000 X-ACL-Warn: Received: from backup-server.nordu.net ([193.10.252.66]) by sog-mx-2.v43.ch3.sourceforge.com with esmtps (TLSv1:AES256-SHA:256) (Exim 4.76) id 1RO5IO-0005I1-6q for bitcoin-development@lists.sourceforge.net; Wed, 09 Nov 2011 10:22:22 +0000 Received: from [109.105.106.199] ([109.105.106.199]) (authenticated bits=0) by backup-server.nordu.net (8.14.3/8.14.3) with ESMTP id pA9AM669021732 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO) for ; Wed, 9 Nov 2011 11:22:09 +0100 (CET) From: =?iso-8859-1?Q?Michael_Gr=F8nager?= Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: quoted-printable Date: Wed, 9 Nov 2011 11:22:06 +0100 Message-Id: To: Bitcoin Dev Mime-Version: 1.0 (Apple Message framework v1251.1) X-Mailer: Apple Mail (2.1251.1) X-Spam-Score: 0.0 (/) X-Spam-Report: Spam Filtering performed by mx.sourceforge.net. See http://spamassassin.org/tag/ for more details. X-Headers-End: 1RO5IO-0005I1-6q Subject: [Bitcoin-development] multisig, op_eval and lock_time/sequence... 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: Wed, 09 Nov 2011 10:22:22 -0000 Hi All, Along with the multisig/op_eval BIPs (11/12) I am considering how the = actual client functionality could be. Some of you might already have the solution for this - if not I would = like to propose the following... Lets consider the 2 of 3 multisig - and lets say I now have some coins = hence only redeemable using 2 key signatures. So when I want to spend = them I would do: 1. from client1 I issue a transaction containing one of the signatures, = with a locktime e.g. 10 minutes from now and a sequence of 0. This = transaction is now posted to the p2p network. 2. client2 discovers the transaction and that it will affect its wallet. = It hence modifies the transaction to includes also the second signature, = changes the sequence to 0xFFFFFFFF=3Dfinal and the lock_time to 0 and = retransmits the transaction. 3. The transaction is now valid and final and will be approved by the = miners. However, for this setup to be possible, we need to reenable the = replacement of transaction in the client.... Anyone working on this now ? Alternatively, the transactions would need to be sent between clients = using another protocol... Cheers, Michael