Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Transactions are not checked for nLocktime and inputs are not checked for nSequence #145

Open
sirdeggen opened this issue Nov 13, 2023 · 1 comment
Assignees

Comments

@sirdeggen
Copy link
Collaborator

/* 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:

@sirdeggen sirdeggen self-assigned this Jul 23, 2024
@sirdeggen
Copy link
Collaborator Author

Ongoing discussion within BSVA regarding how Teranode will handle locktime and sequence. This will inform the direction of this issue.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant