This repository was archived by the owner on May 12, 2025. It is now read-only.
Async chain state side effects from confidential execution#68
Open
Ruteri wants to merge 1 commit into
Open
Conversation
Member
|
left comments on the forum https://collective.flashbots.net/t/async-chain-state-transition-using-messages/2733/5 |
This file contains hidden or 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
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
2 participants
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.
I propose to change how chain transition based on confidential requests is handled: it should be done based on messages generated by the confidential request instead of the return statement.
Link to collective post: https://collective.flashbots.net/t/async-chain-state-transition-using-messages/2733.
Naming subject to change.