You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
/* lots of our valid test transactions have this sequence number, is this not allowed?
This should check to ensure inputs are all final only if the nLocktime is being enforced. The TODO suggests that this check was raising issues during development.
I think that it should be fine to invert this. Only pass if nSequence are all final. Otherwise we have to check nLocktime, but we don't know the height we're at in terms of block without checking blockTx which complicates things.
I would suggest we add status context rather than erroring out. If the nSequence numbers are lower than max - just noting that it might be the case that this transaction does not get mined until the nLocktime value passes.
Discussion:
The text was updated successfully, but these errors were encountered:
arc/validator/default/default_validator.go
Line 158 in 2643ccb
This should check to ensure inputs are all final only if the nLocktime is being enforced. The TODO suggests that this check was raising issues during development.
I think that it should be fine to invert this. Only pass if nSequence are all final. Otherwise we have to check nLocktime, but we don't know the height we're at in terms of block without checking blockTx which complicates things.
I would suggest we add status context rather than erroring out. If the nSequence numbers are lower than max - just noting that it might be the case that this transaction does not get mined until the nLocktime value passes.
Discussion:
The text was updated successfully, but these errors were encountered: