Skip to content

Feature/o1js 3 mesa - #520

Open
garethtdavies wants to merge 5 commits into
proto-kit:developfrom
garethtdavies:feature/o1js-3-mesa
Open

garethtdavies wants to merge 5 commits into
proto-kit:developfrom
garethtdavies:feature/o1js-3-mesa

Conversation

@garethtdavies

Copy link
Copy Markdown

No description provided.

Mina devnet forked to Mesa on 2026-08-19 and mainnet on 2026-09-03. o1js 2.x
builds zkApp commands with 8 state fields and transaction version 3, which Mesa
nodes reject, so the published 0.2.0 can no longer deploy settlement contracts.

Pin o1js and @o1js/native to 3.1.0 in every package and update the lockfile.

mina-fungible-token 1.1.0, the last release before its repository was
archived, declares a peer of o1js ^2.1.0, so a fresh npm install fails with
ERESOLVE. Override its o1js to 3.1.0. The settlement suite's custom token
cases, which deploy and use FungibleToken, pass on 3.1.0.
Mesa raised zkApp app state from 8 to 32 fields. The simulator allocated 8
fields for new zkApp accounts and looped over 8 entries when checking
preconditions and applying updates. Size the new account's state from the
update and loop over the supplied arrays instead.
The deposit and withdraw scripts passed the sender's PrivateKey to
Provable.log, which prints its scalar in decimal. That number is the full
private key, so every deposit and withdrawal wrote the key to stdout and to any
log that captures it. Log the sender's public key instead.

Both lines are also in the published @proto-kit/cli 0.2.0.

This branch has not been deployed

No deployments
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.

1 participant