Re: [Bitcoin-development] RFC: MERGE transaction/script/process for forked chains

2013-12-17 Thread Troy Benjegerdes
On Tue, Dec 17, 2013 at 02:48:14PM -0800, Gregory Maxwell wrote: > On Tue, Dec 17, 2013 at 2: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 fork

Re: [Bitcoin-development] RFC: MERGE transaction/script/process for forked chains

2013-12-17 Thread Luke-Jr
On Tuesday, December 17, 2013 10:41:30 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 cry

Re: [Bitcoin-development] RFC: MERGE transaction/script/process for forked chains

2013-12-17 Thread Mark Friedenbach
-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 bi

Re: [Bitcoin-development] RFC: MERGE transaction/script/process for forked chains

2013-12-17 Thread Gregory Maxwell
On Tue, Dec 17, 2013 at 2: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. We already automatically merge forks that we become aware of simply b