|(3 intermediate revisions by 2 users not shown)|
|−|A block is "discouraged" if the ShouldDiscourage() method in the source code returns true. Currently, for each "new rule" this happens only if (a) 80 of the last 100 blocks obey the "new rule" and (b) the block does not obey the "new rule". |+|
block is , of the blockdoes not .
| || |
|−|At the moment, the only "new rule" for which disobedience is being discouraged is the "put the block height in the coinbase" rule. |+|
is in ..., this.
|−|* Clients '''will consider discouraged blocks''' when determining which chain is difficultywise-longest. | |
|−|* Mining clients '''will not build on top of''' discouraged blocks. | |
|−|* Transactions cannot be discouraged (only blocks), so this does not affect transaction propagation. | |
|−|[[Category:Technical]][[Category:Developer]] | |
Latest revision as of 02:56, 17 October 2013
The idea of "discouraging" a block is to not mine on top of that block, instead mining on top of some other block in an attempt to orphan the discouraged block. Bitcoin does not currently implement block discouraging in any form.
Block discouragement is discussed in a forum post, "Feather-forks: enforcing a blacklist with sub-50% hash power", although the idea predates this.