mempool: Remove potential negative locktime check.
This removes the standardness check to reject transactions with a lock time greater than a maxint32 because the old bitcoind nodes which it was designed to protect against are no longer valid for other reasons and thus there are no longer any of them on the network to worry about.
This commit is contained in:
parent
f4d376d7af
commit
05bdf3b741
1 changed files with 0 additions and 10 deletions
|
@ -658,16 +658,6 @@ func (mp *TxPool) maybeAcceptTransaction(tx *btcutil.Tx, isNew, rateLimit, rejec
|
|||
return nil, nil, txRuleError(wire.RejectInvalid, str)
|
||||
}
|
||||
|
||||
// Don't accept transactions with a lock time after the maximum int32
|
||||
// value for now. This is an artifact of older bitcoind clients which
|
||||
// treated this field as an int32 and would treat anything larger
|
||||
// incorrectly (as negative).
|
||||
if tx.MsgTx().LockTime > math.MaxInt32 {
|
||||
str := fmt.Sprintf("transaction %v has a lock time after "+
|
||||
"2038 which is not accepted yet", txHash)
|
||||
return nil, nil, txRuleError(wire.RejectNonstandard, str)
|
||||
}
|
||||
|
||||
// Get the current height of the main chain. A standalone transaction
|
||||
// will be mined into the next block at best, so its height is at least
|
||||
// one more than the current height.
|
||||
|
|
Loading…
Add table
Reference in a new issue