-
Notifications
You must be signed in to change notification settings - Fork 517
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
Feature/include network id for account update hash berk #13880
Feature/include network id for account update hash berk #13880
Conversation
…include-network-id-for-account-update-hash-berk
!ci-build-me |
…include-network-id-for-account-update-hash-berk
!ci-build-me |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
See nit in comments.
Also, shouldn't we have a test to check that we reject these transactions as part of blocks (/staged ledger diffs) too?
…include-network-id-for-account-update-hash-berk
…include-network-id-for-account-update-hash-berk
!ci-build-me |
!ci-build-me |
…include-network-id-for-account-update-hash-berk
…include-network-id-for-account-update-hash-berk
!ci-build-me |
!ci-build-me |
src/app/test_executive/zkapps.ml
Outdated
@@ -242,7 +243,8 @@ module Make (Inputs : Intf.Test.Inputs_intf) = struct | |||
, zkapp_command_invalid_nonce | |||
, zkapp_command_insufficient_funds | |||
, zkapp_command_insufficient_replace_fee | |||
, zkapp_command_insufficient_fee ) = | |||
, zkapp_command_insufficient_fee | |||
, zkapp_command_single_account_update ) = |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
nit: could you rename this to something more meaningful- zkapp_command_cross_network_replay
or something?
|
||
(* This test uses dummy verifiers, that's why it's not rejecting the problematic zkapp command | ||
But this test is still useful, since it exercises the parts that doesn't requires a pickles instance | ||
Combining together with the test that uses pickles directly, these 2 tests would make sure that |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
can you edit the comment to describe this test? What are the 2 tests here?
@@ -4581,6 +4581,130 @@ module Make_str (A : Wire_types.Concrete) = struct | |||
in | |||
zkapp_command | |||
|
|||
module Single_account_update_spec = struct |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Can you add a comment to describe what this is for (as there are a few different specs) and when it can be used?
zkapp_command_cross_network_replay
staged_ledger.ml
…include-network-id-for-account-update-hash-berk
…' of github.com:MinaProtocol/mina into feature/include-network-id-for-account-update-hash-berk
!ci-build-me |
!ci-build-me |
…include-network-id-for-account-update-hash-berk
!ci-build-me |
!approved-for-mainnet |
Explain your changes:
This PR adds chain name to the account update hash in order to address the concern described here: #13759
Explain how you tested your changes:
Added a section for testing account update with different network ID in zkapps-integration-test;
also added a test in transaction_pool, but since we only have dummy verifier in unit-test, so it should pass the verification.
Checklist: