mirror of
https://github.com/bitcoin/bips.git
synced 2025-05-12 12:03:29 +00:00
Minor improvements to BIP 30
This commit is contained in:
parent
c00721d90f
commit
4d436a8bb4
@ -15,7 +15,7 @@ So far, the Bitcoin reference implementation always assumed duplicate transactio
|
|||||||
|
|
||||||
==Specification==
|
==Specification==
|
||||||
To counter this problem, the following network rule is introduced:
|
To counter this problem, the following network rule is introduced:
|
||||||
*Blocks are not allowed to contain a transaction whose identifier matches that of an earlier, not-fully-spent transaction in the same chain.
|
*Blocks are not allowed to contain a transaction whose hash matches that of an earlier transaction in the same chain, unless that earlier transaction was already fully spent before said block.
|
||||||
|
|
||||||
This rule is to be applied to all blocks whose timestamp is after a point in time that is yet to be decided.
|
This rule is to be applied to all blocks whose timestamp is after a point in time that is yet to be decided.
|
||||||
|
|
||||||
@ -41,7 +41,7 @@ The addition of this rule only makes some previously-valid blocks invalid. This
|
|||||||
A patch for the reference client can be found on https://github.com/sipa/bitcoin/tree/nooverwritetx
|
A patch for the reference client can be found on https://github.com/sipa/bitcoin/tree/nooverwritetx
|
||||||
|
|
||||||
==Acknowledgements==
|
==Acknowledgements==
|
||||||
Thanks to Russell O'Connor for finding and demonstrating this problem, and helping test the patch.
|
Thanks to Russell O'Connor for finding and demonstrating this problem and helping test the patch, and to Ben Reeves for pointing out a few weaknesses in the implementation.
|
||||||
|
|
||||||
[[Category:Developer]]
|
[[Category:Developer]]
|
||||||
[[Category:Technical]]
|
[[Category:Technical]]
|
||||||
|
Loading…
x
Reference in New Issue
Block a user