DFST

@mitschabaude You might also consider adding the new function `SmartContract.checkVerificationKey()` that would compare the verification keys of the compiled and deployed contracts. This function can be called externally and internally...

I've seen this error recently with o1js 0.18.0 on devnet with fully working code and properly deployed contracts: ``` Error in task Error: Transaction failed with errors: - {"statusCode":200,"statusText":"Couldn't send...

Yes, you understand me correctly, it is non-deterministic: - It occurs only on devnet; the same test on the local blockchain is passing - It can be resolved by first...

I've tried adding the delay, but it does not help. What I do is wait for the deploy tx to be included in the block, then wait 30 seconds, then...

@emlautarom1 See https://discord.com/channels/484437221055922177/1171938451193593856/1172278215637733407 https://github.com/o1-labs/o1js/issues/1252

The following discussion can also be of interest to you. You can first sign the tx on the web without compiling or proving and then do the compilation, proving, and...

> Thanks @dfstio, we ended up with something quite similar to what is shared in Discord except for the fact that we have 63 files in the cache folder instead...

Thank you! Passing `overrideWrapDomain: 2` to ZkProgram config resolves the issue. Clearing the cache or passing option `forceRecompile: true` does not resolve it.

Using compile({ forceRecompile: true }) fixes it

Yes, it is correct. I've created a small repo with my usual settings that work for me in MinaNFT: https://github.com/dfstio/zkapp-test/tree/dfst (branch dfst) based on @Yoga2015 code @mitschabaude, you can use...