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-1.v29.ch3.sourceforge.com with esmtp (Exim 4.76) (envelope-from ) id 1Vt3Rg-00016Z-Ko for bitcoin-development@lists.sourceforge.net; Tue, 17 Dec 2013 22:48:56 +0000 Received: from mail-pb0-f48.google.com ([209.85.160.48]) by sog-mx-4.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128) (Exim 4.76) id 1Vt3Re-0007ck-S7 for bitcoin-development@lists.sourceforge.net; Tue, 17 Dec 2013 22:48:56 +0000 Received: by mail-pb0-f48.google.com with SMTP id md12so7592109pbc.35 for ; Tue, 17 Dec 2013 14:48:49 -0800 (PST) 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:organization:user-agent :mime-version:to:subject:references:in-reply-to:content-type :content-transfer-encoding; bh=1SpBJcEzgGL+VWE+110jL8IMOA8HhRP/1embbCGhTtg=; b=P17UZZL5qczxz9PtGHklo0ub6t4LhaCLfLnscj2vqtmyuv7xK/bsUSMVksw5rIptir MOOmea8TcBUWEnsOhwfEwS5VbZcDjHKbFelfMBQbOjtkmXwBf4HlHkJoNek+Ju5eSgBa vEUY5JHgF5Qf08ypcxhJFEypT2VlTE9yiJGCtoFzpdGpO3fRdHtAZXQavoD0cp3UuqGp sp9ta8m9Vah0x7blLFh2XGmYAHXK11Fijv89kJTzfJcvyzecqrOyT2gGt8mN1uaITD2+ zjS80d/B9R9ge8r2x0kCU7j3kE/0JMHwbnCsXVBiMdnjCoC+L0cmLXoEBzStY//Nrbt8 nuJA== X-Gm-Message-State: ALoCoQlGL9u7GuzQDJ/ZRb5UUFtIjKEayb11/+RA4mOQV35T6WgD06tcRPSdbeua3QBSG+X9GUyg X-Received: by 10.68.212.37 with SMTP id nh5mr30364661pbc.16.1387320528883; Tue, 17 Dec 2013 14:48:48 -0800 (PST) Received: from [192.168.127.173] (50-0-36-217.dsl.dynamic.sonic.net. [50.0.36.217]) by mx.google.com with ESMTPSA id pe3sm36378244pbc.23.2013.12.17.14.48.46 for (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Tue, 17 Dec 2013 14:48:47 -0800 (PST) Message-ID: <52B0D4CE.9020108@monetize.io> Date: Tue, 17 Dec 2013 14:48:46 -0800 From: Mark Friedenbach Organization: Monetize.io Inc. User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Thunderbird/24.1.1 MIME-Version: 1.0 To: bitcoin-development@lists.sourceforge.net References: <20131217224130.GC3180@nl.grid.coop> In-Reply-To: <20131217224130.GC3180@nl.grid.coop> X-Enigmail-Version: 1.6 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-Spam-Score: 0.0 (/) X-Spam-Report: Spam Filtering performed by mx.sourceforge.net. See http://spamassassin.org/tag/ for more details. 0.0 URIBL_BLOCKED ADMINISTRATOR NOTICE: The query to URIBL was blocked. See http://wiki.apache.org/spamassassin/DnsBlocklists#dnsbl-block for more information. [URIs: doubleclick.net] X-Headers-End: 1Vt3Re-0007ck-S7 Subject: Re: [Bitcoin-development] RFC: MERGE transaction/script/process for forked chains 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: Tue, 17 Dec 2013 22:48:56 -0000 -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Transactions != blocks. There is no need for a "merge" block. You are free to trade transactions off-line, so long as you are certain the other parties are not secretly double-spending coins they send you on the block chain. When connection to the bitcoin network is re-established, you simply transmit the transactions and in the regular course of things they make their way into one of the next blocks. Any transactions which derive from the double-spent one are invalid. But that's your problem, not the miners - chase after Bob and get him to give you the money he owes. On 12/17/2013 02:41 PM, Troy Benjegerdes wrote: > I want to get some feedback.. I've used distributed version control > systems for a long time, and the most useful feature is to be > able to merge two different forks. > > So what's the equivalent of this for Bitcoin or other > crypto-currencies? > > Let's suppose that me and my friends get 'islanded' from the rest > of the internet for a week, but we still want to trade bitcoin. It > would work if there are local miners, until we reconnect. > > Suppose we have the main chain (Alice), while bob is on a boat, > trading with some friends, but has no network connectivity. > > When bob reconnects with Alice, a 'Merge' transaction happens where > a miner looks at bob's forked blockchain, sees no double-spends, > and includes BOTH chains. > > Now suppose someone on bob's boat has a buggy client, or sent a > transaction before disconnect that results in a double-spend on the > merge. > > So we have a merge conflict, which generally requires human > interaction, so bob and his friends broadcast a MERGE request with > a transaction fee sufficient to cover reconciling the > double-spends, AND incentivize a miner to do some extra work to > merge. > > Thoughts everyone? > > -- Troy > > ------------------------------------------------------------------------------ > > Rapidly troubleshoot problems before they affect your business. Most IT > organizations don't have a clear picture of how application > performance affects their revenue. With AppDynamics, you get 100% > visibility into your Java,.NET, & PHP application. Start your > 15-day FREE TRIAL of AppDynamics Pro! > http://pubads.g.doubleclick.net/gampad/clk?id=84349831&iu=/4140/ostg.clktrk > > _______________________________________________ > Bitcoin-development mailing list > Bitcoin-development@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/bitcoin-development > -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.14 (GNU/Linux) Comment: GPGTools - http://gpgtools.org Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ iQIcBAEBAgAGBQJSsNTOAAoJEAdzVfsmodw4rBUP/jBFvPks4h0k1GQEPQPYvqNa 3OhuSlC9EfHmjXxftj6j0lH6JO60BFIoA3P76oFycQRqzNSw3YoldQ1MttpNAAZg ftiJJjYcuVmDYYWxfWPZN7ZsHrrhGkMn+i0PB1vXU3PB3sStb18vhbIoTZmwH7Rk vaUaX8EKFh6R8Y+6nqFMKu8eALaFQPJFP1aNo31ixsFFJrl02zQeIZiTbrOensEj 6AhXm2oYRqB1aolMmy/m5zcA3IicayJ6seoCQcRhPty6G2l+/4opgATdEBjzgczW Yhw20YkayyvPa+Fsqwad5AzgGYbm7OA0U6mO/pfeNhglNSt/TGfuSPe1oM9hWt9/ 8gP3PG4O4Fxi+gOAlNABgmoRKvQK8T3TX+eoayxPJiLxi+5l3+1CK0FK1+mKPThr heFrc5e9QlUIgATOpLYSs/elgAFM6N2Sez+RNiOg201M10VVKqXzBgZRQ+IYRRk6 jbaBKxsQ/ql5+2vwaUkplg/6Y6rfvRItQ+8xwXEvxazPAAh3Mp0fPbqas+F0e1Ie SwVTq517iV7eu+kMxOJEqaCky8ihbaUmshjeEccXdbodpygxCR2dZ0xAkvwXYtnK +ZjLQ7o8ySZs89Jvdx8H2fsu6m3hS/7Mm+zJVGV/hLHLoL7IrYPzTHcOHv8eT106 IYM30Hv+vDrt+f8ZRZ80 =09Pt -----END PGP SIGNATURE-----