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.

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

Remove timestamp field in zkapp_precondition #560

Merged
merged 15 commits into from
Dec 12, 2022
Merged

Conversation

ghost-not-in-the-shell
Copy link
Contributor

@ghost-not-in-the-shell ghost-not-in-the-shell commented Nov 15, 2022

This PR removes timestamp and also globalSlotSinceHardFork field in zkapp_precondition

Copy link
Collaborator

@mitschabaude mitschabaude left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM!

@mitschabaude
Copy link
Collaborator

but we shouldn't merge yet - should set up and run a CI workflow for this branch first

@mitschabaude
Copy link
Collaborator

@ghost-not-in-the-shell to make the checks pass, you need to update the OCaml bindings of snarkyjs. this is done by running the following from the Mina repo:

./scripts/update-snarkyjs-bindings.sh

and committing the result here

@@ -395,7 +395,7 @@ function LocalBlockchain({
}
events[addr][tokenId].push({
events: p.body.events,
slot: networkState.globalSlotSinceHardFork.toString(),
slot: networkState.globalSlotSinceGenesis.toString(),
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@mitschabaude Since I removed globalSlotSinceHardFork, I replaced this with globalSlotSinceGenesis, would that be okay?

@mitschabaude mitschabaude merged commit 5bb548d into berkeley Dec 12, 2022
@mitschabaude mitschabaude deleted the remove-timestamp branch December 12, 2022 08:36
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants