Duplicate transactions

en · official · sha256:e0849b78a537fe24b6160bbadb9fb153c830d9f7f12f08108aa94b6d8979483dEN

==Specification== 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. This rule initially applied to all blocks whose timestamp is after March 15, 2012, 00:00 UTC (testnet: February 20, 2012 00:00 UTC). It was later extended by Commit [https://github.com/bitcoin/bitcoin/commit/ab91bf39b7c11e9c86bb2043c24f0f377f1cf514 Apply BIP30 checks to all blocks except the two historic violations.] to apply to all blocks except the two historic blocks at heights 91842 and 91880 on the main chain that had to be grandfathered in.

Ссылаются нормы: EveryInputComesFromLiveUtxo, EveryInputMustExistInClosedUtxo, InputsMustCoverOutputs, KnownBip30RepeatIsGrandfathered, Output, TransactionIsValidInNarrowSlice, UtxoSnapshotClosure, all_referenced_inputs_are_live_utxo, bip30_repeat_is_grandfathered, historic_bip30_repeat, input_references, input_value_covers_outputs, referenced_output, total_input_satoshis, total_output_satoshis, transaction_candidate, transaction_valid_in_slice, tx_inputs_valid_in_slice, unspent_output