On Tue, Dec 17, 2013 at 02:48:14PM -0800, Gregory Maxwell wrote: > On Tue, Dec 17, 2013 at 2:41 PM, Troy Benjegerdes <ho...@hozed.org> 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 by > pulling in all the novel non-conflicting transactions the fork > contains and including them in our next blocks.
Now maybe this is a fatal flaw with Bitcoin's hard upper limit for number of coins, but any miners that with good faith tried to support an islanded bitcoin network now have generate transactions that get clobbered when the network reconnects. I can imagine a way to do this with some freicoin-like demurrage, which would only impact new coinbase based on the percentage of the hashing power that was on the other side of the fork. So if you are with the 95% of hashing power, you keep 95% of the new coins when the other 5% shows back up from being islanded. And this is also way more complicated than what I had first imagined to do securely and reliably. ------------------------------------------------------------------------------ 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
