Validator driven transactions #704
Closed
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 PR has become stale because it has been open for 30 days with no activity. Adding the |
|
Going through and closing stale PRs. Sorry this was not reviewed earlier, if you want to pick this back up, feel free to re-open and I'll add a more detailed spec to the GitHub issue, so the target for this work is more clear. |
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.
Context
This PR covers: #336. This is a guess work of how the Validator Driven Transactions should work. The idea is to use rules from genesis to check if the transaction is validator driven then use a flag to bypass some operations that's only needed by authenticated transactions.
Tests
e2e tests were passes but haven't been updated since I need to know if it's the right direction