Conversation
Previously the transaction submission was asynchronous. Now, we return the ID of the launched transaction to the caller.
Now transparent and Cairo RMs have properly different keyspace paths.
08eb5e8 to
63c898b
Compare
e359542 to
d8e1e16
Compare
d8e1e16 to
7a22a8a
Compare
a8b5057 to
1a2d9dd
Compare
…tem/mempool-keyspace
…tem/mempool-keyspace
1a2d9dd to
e3edfda
Compare
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 join this conversation on GitHub.
Already have an account?
Sign in to comment
3 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.
Expose keyspaces at mempool level (no scry allowed during evaluation). Depending on writes, choose backend to execute, depending on reads, allow specific scry calls.