-
Notifications
You must be signed in to change notification settings - Fork 136
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
Fix SnarkyJS to be compatible with new Berkeley #1021
Conversation
Use logger.fake
…elds Remove duplicate user command fields
Adapt global slot serializations
Fix Wasm build BERKELEY
[berkeley] Make CI run pull requests against `develop`
Merge main into berkeley
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.
LGTM!
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.
awesome fix 🙌🏻
Requesting changes because mina-signer should be kept free from OCaml dependencies!
…orators" This reverts commit c37c459.
"methods": { | ||
"voterRegistration": { | ||
"rows": 1259, | ||
"digest": "252726e585fdd28607537e32214069ab" | ||
"rows": 1260, |
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.
that's interesting, I wonder where that extra constraint comes from 🤔
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.
One more constant that wasn't used before takes one half generic gate!
Two more small change requests:
|
…mmyVerificationKey() with mocks.dummyVerificationKeyHash
…sion of snarkyjs signature.ts
…details This commit updates the unreleased changes link and adds the details of version 0.12.0. The breaking changes in version 0.12.0 are also documented, specifically the fix to the default verification key hash for AccountUpdates. This change adopts the default mechanism provided by Mina Protocol and may affect the verification key of already deployed contracts.
…to inclusion of snarkyjs signature.ts" This reverts commit 4bc172d.
…ks from constants.js
…s.dummyVerificationKeyHash for simplicity and readability
…ecoratorMetadata, useDefineForClassFields, and strictPropertyInitialization to support decorators and generic constructors in TypeScript
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.
approving in advance, but it looks like mina-signer still depends on snarkyjs / jsoo
Got this fixed, thanks to your comments. Thanks! 🎉 |
Description
Merges
berkeley
intomain
Notable Changes
Because the Out-Of-Snark dummy verification key hash changed in this PR, the old verification key hash defaults we used (
Field(0)
) were incorrect. There are several places where this value is hard-coded, so we change each place to use the new dummy value. All changes are contained in this commit: 9b4805dUpdate the vk regression tests by creating a new dump.
🔗 Accompanying Bindings PR o1-labs/o1js-bindings#80