rich1.0npub1r3san9v5njl6798hvauyu9ntm6r9c7u8s0t65wls58gpfdcvqp5sa48d0uhttps://nostr.ae/npub1r3san9v5njl6798hvauyu9ntm6r9c7u8s0t65wls58gpfdcvqp5sa48d0unjumphttps://nostr.ae📅 Original date posted:2015-06-12 📝 Original message:Peter it's not clear to me that your described protocol is free of miner influence over the vote, by artificially generating transactions which they claim in their own blocks, or conforming incentives among voters by opting to be with the (slight) majority in order to minimize fees. Wouldn't it in fact be simpler to use the dynamic block size adjustment algorithm presented to the list a few weeks back, where the miner opts for a larger block by sacrificing fees? In that way the users "vote" for larger blocks by including sufficient fees to offset subsidy, but as it is an economic incentives miners gain nothing by inflating the fees in their own blocks. On Fri, Jun 12, 2015 at 11:11 AM, Peter Todd <pete at petertodd.org> wrote: > Jeff Garzik recently proposed that the upper blocksize limit be removed > entirely, with a "soft" limit being enforced via miner vote, recorded by > hashing power. > > This mechanism within the protocol for users to have any influence over > the miner vote. We can add that back by providing a way for transactions > themselves to set a flag determining whether or not they can be included > in a block casting a specific vote. > > We can simplify Garzik's vote to say that one of the nVersion bits > either votes for the blocksize to be increased, or decreased, by some > fixed ratio (e.g 2x or 1/2x) the next interval. Then we can use a > nVersion bit in transactions themselves, also voting for an increase or > decrease. Transactions may only be included in blocks with an > indentical vote, thus providing miners with a monetary incentive via > fees to vote according to user wishes. > > Of course, to cast a "don't care" vote we can either define an > additional bit, or sign the transaction with both versions. Equally we > can even have different versions with different fees, broadcast via a > mechanism such as replace-by-fee. > > > See also John Dillon's proposal for proof-of-stake blocksize voting: > > > https://www.mail-archive.com/bitcoin-development@lists.sourceforge.net/msg02323.html > > -- > 'peter'[:-1]@petertodd.org > 0000000000000000127ab1d576dc851f374424f1269c4700ccaba2c42d97e778 > > > ------------------------------------------------------------------------------ > > _______________________________________________ > Bitcoin-development mailing list > Bitcoin-development at lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/bitcoin-development > > -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.linuxfoundation.org/pipermail/bitcoin-dev/attachments/20150612/89a6898b/attachment.html>