This repository has been archived by the owner on Jun 11, 2024. It is now read-only.
Add LIP "Establish block validity by applying transactions sequentially" #43
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
IkerAlus
approved these changes
Jan 31, 2020
ishantiw
approved these changes
Feb 3, 2020
ManuGowda
approved these changes
Feb 3, 2020
karmacoma
approved these changes
Feb 13, 2020
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This pull request submits the LIP "Establish block validity by applying transactions sequentially".
This LIP introduces a procedure to assert the validity of blocks containing multiple interdependent transactions.
This is done by defining a general way to order transactions.
We then consider a block valid if every transaction is valid against the transitory state leading up to it.
This LIP also specifies when delegates receive their block rewards and fees.