> Casting that vote does them no harm. > Every time another pool joins the blacklist, there's no harm to them to doing > so.
I actually agree that this is a problem, but that's actually not inherent in the proposed enforcement mechanism (just the current voting rules). Here's an alternate: - To start a vote, you set aside a part of your coinbase with amount X <= their entire coinbase amount. - Then you need 51 blocks with a "yes" vote before the coinbase maturity of the target for the vote to be considered a success. - Success means target coinbase has X coins reallocated/burned. - Failure means vote-initiating coinbase has X coins reallocated/burned. The incentives for voting miners are to vote yes if and only if they dislike the targeted miner more than the initiator (all other monetary effects are identical). That isn't a bulletproof way to force miners to only punish double spenders (rather than anything they dislike in general), but it removes the risk free nature of trying to take away another miner's coinbase. It means that you'll need a high level of confidence other miners are on your side before taking a risk, but, because you've got a much longer time frame than 10 minutes, you can get manual confirmation from other miners. On Thu, Apr 24, 2014 at 11:03 AM, Peter Todd <p...@petertodd.org> wrote: > On Thu, Apr 24, 2014 at 10:47:35AM -0400, Christophe Biocca wrote: >> Actually Peter, coinbase confiscations are a much worse mechanism for >> enforcement of widespread censorship rules than simple orphaning. They >> lose their power when the transaction miners are punished for can >> build up over time without losing their usefulness: > <snip> >> Of course, in such a dystopian future, orphaning would be the >> enforcement mechanism. It would be stupid to rely on coinbase >> reallocation/burning to do this task when the existing tools work so >> much better. > > I don't disagree with you at an end stage, but the thing with coinbase > blacklists/confiscation is because it's a voting mechanism the initial > stages of enforcing widespread censorship rules with it are much easier. > For instance, if a 10% pool that has been forced/wants to blacklist > certain transactions can do so, and then vote to blacklist blocks that > do not abide by that blacklist. Casting that vote does them no harm. > Every time another pool joins the blacklist, there's no harm to them to > doing so. At some point they will reach a majority, which causes the > blacklist to actually apply. The whole process happens smoothly, letting > the blacklist be applied safely and easily. With orphaning/reorging on > the other hand you just can't be sure that the other miners will > actually adopt it, making adoption risky. > > Of course, that's above and beyond the fact that you can't prove a > Finney attack happened to a third-party, making it easy to attack > smaller miners with Sybil attacks, get them creating blocks with > double-spends in them, and using that as an excuse to punish them. > >> What's interesting is that this mechanism is especially tailored to >> blocking time sensitive transactions (that need to be confirmed >> now/soon, or are worthless), such that their total out-of-band fees >> can't build up over time. Double spending is one such category. I'm at >> a loss to come up with something else, but maybe someone has a good >> example? > > Decentralized markets are a great example: the bids and orders they > depend on are time-senstive and become much less valuable if they get > delayed greatly. > > -- > 'peter'[:-1]@petertodd.org > 0000000000000000091ae589c034bc0466e2feca51dc018bb2c3303e8ab8648b ------------------------------------------------------------------------------ Start Your Social Network Today - Download eXo Platform Build your Enterprise Intranet with eXo Platform Software Java Based Open Source Intranet - Social, Extensible, Cloud Ready Get Started Now And Turn Your Intranet Into A Collaboration Platform http://p.sf.net/sfu/ExoPlatform _______________________________________________ Bitcoin-development mailing list Bitcoinfirstname.lastname@example.org https://lists.sourceforge.net/lists/listinfo/bitcoin-development