Coby

@mitschabaude `@state(MyOffchainState.Commitments) offchainState = MyOffchainState.initialCommitments();` It is only the commitment that are referenced in the smart contract. Then the `settle` method accepts a rollup proof that _must_ be the right...

Ah right right right... So a non-provable property like ``` class MySmartContract extends SmartContract { @state(MyOffchainState.Commitments) offchainState = MyOffchainState.initialCommitments(); _offchainState = MyOffchainState.default(); // offchainState is a reserved keyword to implement...

> not fetch all actions every time This is fair enough, but also breaks down if more than one party operates the contract right? We can't guarantee that all actions...

> How about this Yeah that's clean!

@asimaranov could you please recreate the graphQL JSON response that fails and the order that the patched o1js arrives at?

@asimaranov No, I mean can you log out the response from `makeGraphqlRequest` in `fetchActions`, then log out the `actionsList` generated by `createActionsList` in this patched version of o1js. If we're...

Thanks @aii23! 40 should still be a processable number so we want to get to the bottom of it. When you do the test with 40, do all 40 actions...

@aii23 , there is another theory that perhaps the archive node is inconsistent about the most recent actions for actions within the same block. If you do the same test...

@aii23 I'd appreciate if you would give the latest commit a spin: [d2c9320](https://github.com/o1-labs/o1js/pull/1784/commits/d2c9320eb44cd9157f8e2059c325292c22f4a84e) Instead of always reversing the order, this commit attempts to find the right order by sorting on...

> make sure to update the bindings to the proper commit from main @Trivo25 I don't know what this means. Is there a script to run or something?