dido:public:ra:xapend:xapend.b_stds:defact:bitcoin:bips:bip_0113
Differences
This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision | |||
|
dido:public:ra:xapend:xapend.b_stds:defact:bitcoin:bips:bip_0113 [2021/08/17 13:18] murphy |
dido:public:ra:xapend:xapend.b_stds:defact:bitcoin:bips:bip_0113 [2021/08/18 10:21] (current) murphy |
||
|---|---|---|---|
| Line 25: | Line 25: | ||
| : //At present, transactions are excluded from inclusion in a block if the present time or [[dido:public:ra:xapend:xapend.a_glossary:b:block_height|block height]] is less than or equal to that specified in the locktime. Since the consensus rules do not mandate strict ordering of block timestamps, this has the unfortunate outcome of creating a perverse incentive for miners to lie about the time of their blocks in order to collect more fees by including transactions that by wall clock determination have not yet matured.// | : //At present, transactions are excluded from inclusion in a block if the present time or [[dido:public:ra:xapend:xapend.a_glossary:b:block_height|block height]] is less than or equal to that specified in the locktime. Since the consensus rules do not mandate strict ordering of block timestamps, this has the unfortunate outcome of creating a perverse incentive for miners to lie about the time of their blocks in order to collect more fees by including transactions that by wall clock determination have not yet matured.// | ||
| - | : //This BIP proposes comparing the locktime against the median of the past 11 block's timestamps, rather than the timestamp of the block including the transaction. Existing consensus rules guarantee this value to monotonically advance, thereby removing the capability for miners to claim more transaction fees by lying about the timestamps of their block.// | + | : //This BIP proposes comparing the locktime against the median of the past 11 block's timestamps, rather than the timestamp of the block including the transaction. Existing consensus rules guarantee this value to monotonically advance, thereby removing the capability for miners to claim more [[dido:public:ra:xapend:xapend.a_glossary:t:transaction_fees|transaction fees]] by lying about the timestamps of their block.// |
| : //This proposal seeks to ensure reliable behaviour in locktime calculations as required by [[dido:public:ra:xapend:xapend.b_stds:defact:bitcoin:bips:bip_0065| BIP65]] (CHECKLOCKTIMEVERIFY) and matching the behavior of [[dido:public:ra:xapend:xapend.b_stds:defact:bitcoin:bips:bip_0068| BIP68]] (sequence numbers) and [[dido:public:ra:xapend:xapend.b_stds:defact:bitcoin:bips:bip_0112| BIP112]] (CHECKSEQUENCEVERIFY).// | : //This proposal seeks to ensure reliable behaviour in locktime calculations as required by [[dido:public:ra:xapend:xapend.b_stds:defact:bitcoin:bips:bip_0065| BIP65]] (CHECKLOCKTIMEVERIFY) and matching the behavior of [[dido:public:ra:xapend:xapend.b_stds:defact:bitcoin:bips:bip_0068| BIP68]] (sequence numbers) and [[dido:public:ra:xapend:xapend.b_stds:defact:bitcoin:bips:bip_0112| BIP112]] (CHECKSEQUENCEVERIFY).// | ||
dido/public/ra/xapend/xapend.b_stds/defact/bitcoin/bips/bip_0113.1629220699.txt.gz · Last modified: 2021/08/17 13:18 by murphy
