Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Identify the ordering of state transitions across contract calls #757

Open
spalladino opened this issue Jun 6, 2023 · 2 comments
Open

Identify the ordering of state transitions across contract calls #757

spalladino opened this issue Jun 6, 2023 · 2 comments

Comments

@spalladino
Copy link
Collaborator

See this post for context, and this reply for the four different strategies for solving it:

  1. Global call counter
  2. Global transition counter
  3. Per-slot transition counter
  4. Per-slot state cache

I'd vote for (4).
@spalladino spalladino added this to A3 Jun 6, 2023
@github-project-automation github-project-automation bot moved this to Todo in A3 Jun 6, 2023
@dbanks12 dbanks12 mentioned this issue Aug 21, 2023
Merged
suyash67 pushed a commit that referenced this issue Aug 21, 2023
@dbanks12
hack(ordering): public state action ordering (#1685)
4f02d09 
Resolves #1617
Resolves #1622 
Resolves #1623 

Patches the `PublicDataReads` and `PublicDataUpdateRequests` coming from
the public kernel to reorder them properly until public state is
properly reordered (#757).

---------
@PhilWindle
Copy link
Collaborator

Closing this as I think it's done?

@github-project-automation github-project-automation bot moved this from Todo to Done in A3 Jan 3, 2024
@spalladino spalladino removed this from the 🦜 Mimic Public Function Call milestone Jan 3, 2024
@spalladino
Copy link
Collaborator Author

Just synched with @dbanks12 and it's still pending!

@spalladino spalladino reopened this Jan 3, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
A3
Status: Done
Milestone
No milestone
Development

No branches or pull requests
2 participants
@spalladino @PhilWindle