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

Clarify which phase1 validation is skipped for isValid == False transactions #4695

Open
lehins opened this issue Oct 15, 2024 · 0 comments
Open
Labels
🖋️ documentation Everything related to documenting code, processes, etc.

Comments

@lehins
Copy link
Collaborator

lehins commented Oct 15, 2024

Figure out a consistent story about Tx for phase2: what should be validated what should not.

It would be useful to create a document that outlines all parts of the transaction that are epxected to be valid when transaction itself is marked as phase2 invalid.

It is possible that we do some redundant checks that might not be necessary for such transactions.

It is important to note in such document that by default it is expected for all transactions to be phase1 valid, because normal operations of the mempool will prevent phase1 invalid transactions. However, the protocol does not prevent some custom version of the node to add phase2 invalid transactions to the chain that have some aspects of such transactions to be invalid, because those aspects do not affect the ledger state.

Therefore, this ticket could be phrased slightly differnetly:

Document exactly which parts of the transaction are validated, whenever isValid == False

@lehins lehins added the 🖋️ documentation Everything related to documenting code, processes, etc. label Oct 15, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
🖋️ documentation Everything related to documenting code, processes, etc.
Projects
None yet
Development

No branches or pull requests

1 participant