On Sun, Feb 09, 2014 at 05:25:41PM +0000, Luke-Jr wrote: > On Sunday, February 09, 2014 5:12:14 PM Peter Todd wrote: > > We have an embedded consensus system and we want to be able to upgrade > > it with new rules. > > This asserts a central authority and gives developers too much power.
Please, the rule change only can happen if users accept it. If anything my proposed mechanism makes it even harder for developers to impose anything by fiat: the spending your digital asset under new rules decreases the amount available of it to trade with users who chose to accept only the old rules. Since there is no safety concern involved, the process is safe for both groups, developers can't plea to the community that "OMG the sky will fall and you'll be all defrauded if you don't upgrade right now!!!" Instead they'll be forced to make it clear that if the community doesn't accept the new rules, whatever assets you've moved to the new system may become forever worthless. -- 'peter'[:-1]@petertodd.org 000000000000000075829f6169c79d7d5aaa20bfa8da6e9edb2393c4f8662ba0
signature.asc
Description: Digital signature
------------------------------------------------------------------------------ Managing the Performance of Cloud-Based Applications Take advantage of what the Cloud has to offer - Avoid Common Pitfalls. Read the Whitepaper. http://pubads.g.doubleclick.net/gampad/clk?id=121051231&iu=/4140/ostg.clktrk
_______________________________________________ Bitcoin-development mailing list Bitcoin-development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bitcoin-development
