pull down to refresh
https://gist.github.com/1440000bytes/211ac92dd4433bb1a2e674bf0ff7db2e
shit. another zkproof failure. maybe transparency is the only safe strategy.
Yes, but: this is a cache failure, not a zk failure. I.e. from trying to optimize away the compute cost of verifying the proof.
it is both! a failure in the zkproof code because of caching!
idk how you classify code but I do not want to be in your project haha! <3
https://gist.github.com/1440000bytes/211ac92dd4433bb1a2e674bf0ff7db2e