EIP-0009: Hard-fork Activation protocol (v1 to v2) #12
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
This was referenced Jun 8, 2020
|
What's preventing this from being merged? |
@glasgowm148 Can be merged now. |
arobsn
approved these changes
Sep 18, 2023
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Motivaton
The upcoming Hard-fork has a lot of changes in ErgoTree evaluation. In order to ensure smooth and manageable switch from Ergo Protocol v1 to EP2 we need to ensure some conditions.
The described process is motivated by switching from AOT to JIT costing and other consensus critical changes in ErgoTree interpreter.
Contributions are welcome.